I keep getting, "If this file were writable you could edit it" at the bottom of the Theme editor...any ideas on how I can remove this so I can customize a theme? Thanks for any help,
Gabe
If this file were writable you could edit it. (16 posts)
-
Gabeperspectiveyecom
Posted 2 years ago # -
Make the file writeable?
Check out the Changing_File_Permissions article in the Codex.
-
chooky
Posted 2 years ago #hi Gabe-
I TOO have this! Ive been hopping all over Support Forum for other probs, this being one of them.
Have you sorted???? If yes, can you tell me how?
Thanks
Chook -
chooky - did you see that response I wrote? It is right above your question. It even has a link to click!
-
Uhm, I just change the files on my harddisc using Wordpad and upload it again... Not necessary then!
-
That will work too, although you should use notepad, not wordpad.
-
Disagree! Notepad makes everything into one long line and removes all the <enters>, etc. and the file no longer works. I don't have that problem using Wordpad.
-
Here's a long list of editors to argue about ;)
-
find100
Posted 1 year ago #I had the same problem, this is often caused when wordpress is installed by fantastico through cpanel.
All I did was, ftp'd my site, went into the themes folder and into the related theme, then CMOD all files to 755 (some servers you may need to 777 them).
Log back into your dashboard and you should be able to edit themes.
-
I don't know if anyone noticed, but since 2.3.1 everything seems to be writable from the dashboard and I can't seem to found the settings to make them not-writable anymore. If I put a theme (for example) on read for owner, group and others, write for noone and execute for all, I can still edit that theme from the dashboard. If execute is marked out, the theme cannot be used, so that's not it. Am I looking at the wrong sollution?
-
You'll want to set
writetoowner. Numerically, use755.If you can still edit your theme from within the WordPress admin interface, even with the files at
755, then the problem probably lies with your server configuration and you'll want to contact your hosting's tech support. -
Ok. But it's weird, there was no editing in older versions and now suddenly all is 'editable' and I can't set them to no-editing anymore (and of course I didn't do anything in the control panel when upgrading).
-
I read on the internet that a file can have settings for rights which you cannot 'downgrade' after uploading, so if a file is already 777 when it's upload it, you cannot set it back to 755 or so. Does this sound credible? If it is, the upgrade could have something to do with it (however the WP upgrade of course doesn't change the themes or plugins...). I will have a look at this when I am home.
-
FLEB
Posted 1 year ago #I read on the internet that a file can have settings for rights which you cannot 'downgrade' after uploading, so if a file is already 777 when it's upload it, you cannot set it back to 755 or so. Does this sound credible?
There is a situation where this can happen. Normally, when you upload files via FTP, the "owner" of the file is you-- the username of your account. Therefore, if the settings are such that the owner of the file has write access, you can write, delete, and have control over the file. This is usually the case with Web files-- the owner is allowed read/write access, while everyone else is given read-only access (so the web-server can serve the files, for instance, but not write to them).
If you use a web-based uploader, though, it's not your account that's placing the file there (as it would be through FTP). The file's data is actually being fed into the web server program, which then writes the file. Most times, to preserve security, the Web server runs as a distinct user (often named nobody), and when the web server places a file, that user, nobody, is considered the owner.
Here's the catch: If the web-server creates the file as Writable only for the owner, that "owner" isn't you when you log in via FTP, later on. You can end up with a file in your webspace that you can see, but that you can't delete or CHMOD. The solution is often to create simple and temporary server script to set the files to be world-writable. That "world" includes your FTP user, and gives you access to the file.
It's doubtful that this caused your problems, although what might have happened is that your upgrade process cleared the "world-writable" flag on some files that were set as such in the last version, making them unwritable by the webserver user. This is something you could probably remedy using your FTP client.
-
Thanks for the lengthy reply! The forum that I read this in proved to be talking about WS_FTP pro in which you can set make the settings before uploading the file. I use some free and ancient WS_FTP with no such function. I cannot find how to make CHMOD settings for files on the harddisc, so I can hardly imagine that this would actually be the issue. What is more, when I go to my control panel, I can change the settings without problems, I can even make a folder thus, that I cannot upload anything into it anymore, so that seems to be fine too. The problem is that WP doesn't care if a file is read only or write and the admin-panel allows me to edit them in any setting. I've tried to block that by trial and error, but without succes so far. I hope I will think of another possibility to try out.
-
Hm, none found. Any suggestions anyone?
Topic Closed
This topic has been closed to new replies.
