Descripció
By default, WordPress will load every plugin on every page. SPS allows the webmaster to select which plugins are activated on a page-by-page basis. This prevents page loads including plugin support files which are not needed for that page. This reduces HTTP requests and download size, so improving website performance for the visitor.
For example, you probably use your contact form plugin only on your Contact Us page. SPS allows you to deactivate it when the page request is for one of your other pages to avoid downloading your contact form style sheets and scripts unnecessarily.
Captures
Settings - Disable / Enable the plugin 
Settings - Set plugin type: Always / Never / Sometimes 
Settings - Set plugin loading per page for "Sometimes" plugins 
Settings - Set plugin loading per post for "Sometimes" plugins
Instal·lació
Not for newbies! The webmaster must have a clear grasp of which plugins are required for which pages, otherwise some pages will have a bunch of errors because the relevant plugin is not loaded.
Using FTP or your host’s file manager system, check for the sub-folder wp-content/mu-plugins and create this subfolder if it doesn’t exist. Upload the SPS folder, simple-plugin-selector.php file and readme.txt into this folder. If you can’t find wp-content, it may have been renamed.
SPS is always-on, so there is no need to enable via admin and users cannot deactivate it by accident.
Plugins in the must-use directory will not appear in the update notifications nor show their update status on the plugins page, so you are responsible for learning about and performing updates on your own.
Settings
Go to Dashboard > Settings > Simple Plugin Selector to set which plugins you would like to activate on a page by page basis.
If a new page, post or product is created, all plugins will be activated for that by default until set by SPS settings.
If a new plugin is activated, it will be loaded for all pages by default until set differently by SPS settings.
There is a setting to deactivate SPS for debugging. To delete the plugin, remove its files using FTP.
PMF
-
How much faster will my site run?
-
The degree of improvement will vary between sites. Users with slow connections are likely to see a big improvement.
-
The theme customizer is not working properly
-
The page inside the customizer is working in front-side context. If there is a plugin which is set to not load on the front-side page, then it won’t be available to the admin-side customizer either. Temporarily disable the plugin filter in SPS settings while using the customizer.
-
Will it work with WooCommerce
-
Yes.
-
Will it work with Polylang
-
Yes, from SPS v1.0.4
Not tested with the premium plugin: Polylang for WooCommerce. -
Will it work with WPML (WordPress Multilingual Plugin)
-
Not tested with the premium plugin WPML.
-
Will it work on multi-site installations?
-
Not tested on multi-site installations.
-
It works on some pages but not others
-
If you create a new page, post or product, SPS does not make assumptions about which plugins are needed for it, so SPS will load all plugins. Run through the settings screens to set plugins for any new pages, posts or products.
-
It doesn’t work at all
-
SPS won’t work if permalinks are set to “Plain”
Ressenyes
Col·laboradors i desenvolupadors
«Simple Plugin Selector» és programari de codi obert. La següent gent ha col·laborat en aquesta extensió.
Col·laboradors
Tradueix “Simple Plugin Selector” a la teva llengua.
Interessats en el desenvolupament?
Navegueu pel codi, baixeu-vos el repositori SVN, o subscriviu-vos al registre de desenvolupament per fisl de subscripció RSS.
Registre de canvis
1.2.0
Support for Tags, Product Tags and Product Attributes withdrawn as too buggy.
Tested with WP 5.8
1.1.1
Fixed minor bug that occured infrequently.
1.1.0
Added support for post, category and tag pages.
Added support for WooCommerce pages: products, product categories, product tags and product attributes.
Added “Copy settings” button on page settings tabs to make settings easier.
Added pagination of long page lists in settings.
1.0.4
Amended to work on with Polylang sites where language codes are embedded in page urls.
1.0.3
Amendments to meet WordPress.org guidelines.
1.0.2
Submitted to WordPress.org for review.