Whether or not there maybe anticipation of making ACF Pro compatible with a Page Builder in the future (or its own), can you help offer a direction for me of why ACF Pro fields do show in SiteOrigin’s Widgets but do not save?
Consequently, this ability would offer a whole new dynamic for ACF Pro and developers with this being useable. I have seen a lot of inquiries on both plugin support areas; yet, no response of why or how to proceed. It seems like half the battle is already there considering the widget abilities seem functional.
Can you help offer guidance of why ACF Pro is not saving? Or, an ETA of when you may hope to make this possible (if being considered)? Thanks.
These are only guesses, I don’t know anything about the plugin that you are referring to.
My first guess at why fields are not saved in those widgets is because they are not saving the widgets in a standard fashion. With widgets ACF save fields on the widget_update_callback hook. If for some reason this hook is not being fired by WP then ACF would not update the values.
My second guess, if this hook is being fired, is that ACF can’t figure out the correct ID to save the values to. The 4th parameter of the callback is $widget and ACF saves the fields to acf_save_post( "widget_{$widget->id}" );
then again, that values might be getting saved, and ACF can’t find them again because of some other issue that is making it hard for ACF to get the values that were saved when it reloads. I can’t be sure.
I’m not the developer, but ACF is designed to work with the standard way that WP does things. If the widget plugin does things in some other way then ACF may never work with it.
I absolutely love ACF and if I could tie this with a PageBuilder like SiteOrigin as I am not a fan of bulky page builder or themeforest dependended ones, it could help some of my clients that chose not to use me for all their website work.
I’m going to relay this to SiteOrigin PageBuilder and see what they say. Thanks John for always stepping up to questions so quickly.
