Conflict with “Page Builder by SiteOrigin”

Dear Petra,

Thank you for the conflict report, I tried on a testing environment.

You are right, this page builder doesn’t like my shortcode :/

It seems other plugins are facing the same problem with this page builder, I checked their support forum. The support team always answer to set WP_DEBUG and check php logs. I did that and discovered the page is loading a very big request (probably an infinite loop) and it’s causing a fatal error.

[27-Feb-2021 15:28:01 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in ...\wp-includes\class-wp-query.php on line 3448
[27-Feb-2021 15:28:01 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 73728 bytes) in ...\wp-includes\functions.php on line 4755
[27-Feb-2021 15:28:01 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 73728 bytes) in Unknown on line 0

I tried a lot of things, the shortcode is working everywhere else (on the widget area, on a normal page). I also tried different “SiteOrigin Widgets” (HTML, Text, Rich editor), every single one of them are causing an error.

Travelers’ Map is using WordPress Core functions to save and fetch everything, so there shoudn’t be any compatibility problem with other plugins :/

Sorry to answer I can’t do anything, I will add this plugin in the “Known issues” of Travelers’ Map.

Have a nice day,
Camille

• This reply was modified 3 years, 9 months ago by Camille V.

Thank you so much for looking into this!

Dear Camille,
I have some further feedback from the developers at SiteOrigin and post it here in case you want to make use of it. In a new update, their plugin will contain a fix to resolve the infinite loops, but it wont
“play well with how Travellers Map stores configuration data. It creates a unique instance for each instance of its settings then and that’s problematic because anything that triggers the_excerpt will result in a new hash being generated. Ideally, they should apply the configuration directly to the container (this is what we do for the SiteOrigin Google Map widget) rather than using specific instances using hashing – there can be only one container per map after all.”

Kind regards and thank you for all your work,
Petra

Hi,

I’m Alex from SiteOrigin. I just want to correct something I said:

that’s problematic because anything that triggers the_excerpt will result in a new hash being generated.

I actually meant:

that’s problematic because anything that triggers the_excerpt could result in a new hash being generated.

Here’s a link to what we do in the SiteOrigin Google Maps widget.

The fix we came up with will prevent the infinite loop, but it won’t, or rather can’t, avoid generating a new hash and that’ll result in the map JS not being able to detect the configuration settings.

Kind regards,
Alex

Hi Alex,
thank you for following up on this!
Petra