dde7

I just increased the PHP memory limit as recommended, by adding the line:

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

to wp-config.php (Network Solutions did allow me to do this, with no problems. This has solved the update problem; I was able to update WordPress to version 3.8 and to update all plugins and themes that needed it. Thank you so much!

Unfortunately, the other problem (cannot edit pages/posts because text and control buttons do not appear in the editor) is still the same in 3.8 as in 3.7.1. Do you have any suggestions for this other problem? Will a further increase in memory (beyond 96M) be likely to help?

Thanks for the tip! So let me make sure I get this straight. As I understand it from the article you linked, I need to edit the file wp-config.php to add the line:

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

(Or substitute any other limit if I want more than 96M.) Is that it?

I’m also hosting with Network Solutions! And I’m noticing site slowdowns, although the update finally went through. Thanks for posting; it had never crossed my mind that this could have anything to do with Hurricane Sandy. Do you have a link with more information about the hosting debacle you refer to? If so, please post it!

Never mind; it finally updated successfully to Jetpack 1.9.1 after yet another attempt. I hadn’t changed anything; I just kept trying to update.

Thanks so much, Jan Dembowski! I followed your instructions, and deleting the annotum-base directory fixed the problem in exactly the way you said. Since Twenty Eleven was the default theme, it was chosen for reversion when Annotum Base was found to be missing.

Thanks. Indeed, it sounds like I’ll have to go to Network Solutions. Maybe I’ll show them this discussion (and post back here as to what experiences I have with them). Your advice is appreciated.

If I don’t get a good resolution from Network Solutions, maybe I’ll try what you first suggested anyway. The restart of Apache is presumably just to get PHP to reread PHP.INI; on a large ISP like Network Solutions, that may happen periodically anyway.

Longer-term, though, it would be good if WordPress developers could find a solution that would avoid the need to go outside WordPress itself. If (as appears to be the case) this problem is simply a result of page size, I can’t be the only one affected, by any means. A hard maximum limit on usable page size will fundamentally restrict the range of functionality of WordPress.

Thanks. But what should go in the PHP.INI file? Normally if I were attempting something like that I would make a copy of the existing PHP.INI, but since I can’t access its location on Network Solutions, I can’t even copy it, much less modify it in place. The suggested fix from the article I linked to is only two lines. I’m concerned that making a PHP.INI from just those two lines will break WordPress by omitting other needed settings.