• Resolved katart17

    (@katart17)


    I noticed that when I have the Page Builder by SiteOrigin plugin activated and then activate the Content Blocks plugin, the site crashes (white screen).

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Johan van der Wijk

    (@vanderwijk)

    Hi Katart,

    Could you please enable debug and post the error message you get here?

    In case you haven’t used the debug functionality yet, here you can see how to enable it: https://codex.www.ads-software.com/WP_DEBUG

    Thread Starter katart17

    (@katart17)

    I activated DEBUG_LOG and received these messages:

    [01-May-2017 12:53:50 UTC] PHP Notice:  Undefined index: row_styles in /xx/xx/public_html/wp-content/themes/edmond/functions.php on line 224
    [01-May-2017 12:53:50 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 32 bytes) in /xx/xx/public_html/wp-content/plugins/master-slider/includes/lib/aq-resizer.php on line 68

    I received multiple of the first line and only one of the last line. I also tried deactivating Master Slider while Content Blocks was active and I still get the White Screen.

    Another thing that was interesting is that when I had Content Blocks activated and Master Slider deactivated, I received the following message in the Error Log:

    [01-May-2017 12:58:44 UTC] PHP Notice:  Undefined index: row_styles in /xx/xx/public_html/wp-content/themes/edmond/functions.php on line 224
    [01-May-2017 12:58:44 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 65552 bytes) in /xx/xx/public_html/wp-content/plugins/lightweight-grid-columns/lightweight-grid-columns.php on line 169

    It seems to be pushing the Memory Limit to any random plugin (I don’t really know what this means). I keep bumping up my MEMORY_LIMIT but that doesn’t seem to help.

    Plugin Author Johan van der Wijk

    (@vanderwijk)

    Yes, the fatal error is definitely related to the PHP memory limit. As this issue is not caused by the Custom Post Widget plugin I would suggest contacting your hosting provider. Changing the MEMORY_LIMIT value often doesn’t work because hosting providers don’t allow users to change their own memory limit (if all users would do this on a specific server, it would not take long before it would crash completely).

    Thread Starter katart17

    (@katart17)

    Thanks for the response.

    It is a MEMORY_LIMIT error, but I think it has something to do with the PHP Notice line (which is an error in my custom theme). When I have the Custom Blocks plugin activated and the MEMORY_LIMIT is set at 256M, the Error Log gets over 6000 lines of the PHP Notice and NO Fatal Memory Limit Error is thrown.

    I’m in communication with the SiteOrigin developer to see how to fix the code in my custom theme.

    UPDATE: after running another test, the Memory Limit error is thrown. I hit a Fatal PHP Error after the PHP Undefined Index Notice runs through thousands of times. The Memory is exhausted and is over the limit after the PHP Notice loops through too many times.

    • This reply was modified 7 years, 7 months ago by katart17.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Conflict with Site Origin Plugin’ is closed to new replies.