What would keep admin from seeing chmod change?

  • Last week I attempted an upgrade from from 1.2.2 to 1.5. I had to undo that by doing a restore.

    Ever since, even though I have used cPanel file manager to change permissions on index.php, style.css, etc., to 774, WP’s admin page refuses to recognize the change. It still insists that to use it to edit a file directly, I must chmod. Been there, done that, and the change does show on the cPanel file manager page.

    What file or function within WP is responsible for “seeing” this change?

Viewing 5 replies - 1 through 5 (of 5 total)

  • Are you and WP definitely looking at the same pages ?
    And perms of 666 are adequate.

    Thread Starter swanderson

    (@swanderson)

    Hi, podz. Yes, we’re looking at the same pages. The message on the bar underneath the template page editing area specifically says the file cannot be edited until the permission level is changed. Click on it and it does nothing.

    Thread Starter swanderson

    (@swanderson)

    I still can’t edit directly from the admin page because WP won’t recognize that I have changed permission for index.php and several other files. Doing it through cPanel is as handy as going through a basement window to get into the house, as opposed to using the front or back door.

    Any additional thoughts, tips, insight would be appreciated. I expect there’s a WP file with a switch thrown the wrong way or something.

    Again, the cPanel display shows the files as permission 774. WP admin page doesn’t get it.

    I can’t but think that you are WP are not looking at the same files.

    When you upgraded, did you delete every file from the server BEFORE uploading any new ones ?

    Thread Starter swanderson

    (@swanderson)

    Here’s the sequence, as far as the blog in question.

    1. After backup, I deleted all files from the subdomain in which the blog exists except wp-config.php, as per directions.

    2. I ftp’d the 1.5 files to my Web space.

    It went badly. I deleted everything but wp-config.php, tried again. Again, it went badly.

    3. I deleted everything from the subdomain.

    4. I restored the backed up files.

    What’s there now is WP 1.2.2. I’ve got other things working fine, but the admin page insists file permissions haven’t been changed so they can be edited.

    BTW, I have since successfully installed 1.5 in a different subdomain using Fantastico, then followed the directions for moving from 1.2 to 1.5. It all looks good with my considerably modified style and seems to work, although it’s not hooked into the pre-existing database.

    Having done this, I now have a much better feel for it and will soon tackle the project again to get the live blog up in 1.5. I suspect my previous problems stemmed from my misunderstanding about php files being transferred as binaries, and also with trusting the ftp program’s automatic feature to make the right choices in transferring. In working with files in the fresh install of 1.5, uploads of modified files were done manually, with everything but graphics files going as ASCII text. Then, everything worked.

    This might be something others have tripped over as well.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘What would keep admin from seeing chmod change?’ is closed to new replies.