Hi @mubiesam
you are welcome!
FDP works as explained in the other support forum for multisite installations. If you need to deactivate plugins with FDP you need to activate each plugin on every single site, not globally on the Network.
Excluding some cases, for me, activating plugins on every single site is also better than activating them on the entire network.
One of the advantages of a multisite is that if you update a plugin, you don’t need to do it for every single site. But you still have this advantage also if the same plugin is deactivated on some sites of the network.
If you activate each plugin on every single site it’s also easier when you have to debug something, but also without FDP. Imagine you have a problem only on one site, and you need to disable a plugin to see if it’s the cause of the problem.
If that plugin is globally active on the network, you have to disable it for all the sites, and sometimes this may mean brake some pages of some sites that absolutelly need that plugin.
And I don’t see cons if you activate the plugins on each site. You have only more work when you create a new site, but I don’t think you frequently manually create new sites.
But this was just my opinion that has nothing to do with FDP.
About FDP, the actual version works only as explained before for multisite.
So, if you need to use FDP, you have no other way. FDP doesn’t see the plugins that are globally active on the network.
Maybe in future versions, you will have the possibility to see also the globally active plugins on the network, but the current version doesn’t give you this possibility, and I can’t say if and when this will change.
Have a great day!
Jose
