| 开发者 |
bearsthemes
minhphamit |
|---|---|
| 更新时间 | 2026年10月28日 15:14 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
beplus-performance-booster folder to /wp-content/plugins/.No. Every optimisation hook is guarded by is_admin() and an additional check that
skips users with the manage_options capability on the front-end.
Add a URL keyword for your theme's main stylesheet to the Exclude CSS Files textarea. That file will be loaded normally while the rest are deferred.
Your server's file permissions do not allow PHP to write to .htaccess. Set the
file to 644 (or ask your host) and try again, or add the rules manually.
In wp-content/uploads/bepluspb-cache/ — inside your wp-content directory. The directory
is created automatically with an index.php stub (to prevent directory listing) and
a .htaccess stub (to block direct PHP execution).
No. The WooCommerce asset-removal option is only applied when WooCommerce is active. All other features work independently.
Yes. The .htaccess browser-caching rules complement full-page caches (LiteSpeed Cache, W3 Total Cache, WP Super Cache, etc.). The JS/CSS optimisations operate at the PHP output level and work with most caching setups.
The uninstall.php script removes all plugin data: the bepluspb_settings option, the
injected .htaccess rules, every file in uploads/bepluspb-cache/, and the
_bepluspb_disable_cache post meta from every post.
This plugin is developed and maintained by BePlus, a WordPress and Shopify development studio. You can learn more about our work at beplusthemes.com.
type
(e.g. module) plus integrity, crossorigin, nonce, and
referrerpolicy attributes when the script is restored after user
interaction. Previously these were dropped, which could break ES
module scripts and scripts protected by Subresource Integrity or a
nonce-based Content-Security-Policy.users group)
or the update-count indicator (site-transient group) through Redis
could corrupt on read-back. Both groups are now kept out of the
persistent Redis cache. If you already had Object Cache enabled,
clear/flush your Redis cache once after updating to remove any
already-corrupted entries.install_dropin() no longer installs the Object Cache drop-in
on a site with no valid saved configuration, which could previously
crash the entire site.Requires PHP raised to 8.1 (7.4 reached end-of-life in
November 2022 and no longer receives security patches). No functional
changes.realpath() and verifies they stay inside wp-content/site root, and only
ever resolves genuine .css/.js asset URLs. Previously a crafted asset
URL containing ../ could point the resolver at files outside the intended
directory, or at a non-asset file inside the site root (e.g. wp-config.php)
that could then be read and cached. Defence-in-depth: asset URLs come from
registered themes/plugins, so exploitation required elevated access, but the
resolver is now strict regardless..htaccess file is now backed up once
(.htaccess.bepluspb-bak) before this plugin first inserts its
browser-cache/compression rules, so the original can be restored if a write
is ever interrupted.wp-content/.bepluspb_oc.json), which
can contain a plaintext Redis/Memcached AUTH password, is now blocked from
direct HTTP access via an auto-generated .htaccess rule in wp-content/
(Apache/LiteSpeed). Previously this file was served directly if requested.
Sites on nginx should add an equivalent location ~ /\.bepluspb_oc\.json { deny all; }
rule manually, since nginx does not read .htaccess files.allowed_classes => false, preventing PHP Object Injection if a cache
value is ever read back in a tampered or unexpected state.0 = user interaction only.<img> and <picture> elements.