Skip to:
Content
Pages
Categories
Search
Top
Bottom

[RESOLVED] I did a CHMOD to wp-content (644 -> 777) and now my blog logins are busted

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

  • Paul Wong-Gibbs
    Keymaster

    @djpaul

    Oh, my.

    Changing the chmod of wp-content to 777 won’t actually *break* your site, but maybe something else happened at the same time. I’d suggest popping into the multisite forums at WordPress.org, and searching/asking for anything similar.


    Hugo Ashmore
    Keymaster

    @hnla

    > I read somewhere that the wp-content directory should be be 777

    Not sure where you read that but no directories should ever be world writeable it’s dangerous, insecure and completely unnecessary. Change those perms back and instead look at how your group/owner is set for site folders – 644 is going to b far too restrictive you need 775 but also the correct group and user able to write to these dirs/files


    online
    Participant

    @online

    Yea, thanks both — I can’t figure out what I did wrong. I think maybe I put the domain mapping in mu-plugins, and then *after* the problem started I move it into plugins, but even if that doesn’t matter, I think there are simply too many variables in play. It’s a relatively new install, so I think I will just do it over. Will use 775, thanks. :)


    online
    Participant

    @online

    I wanted to say that I found the problem (but only after re-installing :/ )

    It was that I had decided to use the activity stream as the homepage (which apparently doesn’t work?)

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[RESOLVED] I did a CHMOD to wp-content (644 -> 777) and now my blog logins are busted’ is closed to new replies.
Skip to toolbar