Multisite problem

Added info: installation writes nothing into mu-plugins, which seems otherwise sound. Could some earlier backfire have written something into db to prevent this? Also, I went back to a previous working prototype to see that the subsites were all of format: *.example.com – that is, there were no subsites having their own domain name like my current site. I’ll try to test that out when I can.

• This reply was modified 1 month, 3 weeks ago by joefryfoto.

Hi @joefryfoto

thank you for reporting this issue and for the information.
Can you help me better understand the issue?

This is what I understand:

• You have a multisite installation
• From the admin top bar you go to My Sites => Network Admin => Plugins (that should have an URL that looks like https://yoursite.com/wp-admin/network/plugins.php
• You click on “Network activate” on the action link of Freesoul Deactivate Plugins
• You see the message “Freesoul Deactivate Plugins can’t be activated networkwide, but only on each single site.”

Is it right until here?

After you see that message I suppose FDP is kept disabled on the network, right?

Then you go to the plugins page of a subsite, and for Freesoul Deactivate Plugins you see “Network only” and you don’t see the action link “Activate”. Is it right?
And it is not possible to activate Freesoul Deactivate Plugins, right?

But on another multisite installation you were able to activate FDP on each subsite, right?

Please, correct me if I’m wrong.

About your sentence “installation writes nothing into mu-plugins“. If you are not able to activate FDP, this is totally normal. FDP writes into the folder wp-content/mu-plugins only if you activate it.
Please, let me know if you were able to activate FDP at least on a subsite of the network.

If I haven’t understood the issue, please add more details to help me better understand it.

In the meantime, I will do some tests with multisite installations taking into account also your last comment. I can anticipate that FDP doesn’t guarantee it works with different domains. The domain has to be only one.

Have a great day!

Jose

Jose everything you stated is correct. I thought I’d made a breakthrough and the problem was cookie-related, but I think I read something wrong, so I edited this comment.

• This reply was modified 1 month, 3 weeks ago by joefryfoto.

Hi @joefryfoto

I checked the code of the WordPress core, and it seems you can see the sentence “Network only” only if in the main comments of the plugin main file you have “Network: true”. In no other way. I think you can stop to investigate about cookies and so on.

Here the main comments of the main file of Freesoul Deactivate Plugins of the previous version 2.2.6:

<?php
/**
 * Plugin Name: Freesoul Deactivate Plugins
 * Plugin URI: https://freesoul-deactivate-plugins.com/
 * Description: Disable plugins on specific pages for performance improvement and support in problem-solving even when you have many plugins.
 * Author: Jose Mortellaro
 * Author URI: https://josemortellaro.com
 * Domain Path: /languages/
 * Text Domain: freesoul-deactivate-plugins
 * Version: 2.2.6
 *
 * @package Freesoul Deactivate Plugins
 */

You can see it here: https://plugins.trac.www.ads-software.com/browser/freesoul-deactivate-plugins/tags/2.2.6/freesoul-deactivate-plugins.php

As you can see nowhere you see Network: true. This was working right.

Also the versions < 2.2.6 were working right.

Don’t ask me why because I have to admit that I don’t know it, and I’m also surprised to see it, the last official version 2.2.7 has the comment “Network: true”. You can see it here https://plugins.trac.www.ads-software.com/browser/freesoul-deactivate-plugins/tags/2.2.7/freesoul-deactivate-plugins.php

The issue you are experienced is caused by that comment line, nothing else. Probably in your other installations you hadn’t version 2.2.7. This will be fixed with the next release. If you want, you can edit the plugin’s main file and remove the line “Network true” to fix the issue before the next release.

I hope it helps.

Have a great day!

Jose

Jose, that worked – thanks much for the quick fix! Is it possible my other site worked on 2.2.7 because I installed 2.2.6, got in the door, so to speak, and then when I upgraded to 2.2.7, the presence of Network:true didn’t matter? If so that would explain everything. Another question: around the time I was installing and reinstalling, I had a Wordfence Server-state warning crop up. Any chance this could have been related, or unlikely?

Thanks again for the great product and quick fix!

Server-state issue in Wordfence seems a false alarm. It looks like it appears because Freesoul creates a directory .tmb outside the normal WordPress installation, even though it is within the WordPress root directory. To prevent getting a Wordfence server-state warning flag, you must go to All Options / Scan Options, check “Scan files outside your WordPress installation” and save.

Jose, does the fact that this folder is 777 make it risky in a multisite scenario? (It’s empty, but I don’t know if it gets used).

Hi @joefryfoto

you are welcome! I’m happy it worked.

About the WordFence alarm, I can only say that Freesoul Deactivate Plugins doesn’t write any .tmb directory outside the WordPress installation.
It writes the file wp-content/mu-plugins/eos-deactivate-plugins.php, and the folder wp-content/uploads/FDP. Inside the FDP folder, it stores its cache and writes its settings. Nothing else.

Are you sure the .tmb is not written by something else?

Have a great day!

Jose

You’re right – the .tmb is being written due to another plugin. Thanks again for the help and a great plugin!