Problem 2.5.1 post_new.php and post.php

i having the same flash problem… it’s real pain..
hopefully so one will be able to help out.

simpgr, I keep checking back here for the answer . . . we need a code genius and we need one now.

You can try deleting the wp-admin and wp-includes folders and repeat the 2.5.1 upgrade. Clear your browser cache, delete cookies, relaunch and hope. ??

You can try deleting the wp-admin and wp-includes folders and repeat the 2.5.1 upgrade.

Yes, this is very, very important and I cannot stress this enough. 90% or more of the problems I’ve solved via email were fixed by this simple trick.

DELETE wp-admin and wp-includes from your server.
UPLOAD those two folders again.
DO NOT OVERWRITE FILES.

I don’t understand why some people cannot overwrite files properly (overwriting works fine for me every time), but everybody else seems to have this issue. If you try to simply overwrite the old WordPress with the new one, and something is wrong, then that is your problem; you cannot overwrite properly. Replace the files instead, by deleting first.

thanks Otto you make us all want to continue using WordPress.

A clean install worked. I attempted to only replace the wp-admin and includes directories to no avail. The app still acted up. I dont know what the deal was, but i eventually created a dev location and set that up to test then moved to the production location. Pretty weird, i’ve never experienced this before, esp. not with WP.

At least i can use it now. Thanks for your help guys.

– delete everything on your ftp related to wordpress (including plugins, theme and htaccess file
– DO NOT DO ANYTHING TO THE DATABASE
– upload a fresh 2.5.1 package to your server
– modify wp-config.php
– enter admin, enable default theme, check if everything is OK, verify the public view of the site
– then, one by one, upload, enable and configure your plugins, checking the site and publish functions everytime
– finally enable your theme

ZuesII,

I have tried this with Cuzoogle’s install and even attempted to create a /dev directory with a fresh install of 2.5.1 and I still get the script error. I’m beginning to think there might be a database issue, because a fresh install w/ new database works, but if you connect to his database it gives the error. Any thoughts?

and I still get the script error.

What script error, exactly?

This is the error:

https://cuzoogle.com/wp-content/uploads/2008/04/errorscreen1.gif

Otto 42- Thank you- this does appear to be a problem with FTP client not sufficiently over-writing files in wp-admin and -includes. For me, deleting those directories from the server and re-uploading the new versions has fixed the prob. Thanks!

I am going to try again to see if I might have missed a step.

I had the same problem as everyone, and I tried deleting the the wp-admin and includes folders and uploading them again (as the upgrade guide says). That didn’t do it, so I deleted all the main wp files, modified and used the new wp-config file, and uploaded the 2.5.1 install main directory wp files. Basically, I did new install in a shortened form. I do hope the developers get this resolved, but thanks for the help.

I did exactly as Zeus suggested above and came away with the same script error when writing a new post as before. I don’t know what is wrong with this installation, but the only common denominator is the database. I’m of the opinion that something in the database is corrupt.

Hi,

I’m pretty new to WordPress, but I’ve encountered this problem too since upgrading to 2.5.1. I haven’t looked into why this problem is occuring, but I do have a quick/dirty workaround to disable autosave completely.

Make a backup copy of /wp-includes/js/autosave.js, then after line 135:

var autosave = function() {

add the line:

return;

Fingers crossed for an official patch soon!

As above, have the problem with AutoSave.
This only appeared after a upgrade from 2.3.1 to 2.5.1, I missed 2.5.0. I used the Automatic Update Plug-In.

Creating a new post is fine, you can even write stuff no problem. The problem appears after the first Save. Thereafter, the site becomes non responsive as does the Browser, in this case FireFox and Safari and Camino. The issue affects the whole browser window including any open tabs. Closing the offending WordPress pages clears up the response time.

The Save button just continually flashes randomly thus locking you out of doing anything productive. YOu can sometimes get the site to save any changes by just bashing the Save button continuously, eventually it notices the trigger, but still becomes unresponsive.

I have removed ALL plugins this had no effect.

I DELETED the above WP-Include and WP-Admin folders and replaced these, sadly this did not solve the issue in my case.

To me, this could be solved by being able to disable the Autosave feature, thus eliminating the problem until the real reason can be established. Even changing the AutoSave time delay to some extraordinary time would help. But the powers that be seem to think there is no valid reason to offer the user the ability to choose to have AutoSave or not. This appears to be one good reason I can think off to have this option.

As it stands, WordPress is unusable for me. It take great patience and time to create one post, much closing windows and reopening. This is clearly a problem for many people.

Someone must be able to find out where in the PHP code, Ajax scripts there the code is to alter the AutoSave?

I am reluctant to have to do another clean install, im not that confident with all of this to be able to do it. But I guess I have little choice right now if I want to use WordPress.

There is a possible link to the Database being the offender. After the update, a warning message came up saying the Database had not been updated neither had the ‘clean -up’ of files taken place. This was all the by-product of using the Automatic Update plug-in. But the flashing save button seems to be quite unrelated to any of this, then what do I know.

New install coming up.