Cannot Deactivate due to chmod

  • Resolved Tony G

    (@starbuck)


    3 years, 2 months ago

    On attempt to temporarily de-activate the plugin, there are three errors reported that “chmod(): Operation not permitted”. I’ve re-hosted this environment and the permissions have changed from installation time.

    This is a request for information about:

    1) What permissions need to be changed to deactivate.
    2) Are similar permissions needed to activate?
    3) What’s happening with this?

    And this is a simple FYI in case this is not designed behavior.

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Darrel

    (@johndarrel)

    3 years, 2 months ago

    Hi Tony,

    Thank you for your question.

    For the config file, you need write permission if you want the plugin to be able to write the rules itself. The temporary basic permission would be 0640 for the config file.

    If you don’t have write permission, you will get the rules to add manually.

    John

    Thread Starter Tony G

    (@starbuck)

    3 years, 2 months ago

    I spent hours trying to debug this. It was failing to chmod on .htaccess. I changed perms manually between 660, 640, 755, and others. At some point that error was no longer occurring – maybe after I used 777 just to see if it would work. I could see the perms changed by the plugin back to 755, and details added to .htaccess by this plugin were cleared on Deactivate, but the plugin remained activated according to WP.

    Ultimately I had to give up. I moved the hide-my-wp folder out of the plugins folder, refreshed the WP admin page to see the plugin was gone – and WP deactivated it because the folder was missing. Then I copied the folder back and saw that it was deactivated from the WP perspective. After this I could activate AND deactivate it again.

    I have no idea what was wrong but the issue is gone now. HTH
    Thanks for your time.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Cannot Deactivate due to chmod’ is closed to new replies.