Plugins not disabled for logged in admin

Thank you very much for the information.

Can you please install fdp-debug https://wordpress.org/plugins/fdp-debug/?

After installation when you go with your mouse on a row you will see the button “DEBUG”. Clicking on that button a new tab will open with some information that can help me to investigate the problem.

Before giving me the information, remove all that you don’t want to share.
It will include for example the homepage and the blog page URL. If you don’t want to share them, remove them.
For me, it’s useful what is written in “GENERAL INFO”, “MU-PLUGINS”, “DROP-IN PLUGINS”.

@sagescrub

Thank you very much @sagescrub

So, you have some mu-plugins that may run before the code of FDP.

Can you please update fdp-debug to version 0.0.4 and provide me again Genera Info? Sorry that I ask it again, but I’ve added some information to the new version that may show the root cause of the issue.
I suspect one of the mu-plugins is writing in the superglobal variable $_REQUEST.

Thank you very much @sagescrub

Unfortunately, it’s not enough to find the root cause.
I don’t have any site on WP Engine. Is it a problem for you to send me the mu-plugins installed by WP Engine?
The cause of the issue is very probably in one of those mu-plugins.
If you want to share them privately you can use this contact form: https://freesoul-deactivate-plugins.com/contact/
If you use the contact form, please share a link that points to a folder that contains the files, not directly the code, because the allowed size of the text has a limit.
If you don’t want to share them, let me know and I will suggest how to proceed in a different way.

Hi @sagescrub

thank you very much!

I’ve checked all the mu-plugis. I have seen nothing strange. I’ve installed them on my installation and was not able to reproduce the problem.

I’ve created a little plugin that will give me the information I need to understand what’s going on.
It calls fdp-update-mu-plugin, you can download it from here: https://plugins.trac.wordpress.org/export/2585996/freesoul-deactivate-plugins/branches/fdp-update-mu-plugin.zip

After activation, it will replace the mu-plugin of Freesoul Deactivate Plugins with another one that includes code to write in the log file.
After activation, please do the following:

– Check in the settings page of Freesoul Deactivate Plugins. You should see “Mu-plugin updated by FDP Update Mu Plugin”. This means the mu-plugin that will debug all that we need was successfully installed.
– Enable the debug in wp-config.php with:

define( 'WP_DEBUG',true );
define( 'WP_DEBUG_LOG',true );
define( 'WP_DEBUG_DISPLAY',false );

the code above should be before the comment /* That’s all, stop editing! Happy publishing. */
– Visit the homepage as logged-in without cache
– Take note of what you find in the file wp-content/debug.log
– Visit the homepage as not logged-in without cache
– Take note of what you find in the file wp-content/debug.log
– Disable some plugins on another page. If you have no plugin that you could disable, install Hello Dolly and then disable that plugin
– Visit that page
– Take note of what you find in the file wp-content/debug.log

Then please, report the information collected in wp-content/debug.log specifying which page you have visited for each group of information.

By doing so I feel confident we can find useful information.

The mu-plugin written by fdp-update-mu-plugin is the same as the standard mu-plugin, but it has a lot of error_log() functions in many points of the file. Excluding the log activity, it’s the same as the usual mu-plugin, so you can use it all in a production environment.
After you have finished, if you deactivate fdp-update-mu-plugin, it will restore the original mu-plugin.

If something is not clear, let me know.

Hi @sagescrub

perfect! Thank you very much!

As written in the email, version 1.8.8.7.5 fixes this issue.