katart17

@nlpro

Thanks for the clear response. This should help.

I will. Thanks

@enigmaweb I was running only this plugin using the twenty-seventeen theme and I didn’t see any errors in the console or in the debug.log. I did get this to work only if I deleted all existing buttons and re-added them. I don’t know what the problem could’ve been.

Thanks @timse201

Would you prefer one over the other? htaccess or allow iThemes to handle it?

@phpbits That seemed to work for me. Thanks!

@phpbits I’m hiding based on Post Type. I’m using the Post Type option, but if I used the Display Widget Logic option, I would use is_page($page_id).

+1 @beh333

We’re having the same problem here

That’s fine. I just wanted to let someone know. I’m working on a development version and had debug set to true.

I just purged the cache. Are you still seeing any issues?

I noticed the error immediately after posting on this forum. It was the Text Widget with the script code in it. The page loaded properly after removing that widget.

UPDATE: I found the problem. There was a bad Widget that was causing the Dynamic Sidebar string to crash the site.

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.

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.

Ok. The only way to get it to work is if I click on the Go Back To WordPress Editor button when Elementor is enabled and then Update the Post. Now, after disabling Elementor on the Posts post type, I can see the edits made in the Default WordPress Editor.

Is Master Slider now PHP 7 compatible?

@averta was this resolved