#40 WP plugins in ss-clean and blacklist.txt integration

[Anonymous]

Originally created by: Bronislawsky

Example : I use a custom blacklist because I need to white-list a plugin, say 'easy-wp-smtp'
PLUGIN_BLACKLIST_SOURCE="path to my custom blacklist.txt"

Within ss-clean there is a hardcode
rm /var/www/html/wp-content/plugins/easy-wp-smtp* ## blacklist risk (smtp)

Should not there be instead a

for blacklisted_plugin
rm blacklisted_plugins

This would enforce the blacklist and permit custom blacklist.

[Anonymous]

Originally posted by: jessuppi

@Bronislawsky Thanks for the suggestion. In all likelihood, there will always remain a certain list of plugins that are "hardcode" disallowed to avoid conflicts with SlickStack. The question is more really defining the categories of plugins that this applies to, which is a work in progress:

https://slickstack.io/faq/blacklisted-plugins

It is a balance trying to keep things as open as possible by default, while still settling on a philosophy and best practices that SlickStack wants to evangelize.

SMTP plugins might be one category that we end up allowing again since it speaks toward avoiding censorship and email API monopolies. Others, like cache plugins, will always be deleted.