WordPress.org

Ready to get started?Download WordPress

Forums

Unable to edit posts (13 posts)

  1. Anonymous
    Unregistered
    Posted 5 years ago #

    I have posts showing on my blog, but when I try and edit them I get the following message.

    Warning: main(Text/Diff.php) [function.main]: failed to open stream: No such file or directory in /home/sites/betcritique.org/public_html/wp-includes/wp-diff.php on line 4

    Warning: main(Text/Diff.php) [function.main]: failed to open stream: No such file or directory in /home/sites/betcritique.org/public_html/wp-includes/wp-diff.php on line 4

    Warning: main(Text/Diff.php) [function.main]: failed to open stream: No such file or directory in /home/sites/betcritique.org/public_html/wp-includes/wp-diff.php on line 4

    Fatal error: main() [function.require]: Failed opening required 'Text/Diff.php' (include_path='.:/home/sites/betcritique.org/public_html/wp-includes') in /home/sites/betcritique.org/public_html/wp-includes/wp-diff.php on line 4

    Anyone got any clues?

  2. vachi
    Member
    Posted 5 years ago #

    this just started to happen? cuz i saw your blog and you have posts form earlier,
    try disabling all your plugins first, and have you edited anything outside of the theme folder?

  3. Anonymous
    Unregistered
    Posted 5 years ago #

    The blog shows the posts, but the editor isn't retrieving them. It happened a couple of times before any plugins were installed and I copied and reposted them as a work around. But it is a pain in the rear end to have to do that.

  4. Anonymous
    Unregistered
    Posted 5 years ago #

    Hello ...
    I hv the same problem of not being able to edit previous posts (3 recent posts so far, the latest one happen this morning / July 30, 2008) ...
    Hv posted this problem at the "Feedback & Requests" forum ...
    No idea what's happening!
    Anyone?

  5. plutopsyche
    Member
    Posted 5 years ago #

    I'm getting the same error:

    Warning: main(Text/Diff.php) [function.main]: failed to open stream: No such file or directory in /home/plutonic/public_html/blog/wp-includes/wp-diff.php on line 4

    Warning: main(Text/Diff.php) [function.main]: failed to open stream: No such file or directory in /home/plutonic/public_html/blog/wp-includes/wp-diff.php on line 4

    Fatal error: main() [function.require]: Failed opening required 'Text/Diff.php' (include_path='.:/home/plutonic/public_html/blog/wp-includes') in /home/plutonic/public_html/blog/wp-includes/wp-diff.php on line 4

    Any ideas?

    Thanks!

  6. Anonymous
    Unregistered
    Posted 5 years ago #

    I'm getting the same error and have requested help twice. I hope a moderator is available soon and realizes that a lot of us are having this problem.

  7. pgatroy
    Member
    Posted 5 years ago #

    I am getting the same error. There are a few posts in our system that we can't edit. Just started happening with WordPress 2.6. Never had this problem before.

    Fatal error: Maximum execution time of 30 seconds exceeded in /home/........./wp-diff.php on line 290

  8. Anonymous
    Unregistered
    Posted 5 years ago #

    strange strange ... I have the same trouble with 2.6 but without error
    only the top links are showing

  9. Anonymous
    Unregistered
    Posted 5 years ago #

    post created but not showing ?
    I've found a solution (it's crazy but it works)
    Check the number of the post you can't edit
    in ex : 500
    got to your host Cpanel or Vdesk
    select your database
    run myphpadmin
    call the database
    search for ***_post
    clik it and in the variable "content" copy the whole text, links etc from the post
    close myphpadmin without updare/register etc etc
    go to WP / write/ post
    past the whole post in it
    save and publish
    that's it.

    If the post number 500 still show in the list - erase it.

  10. gelfling
    Member
    Posted 5 years ago #

    The problem arises when an autosave is the last edit (id) for any particular post.

    To fix the problem:

    1) Sign in to your server control panel and go to your phpMyAdmin to access your SQL database

    2) Access the table called [your installation]posts

    3) Sort the table by post_parent

    4) If you know the number of the post that's causing you grief (eg. 123), navigate to where the post_parent numbers match your ineditable post (post_parent = 123)

    5) Among the data for each record you will see something like this:
    ID ... post_name ... post_parent
    456 123-revision 123
    457 123-revision-2 123
    458 123-revision-3 123
    459 123-autosave 123

    There will be no more revisions for post 123 following the autosave.

    6) Edit the autosave record and change the post_name to be the next revision number
    In our example, ID number 459 needs to be changed so the post_name is 123-revision-4
    The corrected data would then look like:
    ID ... post_name ... post_parent
    456 123-revision 123
    457 123-revision-2 123
    458 123-revision-3 123
    459 123-revision-4 123

    That's it! You can now use WordPress as usual and go edit your post.

    NOTE: If you find records that look something like this:
    ID ... post_name ... post_parent
    456 123-revision 123
    457 123-revision-2 123
    458 123-autosave 123
    459 123-revision-3 123

    DO NOT change the post_name of the autosave. This record (or post) is fine and should be able to be edited in WordPress. Editing is only a problem if the autosave is the last ID for the post.

  11. xeroteam
    Member
    Posted 5 years ago #

    Gelfling, (isn't that from The Dark Crystal?)

    Your solution worked perfectly! I've been searching for hours and found nothing but garbage... Thanks for the fix.

    I was editng a pic in the visual window, multiple times, previewing, editing, previewing, etc. Then the post threw an error and I couldn't get back to the edit post section.

    I knew it had something to do with that damn autosave. Thanks again.

    Len Estrada

  12. EyeOfTheTiger
    Member
    Posted 5 years ago #

    Can you disable autosave ??? Would be a great feature for future wp updates if not...this errors caused be grief also...

    Mike

  13. oncidium
    Member
    Posted 5 years ago #

    I just had the same problem and the solution worked perfectly. Hope they can correct this in a future revision!

Topic Closed

This topic has been closed to new replies.

About this Topic