Error while editing themes

Discussion in 'WordPress' started by longroad, Feb 4, 2007.

  1. #1
    Im just installed Wordpress 2.1
    Trying to edit sidebar.php and header.php by inserting some adsense code.

    I've tried this both in some different custom themes as well as the Default them, and it doesnt work in any.

    I am getting this error after updating in the Theme Editor:

    An appropriate representation of the requested resource /wp-admin/theme-editor.php could not be found on this server.

    I've reuploaded theme-editor.php but still the same thing happens.

    Any ideas?
     
    longroad, Feb 4, 2007 IP
  2. watershawl

    watershawl Peon

    Messages:
    29
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #2
    This happened to me when I deleted the top comment section of the stylesheet. Wordpress seems to lose the ability to find the file after that and errors out. To get around this, I just edited the information there instead of deleting it and this fixed the problem.

    Indianapolis Web Design - http://www.telablue.com
     
    watershawl, May 17, 2008 IP
  3. arramuse

    arramuse Active Member

    Messages:
    512
    Likes Received:
    4
    Best Answers:
    0
    Trophy Points:
    60
    #3
    you may not be setting or switch to Writable mode..

    Please Check Cmode dir..
     
    arramuse, Jan 13, 2009 IP
  4. niitdebasis

    niitdebasis Banned

    Messages:
    84
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    0
    #4
    Your Theme Is Not Supported By the Wp Vr2.1 please Upgrade Your Wp From 2.1 To 2.5.4 Or Higher Your Problem Will Be Solved because previously i had faced this problem and i upgrade my wp version 2.1 to vr2.5.4 then the problem resolved.Try This.Hope Your Problem Will Be Solved.
    Thanks.
     
    niitdebasis, Jan 14, 2009 IP
  5. longroad

    longroad Well-Known Member

    Messages:
    1,645
    Likes Received:
    25
    Best Answers:
    0
    Trophy Points:
    155
    #5
    Nothing to do with that, it was a server issue.
     
    longroad, Jan 14, 2009 IP