WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


This is a question that has bugged me for a really long time and I realize this it isn't necessarily related to WordPress, however I wanted to start by asking the WordPress community. I've been selling WordPress themes for a couple of years now and this is an issue that has come up repeatedly in dealing with customer support but have never really known how to address it, or if it's something I'm doing wrong or not.

The problem that leads me to ask

Every once in awhile when someone installs one of my themes, they decide to go the route of unzipping it and manually uploading the theme folder to wp-content/themes/ of their site with their FTP client.

When people do this they often run into the same issue and it is this: Things on their site will end up not working because it ends up turning out that there are certain files of the theme that when uploaded received permissions that are not readable on their web server...

For example maybe a javascript file doesn't have readable file permissions, so it it's as if it doesn't exist on the front end of their site when called in the head of the site, and thus breaks all the javascript on the frontend of their site.

For the longest time I've chalked this up to inexperience on the user's part. I tell them to change the file permissions with their FTP program. They figure out what the heck that means, and all is right.

However this is continuing to happen to people, and I'm having to give the same responses again and again. Now I'm starting to see more of a pattern with which files it's happening to for people and seeing that it's the same files again and again.

Another thing to note is I've noticed that this happens the most with files I've pasted into the theme. For example, I include the pretty photo jQuery plugin where I've just pasted the folder from prettyPhoto in there and users often end up with the pretty photo CSS and JS file that have non-readable file permissions.

My Question

I understand that users are not experienced with troubleshooting these issues and are not savvy with finding a file that has been give improper permissions, but the fact that users keep facing this with the same files leads me to believe that this is something I'm doing on my end with the files.

So, is this possible? What theoretically could I being doing with plain 'ol CSS, JS, and PHP files on my end that could result in a user uploading the theme on their end with these certain files receiving weird file permissions?

System Info

I'm not sure if this is relavant or not, but I do all my work with these files in Coda on Mac OS 10.7, working with MAMP on my localhost.

share|improve this question

closed as off topic by Wyck, kaiser, Rarst Sep 28 '12 at 19:01

Questions on WordPress Development Stack Exchange are expected to relate to WordPress within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

You could rework your question and try to get a plugin out of that. It could check file permissions and give the user output & info & guidance. – kaiser Sep 26 '12 at 11:59

The unfortunate answer is that I don't think there's anything you can really do to prevent this.

Assuming we're talking about a Linux based server as the destination for your theme, the umask settings for the ftp user determines the permissions for new files, such as a fresh upload of your theme's files.

It also could be affected by whether or not the ftp user being used to upload the files (who will also be the owner of the file) is the same as the user running WordPress or in the same group. However if there is any sanity in their server setup all those files should be readable by all users, but it sounds like your issues with JavaScript files suggest that isn't the case.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.