edit problem with 2.6

  • I can’t edit some of my posts with wp 2.6.
    I get this message when I try to use the edit page:

    —–
    Warning: main(Text/Diff/Renderer.php) [function.main]: failed to open stream: No such file or directory in [path to my site]/wp-includes/Text/Diff/Renderer/inline.php on line 17

    Fatal error: main() [function.require]: Failed opening required ‘Text/Diff/Renderer.php’ (include_path=[path to my site]/include:.:/usr/php4/lib/php’) in [path to my site]wp-includes/Text/Diff/Renderer/inline.php on line 17
    —–

    It seems to happen only when I’ve added an image to the post via the media uploader. I haven’t modified any of the wp files, and it didn’t happen with 2.5. I’ve done the upgrade by the book, but maybe I’ve done something wrong?
    Thanks for any help you can give me.

Viewing 5 replies - 16 through 20 (of 20 total)

  • now, i cant add http links in the articles … -.-‘

    It’s not fixed in 2.6.1 and the patch by codestyling doesn’t work for me. I don’t know what to do. My client is NOT happy.

    I have the sanem problem, since I updated blog to 2.6.1 (2.6?) how far I can remember.
    I checked those files that ^redbyte mentioned, they’re properly uploaded (first, uppercase letter).
    So I think, my problem is that my hosting provider (Dreamhost.com) had disabled the ini_set() function.
    I won’t ask my privder to enable this fucntion if this has been submitted to WP Bug Track already (2.7 version very soon!) So now, I prefer to just edit quickly some files: https://www.wacdesigns.com/2008/08/02/fatal-error-require_once-functionrequire-failed-opening-required-textdiffrendererphp/

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    There is no “ini_set” bug anywhere in WordPress 2.6.2, because the places that ini_set is used are all ignoring the result.

    See, this message:
    ini_set() has been disabled for security reasons in /.../wp-includes/pluggable.php on line 1517
    …doesn’t make any sense, because pluggable.php does not contain any reference to “ini_set” at all.

    Now, the phpmailer class does use ini_set in some cases, however it checks for safe mode first and doesn’t use it in those cases.

    Also, upper/lowercase always matters. Only Windows doesn’t care, every other operating system on the planet does. So yes, case is important and always has been.

    I was getting a similar error, however, without the “inline.php” file. I used the patch from code-styling.de, but that didn’t help.

    Then for shitz and giggles, I went to one of my working blogs, copied the Test folder, pluggable, and wp-diff files over to the blog that was broken. It worked perfectly. Before copying, I erased all instances of the “bad” files and folder from the broken blog to avoid any mishaps…

    The broken blog was WP 2.6.2, the working blog was a WP 2.6.1 but the files copied over fine and without error.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘edit problem with 2.6’ is closed to new replies.