The page on which I get this error is a Formidable Forms View, which has its own details “page”.
What that means in FF is that you can view all the entries for a form (what FF calls the Listings Page), and when you click on one of them, you see the full entry (Details Page) as if it was a separate page.
I use Page Builder with a single row and a SiteOrigin Editor widget, containing the FF shortcode for the View.
I’m thinking that Page Builder might be interpreting the entry details as an attempt to render the page a second time??
On pages where I run FF Views that do not use a Details Page, I don’t get the error.
We’ve been running FF and SiteOrigin on this site for almost two years now and this has never come up before.
I’ve updated SO in the last day to 2.22.1 and WP is at 6.2. Formidable Forms is also up to date at 6.2.3.
Hi George
Thanks for getting in touch.
The check in question was added to prevent a situation where another plugin was repeatably rendering Page Builder, resulting in the memory limit being reached. I’ll ask Alex here at SiteOrigin to take a look but it’s likely the issue triggered by Formidable.
Hi George,
I’ve had a look at how Formidable Forms handles output on the details page and I can confirm this notice is being triggered by that plugin. This isn’t something we can directly fix and Page Builder will ensure this can’t result in a more serious error. We added checks to prevent repeated rendering a few years ago so it’s likely that Formidable Forms recently made a change that introduced this so I recommend reaching out to them to see if they have any ideas.
Kind regards,
Alex
Fabulous, Alex – I thought that might be the case.
And thanks again for Page Builder – still my go-to way to build in
WordPress!
Hi George,
Thank you for your very kind words. :)
Please feel free to open another thread if anything else comes up and we’ll lend a hand.
Kind regards,
Alex