Hi Deepak
this is because many times you want to disable the plugin only for the locked rows.
FDP automatically locks the row if you disable/enable a plugin on that row because it assumes you want specific settings on that row. But if you deactivate a plugin on an entire column, you may want to deactivate it only on the locked rows.
If on that page you have only 100 posts, you can click on the button “Lock all”.
I suppose you don’t need the same plugins on those 100 posts or you have other posts where you need different settings. In another case, it would be better to use the options “Post Types”.
@golinuxcloud
Thread Starter
Deepak
(@golinuxcloud)
Hello Jose,
Thank you for your response.
I would assume that if I am using “Activate/Deactivate All” then I would like to disable the plugin on all the selected posts (independent of the lock status) and this action should further lock the post.
Assuming if I have 1000s of post wherein on 500 posts I want to disable a plugin which I select via bulk edit but then I don’t have an option to disable a plugin on this list unless I manually lock them so it would be hectic to lock every post one by one
For example I have multiple posts with “table” plugin but “Post Type” can’t get this list. The only way for me to disable this table plugin is to do a search and shortlist the posts and then do bulk edit.
I hope you can think of a better solution but I feel if I choose to “deactivate all” for a plugin then I definitely want to lock the selected post and make the changes.
You are welcome @golinuxcloud
Probably I haven’t fully understood or maybe you haven’t seen the button “Lock all”.
I understand you want to do the equivalent of “Activate/Deactivate All” + “Lock all”. So you should disable the plugin on the entire column and then click on “Lock all”.
Thread Starter
Deepak
(@golinuxcloud)
Thanks Jose.
Okay sorry, I didn’t checked there was an option to “Lock All” so we should use that before using “Activate All”
But I believe many others would also face this 🙂
As because I assumed just doing “Deactivate All” would have locked and deactivated. But I know the secret now so I will be cautious going forward.
But it would be good if this behaviour is informed somehow? As luckily I was inspecting one of my pages and realised one of the plugin was not disabled and then I started analysing. 🙂
You are welcome.
If you deactivate a plugin on an entire column, you may want to deactivate it only on the locked rows. This is why you have the button to lock and unlock all.
Many users disable the plugins by post type and then use the Singles settings to change the settings on a few posts. I know this is not your case, but in that case, if you disable a plugin on the entire column you don’t want to lock all the rows because they would override the Post Types settings.
I know the padlock is sometimes a source of confusion, but it’s needed to assign the priority between Post Types and Singles.
In the Singles settings, you should see the warning “The Post Type Settings are overriding these settings for all the rows that don’t have the closed padlock”. This is how FDP tries to warn the user. Once the user knows the padlock is important to assign the priorities, I think it’s better to don’t lock all the rows when you disable a plugin on the entire column, but have the possibility to do it with the button “Lock all”.
If you want to be sure about the disabled plugins, you have the icon “?”. It’s the third icon that appears when you go with the mouse on the post name. Clicking on that icon you can check which plugins are really disabled. When you have doubts, click on that icon and you will see a popup that shows you the disabled plugins and by which settings.
What I can do is maybe adding a popup after you click on “Activate/Deactivate All” that asks you if you want also to lock the rows. Then, I think everybody would be happy 🙂
Thread Starter
Deepak
(@golinuxcloud)
Thank you so much for the explanation.
Yeah the relation between Post Type and singles is confusing so I prefer to use only singles 🙂
The solution you proposed sounds perfect and should avoid any confusion to anyone with a similar requirement as mine.
Best regards
