In wp-content there are
the subdirectories
cache, languages, plugins, shield (from the plugin shield security), themes, updraft, upgrade, uploads, w3tc-config and
the files
advanced-cache.php, db.php, index.php, object-cache.php and debug.log.
In wp-content/plugins there are
the subdirectories of all activated plugins and the index.php.
If this is what you meant … 🙂
-
This reply was modified 1 year, 10 months ago by Achim Hahn.
So I’d try posting a message to the devs of each of those security plugins to see if their plugin can block plugin deactivations.
Okay, I have allready started with a post in shield security’s support forum.
Thank you very much for your support, Steve!
Also thanks to you, Ramona!
Paul
(@paultgoodchild)
@achimhahn This behaviour you’ve described in \wp-content\shield\ptguard\plugins
is perfectly normal for Shield. It’s part of Shield’s processing and would in no way cause the behaviour you’re outlining here.
@sterndata @nextend_ramona
Strike! I found out what caused the problem!
It was the plugin Query Monitor.
As I tried to activate an installed plugin (health check) and clicked on the option “health check” I got an error message, saying that I dont’t have the right to enter that page.
I add the message here, but it is in German:
Du bist leider nicht berechtigt, auf diese Seite zuzugreifen.
Diese Meldung wurde durch WordPress Core ausgelöst.
Aufrufstapel
wp_die()
wp-admin/includes/menu.php:364
Query Monitor
“Sender” was the plugin Query Monitor.
So I forcefully deactivated it (by renaming the plugin subdirectory) and … everything was fine again. I’m able again to activate/deactivate/delete plugins as usual.
I have not tested, wether it was due to settings of QM or to the plugin itself!
Utterly bizarre! Anyhow, good detective work! I recommend reporting this at https://wordpress.org/support/plugin/query-monitor/#new-post so the plugin’s developers and support community can help you with this.
@sterndata
I posted it in the QM support forum.
Thanks and bye!
@sterndata @nextend_ramona
It was an issue of clearing the object cache.
That solved the problem.