michaelrod77

Problem solved… you can check out the answer here:

https://stackoverflow.com/questions/17954818/cant-add-new-posts-in-wordpress-memory-error/17998468#17998468

Problem solved… you can check out the answer here:

https://stackoverflow.com/questions/17954818/cant-add-new-posts-in-wordpress-memory-error/17998468#17998468

No repsonse, so we went with another plugin which works very well: Advanced lazy load. It doesn’t allow lazy loading of widgets, but does a great job with images and causes no errors.

Just to update… I solved most of the errors I posted, but one main error still looms:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 491520 bytes) in /var/www/staging.collegespun.com/wp-admin/edit-form-advanced.php on line 306

I have increased the memory to 512M in php.ini, wp-config.php, and in default-constants.php, but I still can’t seem to get past this error (which seems to show an allowance of only 256M). Is there another place/file where the memory can be increased?

BTW, I have the default template (twenty-eleven) running with all plugins disabled and the error still shows.

Just switched ‘display_errors = On’ in the php.ini and found the error message on post-new.php:

Notice: Trying to get property of non-object in /var/www/staging.collegespun.com/wp-content/themes/collegespun/functions.php on line 182 Notice: Undefined index: college_setup_options_noncename in /var/www/staging.collegespun.com/wp-content/themes/collegespun/includes/college-setup.php on line 125 Notice: Undefined index: conference_setup_options_noncename in /var/www/staging.collegespun.com/wp-content/themes/collegespun/includes/conference-setup.php on line 101 Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 491520 bytes) in /var/www/staging.collegespun.com/wp-admin/edit-form-advanced.php on line 306

Looks like several errors here.

Thanks, mzandstra. I checked and confirmed that both the value in the DB and in version.php are matching. In my case, for version 3.5.2, they both match db_version 22442.

I also tried your point #6 (removing spam comments) but it didn’t help either unfortunately, although I can imagine tat the system will probbaly run a bit faster after that once it’s running normal again. Thanks.