Site logo

Archived topic

Trouble with customizing my page

15 replies · Started by Tobias on September 23, 2016

Viewing posts 1–15 of 16

Hey everyone,

so I have this problem with customizing my page when GP-Premium is activated. I have tried deactivating all my other plugins - it has nothing to do with that. I also narrowed the problem down to the features "Background" and "Copyright". Whenever one of the two is activated, customizing wont work and i only get a white screen instead of the options. The other add ons like "Colors" work fine. However I had the same problem with different add ons before.

Any ideas?

Thanks in advance. :)

I just checked that - the limit is set to 256MB and only 35MB are used right now so i don't think that is the problem :S

I've tried this on a page where the only plugin installed is GP Premium - the issue does still exist. :s

I can sometimes get "Backgrounds" to work by randomly activating/deactivating other features. However I can only customize my page once then. When I try to access "customize" again it shows me the white screen again. It's just really odd.

I will try WP Debug and checking the error_log next. Let's see if any of that works :o

White screen can mean a couple things:

1. Ran out of PHP memory. The fact that it works when you disable some add-ons/plugins points to this. Less things running = less memory usage. It might be worth upping the value even more just to test.

2. PHP error - this would be caused by another plugin and would show up in the error_log file.

Okay so I turned on WP_Debug and got this error message: Strict Standards: Redefining already defined constructor for class wp_memory_usage in / ..... on line 39

When I saw this I thought maybe it is an issue with the php memory. So I checked the php memory again - it is set to 256mb but turns out Wordpress was only able to use 40mb. I thought I finally found the problem, set the limit to 128mb using define('WP_MEMORY_LIMIT', '128M');

However the problem still occurs. I have no idea what to do at this point. :/

You may have to set it in your php.ini file. If you call your hosting they should be able to point you in the right direction.

The memory is set to 128MB for Wordpress - that's unfortunately not the problem.

Could it have anything to do with the browser, cache or cookies?

It could do, but I'm still leaning towards PHP memory. The amount the page is reporting could be false, so that number might need increasing regardless of what the numbers are reporting.

The fact that turning on certain functionality fixes it points to PHP memory and not much else.

I don't have access to the php.ini file. However in .htaccess it says „php_value memory_limit 256M“ and in wp_config.php I set the limit to 256MB with “define(‚WP_MEMORY_LIMIT‘, ‚256M‘);” - that didn't fix it.

I also tried two different plugins, which show the available and used memory. They both showed me that the WP limit is set to what i set it.

So unfortunately I don't think that php memory is the problem. :o

Would it help if i gave you some sort of guest access to the page so you could take a look at the problem yourself?

Sure, you can send it through the contact form right here on this site :)

Sorry but where exactly can i find that contact formula? :D

Sorry, here you go: https://generatepress.com/contact/

Looking into this a bit more, the error you received above, did it happen with this plugin installed?: WP-Memory-Usage

If so, that's a super old plugin - I would deactivate it.

In your wp-config.php file, did you add the line looking exactly like you wrote it above?:

define(,WP_MEMORY_LIMIT', ‚256M');

If so, it should look like this:

define('WP_MEMORY_LIMIT', '256M');

It's possible that this isn't working because the value in your php.ini file is overwriting these values.

If that's the case, you'll need to contact your server and ask them to up the limit.

Yeah I deleted that plugin after I found a better one anyways.

Sorry i mistyped above. I checked the FTP and the code is right.

I sent you a message with the required data. I hope you can find whatever causes the problem :)

This archived topic is closed to new replies.