WordPress.org

Ready to get started?Download WordPress

Forums

No CHMOD Directory & File Permissions In Documentation (31 posts)

  1. jimnyc
    Member
    Posted 9 years ago #

    Why is there no clear one-stop shopping for the correct permissions for directories and files? There are fragments all through the forums and wiki that tell you what chmod is and how to use it and bits and pieces here and there with maybe this and maybe that for specific files and directories, but there is no one place (that shows up in searches) that illustrates even a starting place for permission assigments. [Comment moderated]

  2. Mark (podz)
    Support Maven
    Posted 9 years ago #

    This is a little story about four people named Everybody, Somebody, Anybody, and Nobody.

    There was an important job to be done and Everybody was sure that Somebody would do it.

    Anybody could have done it, but Nobody did it.

    Somebody got angry about that because it was Everybody's job.

    Everybody thought that Anybody could do it, but Nobody realized that Everybody wouldn't do it.

    It ended up that Everybody blamed Somebody when Nobody did what Anybody could have done

  3. jimnyc
    Member
    Posted 9 years ago #

    The moderation was more like censorship than moderation since the statement illustrates this manifestation of that problem.

    The response is just as cute as it was years ago but still gives no clear instructions. I just checked the MT site and found what is missing here just by clicking on the User Manual and doing a page search for chmod.

    If Anybody, Somebody, know what the specs are one or both or all should just share them upfront so that Everybody will know and Nobody can go back home.

    I am begining to suspect that there is no clear consensus on this and no baseline for cinfigurations has been set.

  4. Mark (podz)
    Support Maven
    Posted 9 years ago #

    IF I have time, and IF I have the inclination , I will do it later.

  5. NuclearMoose
    Member
    Posted 9 years ago #

    There is a code of conduct required when using this board. If you post comments that are likely to start flame wars, then they will be moderated. You can go ahead and bring out the "censorship bomb" but it doesn't wash with me.

  6. natasp
    Member
    Posted 9 years ago #

    sorry for asking a silly n00b quesi, but how do i start a new thread on these support forums once i have logged in..
    ?

  7. Mark (podz)
    Support Maven
    Posted 9 years ago #

    And do you know what jimnyc ??

    It would REALLY help your cause if YOU had been polite and said things like "Please" and "Thank You".

    Do forum helpers get paid ?
    No.

    Did you get a support guarantee when you downloaded WP ?
    No.

    Do I get sick and tired of people comparing WP with MT because MT costs MONEY and WP is FREE
    Too damn right.

    Do posts like your make me seriously think of just jacking in all the support I give ?
    YES.
    Yes it damn well does.

  8. natasp
    Member
    Posted 9 years ago #

    :(
    please..?

  9. jimnyc
    Member
    Posted 9 years ago #

    Thank You!

  10. jimnyc
    Member
    Posted 9 years ago #

    natasp - goto to the top of this page above the Subject of this thread and click on either Installation (to start a new thread in this Theme) or WordPress Support (to pick a different Theme forum). Once there scroll to the bottom of the page and you're there.

  11. natasp
    Member
    Posted 9 years ago #

    many thanks.. jimnyc..

  12. Mark (podz)
    Support Maven
    Posted 9 years ago #

    http://codex.wordpress.org/User:Podz/Permissions

    This echoes the permissions that I have on one blog of mine.

    If you want permissions on 1.5, you can wait until it is released.

    And to jimnyc .... you didn't say Please.

  13. jimnyc
    Member
    Posted 9 years ago #

    Thank You!

  14. jimnyc
    Member
    Posted 9 years ago #

    So summarized the permissions for 1.2 are:

    All directories should be set at 755.

    All files are 664 with the following exceptions:

    666
    /wordpress/index.php
    /wordpress/wp-comments-popup.php
    /wordpress/wp-comments-post.php
    /wordpress/wp-comments.php
    /wordpress/wp-layout.css

    755
    wordpress/wp-content/link-update-cache.xml
    wordpress/wp-content/links-update-cache.xml

    ---
    /wordpress/license.txt
    /wordpress/readme.html
    /wordpress/wp-config-sample.php

    Should these permissions be insufficient check with your Host as this will be due to their security settings.

  15. Mark (podz)
    Support Maven
    Posted 9 years ago #

    And the point of the post above was what precisely ?

  16. NuclearMoose
    Member
    Posted 9 years ago #

    /wordpress/index.php
    /wordpress/wp-comments-popup.php
    /wordpress/wp-comments-post.php
    /wordpress/wp-comments.php
    /wordpress/wp-layout.css

    The above files ONLY need to be CHMOD 666 if you plan to use the WordPress admin panel to edit the files. Otherwise they can be left as is.

  17. jimnyc
    Member
    Posted 9 years ago #

    wonderful - Thank You

  18. NuclearMoose
    Member
    Posted 9 years ago #

    You're welcome. :)

  19. eetdcob
    Member
    Posted 9 years ago #

    Thank you for these permission notes!
    What puzzles me is, that on two installations I've done, on OSX, the PHP scripts do not have execute permissions set, for anybody. I would think they wouldn't work, but they do.

    Separately:
    I also wish the docs were more centralized & filled out.
    I've paid a bit o money by the way & don't mind paying for things I use, so I'm not just complaining. Maybe as I go along things will become clearer, but boy is it nice to have good docs at hand. I really respect good documentation writing. Not the most glamorous job but so important.

    For me, the ease of the first WP installation was such a relief. Someone did a really nice job on the install, you can never have too much comforting feedback. It's the gory details which come after which get confusing.

  20. NuclearMoose
    Member
    Posted 9 years ago #

    Centralized as in this:
    http://codex.wordpress.org/ ?

    Also, what did you find lacking in the documentation? We're always happy to get feedback so that we can make it better.

  21. eetdcob
    Member
    Posted 9 years ago #

    moose > why yes that looks good :) Thank you. I'll be studying it like heck.

    I see no link to it from the Docs page. I switched to view source and searched for codex to be sure. That would be a nice link to have. Or is that link elsewhere on the site? If there's some other link on the Docs page that redirects to Codex I didn't find it.

    Anyway thanks for now!

  22. NuclearMoose
    Member
    Posted 9 years ago #

    Codex is still in development which is why it has only been soft-launched.

  23. eetdcob
    Member
    Posted 9 years ago #

    Again about permissions: on two OSX installations I've done, the PHP scripts do not have execute permissions set, for anybody. Why do they work?

    Is there a better thread in which to ask about documentation? I'm reading Codex carefully. It seems like anyone can add to it, and many parts are blank. Is a remark like "The instructions and examples at the page for the template tag should be self-explanatory" (they aren't) a developer's opinion? Even the process (if there is one) of commenting on docs in Codex is confusing. An authoritative, from-the-source manual is needed. Jimnyc was not well received for saying so, but considering I wouldn't have found Codex from the official WordPress site, he had a point. Podz's remark about Everybody and Nobody suggests that WP is not a product but a community process, in which users (customers, if they've paid) shouldn't express wishes unless they're prepared to write the code. Is that it?

  24. "Codex is still in development which is why it has only been soft-launched." ~ NuclearMoose

  25. paperlion
    Member
    Posted 9 years ago #

    My first install with a new host is misbehaving. Couldn't return to the site from the Admin, and before this (actually the really first attempt) the links would show the correct target urls, but the page would hang (going back and forth to/from the site to the admin, etc.).

    After seeing the recommended permissions (for 1.2.2), the hosting tech suggested the following:

    664 is what the file is set for, that means you can read/write, anyone in the same linux group, can read/write and anyone else can read. 644 might be more appropriate, or 744.

    As the installation isn't working, can someone qualify the settings that are in the links and posts here?

    Also, there was a recommendation for config-sample.php, but not the real one, config.php - I know it's in the Wiki somewhere, but I don't remember where.

    Also, also; (getting tired of hearing myself type PS), can someone suggest any general guidelines for 1.5 permissions - at least if there are any files NOT to set the same way they are downloaded?

  26. NuclearMoose
    Member
    Posted 9 years ago #

    @eetdcob,

    Those remarks were not well-received because of their tone, not because of the question that was being asked. As for not wanting anyone to express wishes, nothing could be further from the truth. The only way more and better documentation will be generated is as a result of feedback from users. However, if a person comes across in a condescending or mean-spirited way, their remarks aren't well-received, as demonstrated in this thread.

    Open source projects ARE a community process, but this community is not exclusionary. I am not a coder, but I have found ways to contribute in spite of that.

    "An authoritative from-the-source manual is needed." you say. Not sure what you mean by that.

    Your comments about the template tags documentation is a perspective which I share. In fact, I would be so bold as to say that Podz would also agree that they need some additional work done on them. This has been discussed within the group of those folks who have volunteered to work on the documents.

    One final point. There are by now, tens of thousands of WordPress users. There are maybe a dozen volunteers working actively on documentation. This is in addition to them having their own site or sites to manage, contributing to other projects, and of course, real life.

    Consider that there are probably ten times as many folks helping out with plugins and code, and you can see why documentation does lag behind. It's not the sexy part of a project, and takes a lot of time and work to get it to a decent level.

  27. Mark (podz)
    Support Maven
    Posted 9 years ago #

    I agree, and I'm the sexy part :)

  28. paperlion
    Member
    Posted 9 years ago #

    :(
    please..?

  29. To get started with permissions, similarly follow Podz' guidelines for v1.2.2 permissions, or try 666 or 755. And, delete config-sample. You don't need it.

  30. eetdcob
    Member
    Posted 9 years ago #

    Moose > I just saw your comments, thank you.

    I really just had a permissions question in the beginning. My PHP scripts do not have execute permissions set, for anybody. They work (yea!) but why? I assumed they would need to be +x (unix environment).

    And back to your post:

    ""An authoritative from-the-source manual is needed." you say. Not sure what you mean by that."

    A manual by the developers. But I see now that the idea of a developer is diffuse here. I don't mind writing docs, but I'm just learning it.

    "I am not a coder, but I have found ways to contribute in spite of that."

    You're listed as a developer. ?

    Well, to blog is interesting, but to have a weekend is divine. Have a good one all.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.