Forums

Your Attempt to Edit Post "" Has Failed Issues (8 posts)

  1. NOLAKeith
    Member
    Posted 3 months ago #

    I keep having this issue and no matter where I search I cannot find a solution. I have tried the "fix" by turning off the autosave but that created more problems for the site than by keeping the autosave on.

    Is there any support for this or an idea of when WP might fix the issue?

    This is something that just popped up within the last couple of months and it is driving me insane. I've read some people who havent had the problem and now starting to think it might be a web server issue?

    I am using a Plesk Windows server. Is it possible this could be the problem?

    I am not sure what the deal is, but I have a local copy of my website on my desktop and posting works fine. All plugins are installed on the local machine and have no issues.

    I did a test post on my live site without any custom fields and the posting worked fine. I did this three more times with one of those times using custom fields and it worked.

    However, all of the tests posts were just text, no coding at all. Could this be an issue now?

  2. jdembowski
    Member
    Posted 3 months ago #

    One thing that won't help you is creating multiple threads with the same topic.

    http://wordpress.org/support/profile/2357626

    I don't have this issue so I can't really comment. But one thing that might help you here is if you can provide provide the version of WordPress, version of PHP, plugins, etc.

  3. NOLAKeith
    Member
    Posted 3 months ago #

    I wouldnt have to create multiple threads if there was some credible answers.

    If you read to the right of the topic discussion you will see I am using WP 2.8. However, I've had this issue since I upgraded to 2.7. Just all of a sudden the issue arose.

    I've been using the same plugins - Featured Content Gallery, WP Super Cache, Google XML Sitemap, and SimplePie for WP.

  4. jdembowski
    Member
    Posted 3 months ago #

    I am not sure what the deal is, but I have a local copy of my website on my desktop and posting works fine. All plugins are installed on the local machine and have no issues.

    Local desktop version works, web server version displays the problem occasionally. I'm drawing a blank but something's different between those two environments. Can you do the following and create a file called phpinfo.php with just this line in it

    <?php phpinfo(); ?>

    Load that file on your browser via both your local desktop version as well your server version. That will give you a dump of your PHP environment for both installagtions.

    Check the major and minor version numbers of your PHP and see if anything in the output leaps out at you.

  5. NOLAKeith
    Member
    Posted 3 months ago #

    Well it appears the versions are different. On my live site I am using PHP 5.2.6 and on the local site it is using PHP 5.2.9.

    Would that be possible to change how things are in my wordpress installs?

    I will try to repoduce the error in my local install.

    No error when testing. Just sent request to server admins to upgrade PHP.

  6. csw
    Member
    Posted 2 months ago #

    Hi,

    Any solution for this issue? I'm having the same problem.
    My Wordpress version is 2.8.1.

    Thanks.

  7. billydec
    Member
    Posted 1 month ago #

    I'm also having the same issue. I'm using 2.8.5 but this has been happening since upgrading from 2.7

    I've searched all over but can't figure out what's going on. Any help would be greatly appreciated.

  8. mikego
    Member
    Posted 1 month ago #

    In both Wordpress 2.8.4 and 2.8.5 (we have 3 WP blogs that are affected by this bug), I've found that if you do enter the body of the post and not enter a title, you can skirt this bug. After you select "Save Draft" or "Publish", you can go ahead and enter the title and save it. (My permalinks setting is set to Default.)

    BTW, I've also imported the contents of one blog into a brand new Wordpress blog (into a fresh MySQL database) but that didn't work either which leads me to conjecture that something in the contents is triggering this bug.

Reply

You must log in to post.

About this Topic

Tags