Search Results for 'beaver builder'

ACF Widgets Support Search Search Results for 'beaver builder'

Viewing 9 results - 1 through 9 (of 9 total)
  • Author
    Search Results
  • #93954
    Daron Spence

    Unfortunately, I can’t extend ACF to render widgets in other places. Not that it’s not possible, but it’s not my place to extend ACF in such a way right now. Any changes to the ACF APIs could render a site broken.

    Beaver Builder and other page builders have run into this issue as well. Until ACF decides to support page builders (which usually use widgets) then I most likely will not as well.

    If you want a refund, I’m happy to give you one and void your license. I’m sorry we can’t find a workaround for this. If things change, I’ll be sure to reach out!

    Daron Spence

    Hey Dallas, I looked into this some more and it seems like this a feature that would be too costly for me to maintain moving forward. Page builders by their very nature kind of break the WordPress mold and do things a little unorthodoxly (which 9/10 is fine!). This is one of those cases where it doesn’t make sense for me to write the support to bridge the gap between ACF and the SiteOrigin page builder.

    Widgets are also in a weird transition right now where they are being used in all sorts of places and core has not defined how to use them universally across front/back ends. I’d also be put into a position to start trying to actively support other page builders (with which there are many) who all do things differently. Ie. Beaver Builder is 100% front end, while SiteOrigin is a hybrid. Creating a consistent experience across platforms isn’t feasible in this stage of ACFW’s life. If you get 100 people to buy the lifetime license we can talk more though 😉

    Let me know if I can help you with anything else Dallas.

    I appreciate your support for ACFW in the interim.


    Daniel Simanek

    Yeah, I saw the Beaver Builder message from earlier, and read through it to make sure my question wasn’t answered there.

    As for the exact issue I’m having, I should have said ‘form’ and not fields. It’s the form used to create the fields, and not getting the data out of them. I’m not sure if that makes a difference to the hooks that are needed, but I figured I would check.

    Daron Spence

    Hey Daniel.

    Page builders can be tricky because they don’t run the normal action hooks like when you’re using the regular post editor. The problem is usually seen on “Front End” page builders more so than /wp-admin/ page builders. Usually if they run all of the hooks needed for an admin page request, it seems to work but not always.

    I’ve heard the same complaints about Beaver Builder as well 🙁

    Sorry about that 🙁


    Alright, thank you very much! The Beaver Builder is not necessarily the final plugin im going to use for my project, so maybe i will find another, more suitable, page builder. What i want to do is insert my built sliders etc. right into any page of my website to offer a big flexibility.

    Maybe the thrive builder is widget ready, im going to take a further look at other user-friendly builders.

    Thank you for your great support! 🙂

    Daron Spence

    David, it seems that Beaver Builder and Advanced Custom Fields are not compatible. ACF uses an action from within the widget creation process to add the fields. Beaver builder is skipping that action entirely and displaying the widget’s form directly.

    I tried it also with the default “Text” widget and was getting the same results as “Einfaches Bild”. This confirmed that the issue lies within communication between ACF and Beaver Builder and not ACFW. In fact, Beaver Builder isn’t even located in the admin area, as none of my ACFW admin scripts were being included in the page builder sections.

    I’m sad to say there isn’t much I can do to help you at this point. 🙁
    Beaver Builder is definitely the one to blame as ACF & ACFW both use the correct hooks and filters for modifying widget content/fields.

    Let me know if I can help you with anything else. For what it’s worth, I peeked into your einfaches-bild template file and everything looks good in there.

    You might try seeing if any of the other page builder plugins work with widgets correctly. I stumbled across this article (https://www.wpbeaverbuilder.com/support/q/support-for-advanced-custom-fields-5-fields-in-widgets/) on the beaver builder website, so maybe they can work on a fix, though it seems unlikely as Beaver Builder is a non-admin area interface.

    Thanks for supporting ACFW though! I really appreciate it! Seems like I’m starting to get a lot more traffic from you kind folks Germany 🙂

    Daron Spence


    I meant to say, is ACF working on other widgets? Add an ACF field to the text widget, and then see if it works in beaver builder.

    Daron Spence

    Hi David, sorry to hear you are having trouble.

    Can we do a bit of troubleshooting? If you add some new fields to the built in widgets (Text, Tag Cloud, etc) do those show up in beaver builder, or are they missing as well?


    Hey there,

    i would like to insert a widget per drag & drop at any place of my website using the Beaver Builder. I added a new Widget, a new custom field, and made sure they are shown (rules). I made a custom field for text and for an image.

    When i open the widgets menu, iam also able to fill in the text and image, but if i use the beaver builder, i guess at any point the plugin is loosing information. It only replys:

    You have not added any fields to this widget yet.

    Add some now!

    Make sure to set the location rules to: Widget : is equal to : example_image

    I hope you can help me with that!
    Thank you very much in advance!
    Very nice plugin by the way!

Viewing 9 results - 1 through 9 (of 9 total)