Luis Martins

Would love this one too. Even after working with the plugin for a while I keep tabbing when trying to move to the next field.

I see your point, I’ll override for my use case. Thanks.

Any feedback on this?

Hi Greg, thanks for your feedback.
A bit surprising you haven’t tried WP CLI, you really should give it a go. Globals are always problematic, but I’ll check with them too to see if there’s something that can be done here. They will probably say this should avoid globals. Lets see.

Many thanks Andrew for the feedback and for not taking to heart my comments here.

Great, thanks for the update and the feedback Andrew.

Cheers
Luís

Hi Andrew,

Many thanks for your comments.

1. I see your point. I wouldn’t mind having the option on both locations actually. The top bar is a crowded space with plugin like yoast filling that area. It’s just a small detail.

2. Well, not having shortcodes all over the place is another thing I love about Tailor so if the consequence of that is loading a few assets im pretty ok with it.

3. In some projects I use ACF fields to create different content regions on one give page. But after this a little more though, it might not be as important as I first imagined, and considering the implications when editing from the front-end as you mention on point 1) it might as well be ignored.

Thanks again Andrew.

Apparently this is still the case, the plugin hasn’t got image updates for a while.

Hi Ogrosko,

Not really sure what you mean. I use Timber’s caching by passing the expiration parameter in the render method:
https://github.com/timber/timber/wiki/Performance#cache-the-entire-twig-file-and-data

Im not understanding how will the dashboard be able to detect if my front-end makes use Timber’s caching this way.

Any updates please? Can you confirm if this is still working for you on the latest version of WordPress/Timber?

@david, having tested loading the form via the API I get the same behaviour. The form is properly rendered (the assets were loaded with wp_enqueue_script( 'cf-dynamic' ); but when I submit the form it still triggers a full page reload.

The form data does get submitted though, and the URL is appended with ?cf_su=1&cf_id=10

Digging through the code I’ve noticed that neither the form or the submit button have js events attached to them, is this normal?

While I haven’t found this info in the documentation, I did however managed to learn what I was after. Closing this.

@david, any chance you could provide some feedback?

Hi David, yes this is with the latest version.

I actually just installed on this particular project as I am trying to convince the client to switch from gravity forms to Caldera.

What happens in my case is pretty much the same das @bucketpress described. I added wp_enqueue_script( 'cf-dynamic' ) which also makes the form styling available on the ajax page where the form is displayed, but when I submit the form the entire page gets reloaded loosing the state it had before.

Thanks for any help, and congrats on the awesome release btw.

Having the same problem has @bucketpress, is there way to get the submission to not trigger a page reload on this situation?