• Hi.

    I’m trying to enable the troubleshooting mode,
    But I failed with the message “We were unable to create the mu-plugins directory”

    First I think it is because I don’t have the directory. So I’ve created mu-plugins directory and changed my wp-admin.php file, as the guideline I found on google. But it didn’t work.
    And second, I think it is because of authorization. So I’ve changed my folders authority to 777 (I know this is dangerous but I just tried) But It failed again.

    I still think that this is because of the authorization problem, but I have no idea at all now.

    Please let me know how to solve this problem.

    • This topic was modified 6 years, 2 months ago by innosys.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Marius L. J.

    (@clorith)

    Hiya,

    the plugin should (if having enough access) be creating the directory for you, and if it is missing some access you should get be getting a form to input credentials, did this not happen for you?

    I’m also curious what changes you made to wp-admin.php, this is a file you shouldn’t be making changes to, so perhaps the changes made to that could be related, but I won’t say that for certain without knowing what was changed.

    Oh, and if you look at the debug information sections, does it report any problems with directory access?

    That’s a lot of questions, hopefully that’s not too offputting, as they’re all individual potential problems that are worth looking into ??

    Thread Starter innosys

    (@innosys)

    Hi.

    Thank you for the reply.

    First of all, I’m sorry that it was not wp-admin, It was wp-config what I have modified. also, the change I’ve made in wp-config.php, it was from this article. but I’ve restored all changes I’ve made, because I think that article is not for my case. So I think that would not be a problem.

    And for ‘the plugin should (if having enough access) be creating the directory for you, and if it is missing some access you should get be getting a form to input credentials, did this not happen for you?’
    I didn’t get any message.

    But as you said, I’ve checked the debug information section, I found that both ‘the plugins’ and ‘The Must Use Plugins’ directories are ‘Not Writable’ state.
    I don’t know how to change it to ‘Writable’ state.??

    • This reply was modified 6 years, 2 months ago by innosys.
    Plugin Author Marius L. J.

    (@clorith)

    There are two things that determine if the directories are writable, if you are only getting a message about us not being able to copy files, and that’s it, the likely scenario is that the permissions on the directory are wrong.

    I’m not sure if you’re familiar with FTP software, or if your web host perhaps has some kind of file editor you can use, but what you want to do is navigate to the wp-content/ directory, there should be a folder named mu-plugins there (if there isn’t, create it your self). Make sure the folder permissions are set to something like 750 (if it uses numbers), or if it’s just checkboxes:

    
    User: Read, Write, Execute
    Group: Read, Execute,
    World: <nothing>
    
    Thread Starter innosys

    (@innosys)

    I use FTP software and all my permission settings were 755 for the directories, 644 for the files now. I heard that this is recommended setting from WordPress.

    I changed my mu-plugins directory permissions to 777, after reading your reply, now the debug information section says ‘writable’. and now the error message has been changed to like ‘We were unable to copy the plugin file required to enable the Troubleshooting Mode.’.
    It seems like this error is about the permissions of files, just the same as the error occurred in the directory. right? If it’s right, isn’t it too dangerous to set my files and directories permissions to 777 since anyone would be able to read, write, execute?

    • This reply was modified 6 years, 2 months ago by innosys.
    • This reply was modified 6 years, 2 months ago by innosys.
    Plugin Author Marius L. J.

    (@clorith)

    Yes, you should not be using 777 anywhere. I’m afraid I don’t have any good ideas here as to why you are seeing that message then, you should have been presented with a form to provide FTP details at the very least if it was stuck… hmm

    What page are you on when receiving this notice?

    Thread Starter innosys

    (@innosys)

    Here is the screenshot of the page.
    https://drive.google.com/file/d/1keIDFUFN9SG86Z8tDdcjyytGYUGp27fu/view?usp=sharing

    It’s just shown to me when I clicked the Enable Troubleshooting Mode button.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘“we were unable to create the mu-plugins directory”’ is closed to new replies.