larkinsoft

esmi, the solution was simpler but less obvious. I had edited the contents of .htaccess in my wp-admin folder to deny non-admin types, and in the process had removed the WordPress default code (see below). Adding the code back in below my edits restored the page/post editor functionality.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /[yourhomefolder]/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /[yourhomefolder]/index.php [L]
</IfModule>

# END WordPress

Dave, I found what was preventing the editor on my system. I had edited the contents of .htaccess within the wp-admin folder on the server to deny access to non-admin IP addresses. In the process, I had removed the WordPress code that was in there. Adding it back (example is in the wp-content folder) solved the problem. The code should resemble the following:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /[yourhomefolder]/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /[yourhomefolder]/index.php [L]
</IfModule>

# END WordPress

Also, make sure that the .htaccess file in your wp-admin folder contains the following code (put there by default, but many developers edit this file for security purposes):

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /[yourhomefolder]/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /[yourhomefolder]/index.php [L]
</IfModule>

# END WordPress

I’m getting exactly the same problem. Just installed latest WP and cannot edit any content on either posts or pages. All other screens and data appear fine, so I strongly doubt it’s the database. I went into PHPAdmin to see that all tables were readable, etc., and everything looked fine.

I’m wondering if a setting in FireFox is blocking the AJAX code that allows editing, or if it’s a directory permissions setting, or a browser incompatibility with the latest WP.

Anybody at WP.org have an idea. Prior versions of WP did not have this problem.

Thanks a million Jarret – I appreciate it!