rolfkleef

For the record: I had the same problem, and deactivate-reactivate solved it for me too.

hi Evan, just a quick note: the patch in my pull request actually is independent of the issue in this topic… I’d contest the last bullet on your v6.0.3 list:

The fix for that is really on SitePanel’s end. If I remove the patch I proposed to them, the behaviour returns, and their update to 2.2.1 last week didn’t include it yet. It’s not fixable in this plugin.

(The new version does solve my other issue, interference with ‘the_content’ filter, https://www.ads-software.com/support/topic/another-interaction-with-pagebuilder-the_content-recursion)

Hope I’m clear with this ??

Looks like it’s all working fine on my local development version!

hi Evan, thanks! I see the first commit in my pull request indeed is not right.

The second commit in that pull request has a small additional fix. Line 136 in plugin_core/public/css/yikes-inc-easy-mailchimp-extender-public.css refers to id #yikes-mailchimp-container rather class .yikes-mailchimp-container and should be changed then as well, I think:

/** Remove top margin on the form title **/
#yikes-mailchimp-container .yikes-form-title {
	margin-top: 0;
}

Thanks Tracy! I’m keeping my eye on https://github.com/yikesinc/yikes-inc-easy-mailchimp-extender/issues/385 landing ??

Ok, what to do on a rainy Sunday afternoon… finding the culprit:

It turns out that the PageBuilder uses javascript to construct a data structure from all widgets, and scans the form in a widget for all elements with a “name” attribute.

Since Easy Forms assigns a “name” to each <option> in the form <select> box, it basically ends up setting form_id to the last option in the list.

I have proposed a fix to the PageBuilder plugin that solves this https://siteorigin.com/thread/problem-with-easy-forms-for-mailchimp-widget/#comment-82633

Thanks for your efforts!

Hi Evan, Tracey,

Thanks! Site Origin’s response basically is to integrate their code suggestion, so if you’re up for that: great!

To make sure we have no misunderstanding, Evan: when using Page Builder, it’s possible to add any widget to block on the page, and on my sites, Easy Forms does appear under the “all widgets” section or when searching.

I’ve used that before with “Easy Forms” 5.x, and it’s still possible for 6.0 — except that somehow the choice of which form to use is not properly stored upon save in 6.

Maybe for information: my workaround now is to just duplicate the form (it’ll be last in the list), add the widget to a page, save that page, and hopefully not have to adapt its content soon ??

~~Rolf.

Cross-linking: https://siteorigin.com/thread/problem-with-easy-forms-for-mailchimp-widget/

Hi Evan, thanks for taking the effort to investigate!

The shortcode works, although I don’t know how to adapt the label of the submit button.

I just tested it with a clean WordPress setup, with only the plugins siteorigin-panels and yikes-inc-easy-mailchimp-extender and the default theme. When I add a new page, switch from “Visual” to “Page Builder”, and click “+ widget”, “Easy Mailchimp Forms” is one of the options.

So now we have two problems… ?? Creating a reproducible environment.

There is a short page at SiteOrigin about making widgets compatible, I’d guess you might know if this is relevant: https://siteorigin.com/docs/page-builder/widget-compatibility/

I can see an add_action to enqueue_scripts as described in their documentation, but haven’t found anything around form setup.

But it may be irrelevant. I can add and edit the widget in Page Builder, it only “loses” the actual form id when saving the page.

I’ll start a forum thread there too.

Thanks!
~~Rolf.

thanks for the quick fix ??

oops, should have mentioned that I’m referring to the code for getButton() in flattr.php…

I have the same warning in my cron job output since I upgraded the plugin to 2011.1019 on WP 3.2.1

What I can find so far: on line 64 it tries to read a file specified in $url that only contains ‘http:’

Feedwordpress tries to process all links in the category Contributors.

I had one site listed without an RSS feed associated with it. Putting that site under a different link category (so feedwordpress doesn’t process it anymore) stopped the warnings.