WordPress.org
Get WordPress

Plugin Directory

Changeset 3210076


Ignore:
Timestamp:
12/18/2024 07:38:23 PM (15 months ago)
Author:
lorro
Message:

Update to v2.0.0

File:
1 edited

Legend:

Unmodified
Added
Removed

  • simple-plugin-selector/trunk/readme.txt

    r3070734 r3210076  
    22Contributors: lorro
    33Tags: plugins, performance
    4 Requires at least: 5.6
    5 Tested up to: 6.5
    6 Requires PHP: 7.3
    7 Stable tag: 1.3.2
     4Requires at least: 6.2
     5Tested up to: 6.7.1
     6Requires PHP: 7.4
     7Stable tag: 2.0.0
    88License: GPLv3
    99License URI: https://www.gnu.org/licenses/gpl-3.0.html
    … …  
    1515By default, WordPress will load every plugin on every page. The Simple Plugin Selector (SPS) plugin allows the administrator to select which plugins are used on a page-by-page basis. This prevents unneeded plugins and plugin support files from loading. HTTP requests and download size will be reduced, so improving website performance for the visitor.
    1616
    17 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.
     17For 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, so your users don't download your contact form style sheets and scripts unnecessarily.
    1818
    1919The plugin has a user-friendly interface, so the administrator can see easily which plugins are running on each page.
     20
     21Plugin filtering is disabled in admin context.
    2022
    2123Not for newbies! The administrator must have a clear grasp of which plugins are required for each page, otherwise some pages will have errors because a required plugin is not loaded.
    … …  
    2527Load and activate the plugin in the normal way at Dashboard > Plugins > Add New
    2628
    27 Once activated, the plugin will copy its files to the /wp-content/mu-plugins directory. Code in mu-plugins runs before normal plugins are loaded. That's why the plugin filter code must be run from there.
     29Once activated, the plugin will copy its plugin filter file to the /wp-content/mu-plugins directory. Code in mu-plugins runs before normal plugins are loaded. That's why the plugin filter file must be run from there.
    2830
    2931== Deactivating ==
    3032
    31 Deactivating SPS in the normal plugins list will deactivate plugin filtering and remove SPS files from mu-plugins.
     33Deactivating SPS in the normal plugins list will deactivate plugin filtering and remove the SPS file from the mu-plugins directory.
    3234
    33 Removing the SPS plugin using FTP will leave unwanted SPS files in mu-plugins, but plugin filtering will be disabled.
     35Removing the SPS plugin using FTP will leave an unwanted SPS file in mu-plugins, but plugin filtering will be disabled.
    3436
    35 SPS settings are not deleted by deactivation or deletion. Reactivating should pickup filtering where it left off.
     37SPS settings are not deleted by plugin deactivation or deletion. Reactivating should pickup filtering where it left off.
    3638
    3739== Settings ==
    … …  
    6163Yes.
    6264
    63 = Will it work with Polylang =
     65= Will it work with Polylang or with WPML (Wordpress Multilingual Plugin) =
    6466
    65 Yes, from SPS v1.0.4
    66 Not tested with the premium plugin: Polylang for WooCommerce.
    67 
    68 = Will it work with WPML (Wordpress Multilingual Plugin) =
    69 
    70 Not tested with the premium plugin WPML.
     67Not tested with Polylang or the premium plugin WPML.
    7168
    7269= Will it work on multi-site installations? =
    … …  
    9188== Changelog ==
    9289
     90= 2.0.0
     91* Fixed a bug in settings. Users of previous versions will need to redo their settings.
     92* Updated the code to meet WordPress security requirements
     93* Tested with WP 6.7.1
     94
    9395= 1.3.2 =
    9496* Tested with WP 6.5.2
    … …  
    99101
    100102= 1.2.0 =
    101 * Support for Tags, Product Tags and Product Attributes withdrawn as too buggy.
     103* Support for Tags, Product Tags and Product Attributes removed as too buggy.
    102104* Tested with WP 5.8
    103105
    … …  
    113115= 1.0.4 =
    114116* Amended to work on with Polylang sites where language codes are embedded in page urls.
     117(This feature is no longer supported as it proved to be too buggy)
    115118
    116119= 1.0.3 =
    … …  
    122125== Upgrade Notice ==
    123126
    124 = 1.3.2 =
    125 Tested to work with WP 6.5.2
     127= 2.0.0
     128* Fixed a bug in settings. Users of previous versions will need to redo their settings.
     129* Updated the code to meet WordPress security requirements
     130* Tested with WP 6.7.1
Note: See TracChangeset for help on using the changeset viewer.