Saltar al contenido principal
MeteorGPLby WebbingApps
LT

LiteSpeed Cache

Plugin
Seguir 0 Dar estrella 0
Instalar

All-in-one unbeatable acceleration & PageSpeed improvement: caching, image/CSS/JS optimization...

  • 0 estrellas
  • 0 seguidores
  • 0 descargas
  • Licencia no declarada

Versiones 0

Las más recientes primero · cada versión se analiza antes de publicarse
Mostrar 72 versiones aún no disponibles

Lanzamientos que figuran en el registro de cambios del proveedor o en WordPress.org y que el repositorio aún no tiene.

  1. 7.9.1 Aún no disponible

    Publicado en WordPress.org

  2. 5.3.2 Aún no disponible

    Object Fixed object cache lib incr, decr functions (thanks bdrbros/DANIEL) #516

    Entrada del registro de cambios

  3. 5.3.1 Aún no disponible

    CLI Presets feature is now usable from the CLI. (xLukii)

    Entrada del registro de cambios

  4. 5.3 Aún no disponible

    🌱Presets New Presets feature and menu item.

    Entrada del registro de cambios

  5. 5.2.1 Aún no disponible

    🐞Core Fixed a fatal error that occurred when uninstalling. (#894556 Hostinger)

    Entrada del registro de cambios

  6. 5.2 Aún no disponible

    🌱UCSS Added UCSS message queue to improve service quality and reliability

    Entrada del registro de cambios

  7. 5.1 Aún no disponible

    🌱Toolbox Debug log can now show Purge/Crawler logs as well. (Tynan)

    Entrada del registro de cambios

  8. 5.0.1 Aún no disponible

    🐞Cloud Fixed a potential PHP error that could occur with the cloud service summary. (Bruno Cantuaria)

    Entrada del registro de cambios

  9. 5.0.0.1 Aún no disponible

    🔥🐞Cloud Fixed an issue with the cloud request timestamp update which causes a usage sync failure. (great thanks to Kevin)

    Entrada del registro de cambios

  10. 5.0 Aún no disponible

    🌱VPI Added Viewport Images feature to LiteSpeed Options metabox on Post Edit page.

    Entrada del registro de cambios

  11. 4.6 Aún no disponible

    Page Optimize Improved compatibility for JS Delay.

    Entrada del registro de cambios

  12. 4.5.0.1 Aún no disponible

    🔥🐞Media Fixed an issue where lazy-loaded images would disappear when using custom CSS image loading effects.

    Entrada del registro de cambios

  13. 4.5 Aún no disponible

    🌱Page Optimize Localization is back.

    Entrada del registro de cambios

  14. 4.4.7 Aún no disponible

    Page Optimize Dropped Inline Lazy Load Images Library option. Now will always inline lazyload library. (Ankit)

    Entrada del registro de cambios

  15. 4.4.6 Aún no disponible

    Guest Restored document.referrer for organic traffic purposes when Guest Mode is enabled. (michelefns)

    Entrada del registro de cambios

  16. 4.4.5 Aún no disponible

    Data Fixed potential PHP notice when generating CSS/JS optimized files w/ PHP v7.4+. (Sarah Richardson/silencedgd/slr1979)

    Entrada del registro de cambios

  17. 4.4.4 Aún no disponible

    Page Optimize Delay deletion of outdated CSS/JS files for a default of 20 days to avoid 404 errors with cached search engine copies.

    Entrada del registro de cambios

  18. 4.4.3 Aún no disponible

    🐞Media Fixed an issue where WebP is served erroneously under Guest Mode on older versions of Safari. (hash73)

    Entrada del registro de cambios

  19. 4.4.2 Aún no disponible

    Purge In order to clear pages containing 404 CSS/JS, the purge header will always be sent even in cases where purge must be delayed.

    Entrada del registro de cambios

  20. 4.4.1 Aún no disponible

    🐞ESI Fixed ESI failure on non-cached pages caused by DONOTCACHEPAGE constant.

    Entrada del registro de cambios

  21. 4.4 Aún no disponible

    🌱Crawler Added the ability to enable or disable specific crawlers. (⭐ Contributed by Astrid Wang #PR390)

    Entrada del registro de cambios

  22. 4.3 Aún no disponible

    UCSS Separated UCSS Purge from CCSS Purge. (⭐ Contributed by Alice Tang #PR388)

    Entrada del registro de cambios

  23. 4.2 Aún no disponible

    Cloud Auto redirect to a new node if the current node is not available anymore.

    Entrada del registro de cambios

  24. 4.1 Aún no disponible

    🌱UCSS/CCSS/LQIP Moved queue storage to file system from database wp-options table to lessen the IO load. (#633504)

    Entrada del registro de cambios

  25. 4.0 Aún no disponible

    🌱🌱🌱Guest Introduced Guest Mode for instantly cacheable content on the first visit.

    Entrada del registro de cambios

  26. 3.6.4 Aún no disponible

    Toolbox Fixed Beta Test upgrade error when upgrading to v3.7+.

    Entrada del registro de cambios

  27. 3.6.3 Aún no disponible

    Core Fixed potential upgrade failure when new versions have changes in activation related functions.

    Entrada del registro de cambios

  28. 3.6.2 Aún no disponible

    Page Optimize Fixed an issue where network purge CSS/JS caused 404 errors for subsites.

    Entrada del registro de cambios

  29. 3.6.1 Aún no disponible

    WP Tested up to WP v5.6.

    Entrada del registro de cambios

  30. 3.6 Aún no disponible

    🌱WebP Added WebP support on Safari Big Sur or Safari v14.0.1+. (@ruikai)

    Entrada del registro de cambios

  31. 3.5.2 Aún no disponible

    CSS CSS Combine is now compatible w/ inline noscript CSS. (@galbaras)

    Entrada del registro de cambios

  32. 3.5.1 Aún no disponible

    JS Inline JS containing nonces can now be combined.

    Entrada del registro de cambios

  33. 3.5.0.2 Aún no disponible

    This is a temporary revert fix. Code is SAME as v3.4.2.

    Entrada del registro de cambios

  34. 3.5.0.1 Aún no disponible

    🔥🐞CSS Fixed print media query issue when having CSS Combine. (@paddy-duncan)

    Entrada del registro de cambios

  35. 3.5 Aún no disponible

    Page Optimize Refactored CSS/JS optimization.

    Entrada del registro de cambios

  36. 3.4.2 Aún no disponible

    CCSS Corrected the issue that wrongly appended non-CSS files to CSS in links before sending request.

    Entrada del registro de cambios

  37. 3.4.1 Aún no disponible

    🐞CCSS Fixed an issue where dynamically generated CSS failed with TypeError: Cannot read property type of undefined.

    Entrada del registro de cambios

  38. 3.4 Aún no disponible

    🌱LQIP New setting LQIP Excludes.

    Entrada del registro de cambios

  39. 3.3.1 Aún no disponible

    🌱Page Optimize New option to Remove Noscript Tags. (@phuc88bmt)

    Entrada del registro de cambios

  40. 3.3 Aún no disponible

    🌱Page Optimize Added a new setting, Inline JS Deferred Excludes. (@ankit)

    Entrada del registro de cambios

  41. 3.2.4 Aún no disponible

    Object New installations no longer get custom data.ini reset, as this could cause lost configuration. (@Eric)

    Entrada del registro de cambios

  42. 3.2.3.2 Aún no disponible

    🔥🐞Page Optimize Hotfix for CSS/JS minify/combine. (@jdelgadoesteban @martinbailey)

    Entrada del registro de cambios

  43. 3.2.3.1 Aún no disponible

    API New filter litespeedbufferbefore and litespeedbufferafter. (#PR243 @joejordanbrown)

    Entrada del registro de cambios

  44. 3.2.3 Aún no disponible

    🌱Page Optimize Added Unique CSS option for future removal of unused CSS per page. (@moongear)

    Entrada del registro de cambios

  45. 3.2.2 Aún no disponible

    🌱Purge Scheduled Purge URLs now supports wildcard. (#427338)

    Entrada del registro de cambios

  46. 3.2.1 Aún no disponible

    Cloud LQIP/CCSS rate limit tweaks. (@ianpegg)

    Entrada del registro de cambios

  47. 3.2 Aún no disponible

    Image Optimize Major improvements in queue management, scalability, and speed. (@LucasRolff)

    Entrada del registro de cambios

  48. 3.1 Aún no disponible

    🌱Network Added Debug settings to network level when on network.

    Entrada del registro de cambios

  49. 3.0.9 Aún no disponible

    Purge Comment cache can be successfully purged now.

    Entrada del registro de cambios

  50. 3.0.8.6 Aún no disponible

    CCSS Bypassed CCSS functionality on frontend when domain key isn't setup yet.

    Entrada del registro de cambios

  51. 3.0.8.5 Aún no disponible

    🔥🐞3rd Hotfix for WPLister critical error due to v3.0.8.4 changes.

    Entrada del registro de cambios

  52. 3.0.8.4 Aún no disponible

    🌱Crawler New setting: Sitemap timeout. (#364607)

    Entrada del registro de cambios

  53. 3.0.8.3 Aún no disponible

    Cloud Better compatibility for the Link to QUIC.cloud operation. (@Ronei de Sousa Almeida)

    Entrada del registro de cambios

  54. 3.0.8.2 Aún no disponible

    GUI Corrected the Request Domain Key wording.

    Entrada del registro de cambios

  55. 3.0.8.1 Aún no disponible

    Object Object cache compatibility for upgrade from v2.9.9- versions.

    Entrada del registro de cambios

  56. 3.0.8 Aún no disponible

    Released v3 on WordPress officially.

    Entrada del registro de cambios

  57. 3.0.4 Aún no disponible

    Cloud Apply Domain Key now receives error info in next apply action if failed to generate.

    Entrada del registro de cambios

  58. 3.0.3 Aún no disponible

    Conf Settings from all options (data ini, defined constant, and forced) will be filtered and cast to expected type.

    Entrada del registro de cambios

  59. 3.0.2 Aún no disponible

    GUI More guidance on domain key setting page.

    Entrada del registro de cambios

  60. 3.0.1 Aún no disponible

    Data Increased timeout for database upgrade related to version upgrade. Display a banner while update in progress.

    Entrada del registro de cambios

  61. 3.0 Aún no disponible

    🌱Media LQIP (Low Quality Image Placeholder).

    Entrada del registro de cambios

  62. 2.9.9.2 Aún no disponible

    🌱GUI New settings to limit News Feed to plugin page only.

    Entrada del registro de cambios

  63. 2.9.9.1 Aún no disponible

    🌱Env Environment Report can now append a passwordless link for support access without wp-admin password.

    Entrada del registro de cambios

  64. 2.9.9 Aún no disponible

    Core: Preload all classes to avoid getting error for upcoming v3.0 upgrade.

    Entrada del registro de cambios

  65. 2.9.8.7 Aún no disponible

    3rd: Enhanced WP stateless compatibility. (#PR143)

    Entrada del registro de cambios

  66. 2.9.8.6 Aún no disponible

    3rd: Bypassed page optimizations for AMP. (#359748 #PR169)

    Entrada del registro de cambios

  67. 2.9.8.5 Aún no disponible

    CCSS: Removed potential PHP notice when getting posttype. (@amcgiffert)

    Entrada del registro de cambios

  68. 2.9.8.4 Aún no disponible

    Object: Increased compatibility with phpredis 5.0.

    Entrada del registro de cambios

  69. 2.9.8.3 Aún no disponible

    CSS: Enhanced the CSS Minify compatibility for CSS with missing closing bracket syntax errors. (@fa508210020)

    Entrada del registro de cambios

  70. 2.9.8.2 Aún no disponible

    🔥🐞 3rd: Fixed PHP 5.3 compatibility issue with Facetwp.

    Entrada del registro de cambios

  71. 2.9.8.1 Aún no disponible

    3rd: Set ESI template hook priority to highest number to prevent ESI conflict with Enfold theme. (#289354)

    Entrada del registro de cambios

  72. 2.9.8 Aún no disponible

    Core: Refactored loading priority so user related functions & optimization features are set after user initialization. (#717223 #114165 #413...

    Entrada del registro de cambios

Léame

Licencia

LiteSpeed Cache

All-in-one unbeatable acceleration & PageSpeed improvement: caching, image/CSS/JS optimization...

LiteSpeed Cache for WordPress (LSCWP) is an all-in-one site acceleration plugin, featuring an exclusive server-level cache and a collection of optimization features.

LSCWP supports WordPress Multisite and is compatible with most popular plugins, including WooCommerce, bbPress, and Yoast SEO.

LiteSpeed Cache for WordPress is compatible with ClassicPress.

Qué añade

  • Shortcodes: [esi]
  • WP-CLI: litespeed-debug, litespeed-image, litespeed-online, litespeed-option, litespeed-presets, litespeed-purge

Installation

View detailed documentation.

For Optimization Without a LiteSpeed Web Server

  1. Install the LiteSpeed Cache for WordPress plugin and activate it.
  2. From the WordPress Dashboard, navigate to LiteSpeed Cache > Page Optimization. Enable the available optimization features in the various tabs.

For Caching and Optimization With a LiteSpeed Web Server

  1. Install LiteSpeed Web Server Enterprise with LSCache Module, LiteSpeed Web ADC, or OpenLiteSpeed with cache module (Free). Or sign up for QUIC.cloud CDN.
  2. Install the LiteSpeed Cache for WordPress plugin and activate it.
  3. From the WordPress Dashboard, navigate to LiteSpeed Cache > Cache, make sure the option Enable LiteSpeed Cache is set to ON.
  4. Enable any desired caching and optimization features in the various tabs.

Notes for LiteSpeed Web Server Enterprise

  • Make sure that your license includes the LSCache module. A 2-CPU trial license with LSCache module is available for free for 15 days.
  • The server must be configured to have caching enabled. If you are the server admin, click here for instructions. Otherwise, please request that the server admin configure the cache root for the server.

Notes for OpenLiteSpeed

  • This integration utilizes OpenLiteSpeed's cache module.
  • If it is a fresh OLS installation, the easiest way to integrate is to use ols1clk. If using an existing WordPress installation, use the --wordpresspath parameter.
  • If OLS and WordPress are both already installed, please follow the instructions in How To Set Up LSCache For WordPress.

Faq

Why do the cache features require LiteSpeed Server?

This plugin communicates with your LiteSpeed Web Server and its built-in page cache (LSCache) to deliver superior performance to your WordPress site. The plugin’s cache features indicate to the server that a page is cacheable and for how long, or they invalidate particular cached pages using tags.

LSCache is a server-level cache, so it's faster than PHP-level caches. Compare with other PHP-based caches.

A page cache allows the server to bypass PHP and database queries altogether. LSCache, in particular, because of its close relationship with the server, can remember things about the cache entries that other plugins cannot, and it can analyze dependencies. It can utilize tags to manage the smart purging of the cache, and it can use vary cookies to serve multiple versions of cached content based on things like mobile vs. desktop, geographic location, and currencies. See our Caching 101 blog series.

If all of that sounds complicated, no need to worry. LSCWP works right out of the box with default settings that are appropriate for most sites. See the Beginner's Guide.

Don't have a LiteSpeed server? Try our QUIC.cloud CDN service. It allows sites on any server (NGINX and Apache included) to experience the power of LiteSpeed caching! Click here to learn more or to give QUIC.cloud a try.

What about the optimization features of LSCache?

LSCWP includes additional optimization features, such as Database Optimization, Minification and Combination of CSS and JS files, HTTP/2 Push, CDN Support, Browser Cache, Object Cache, Lazy Load for Images, and Image Optimization! These features do not require the use of a LiteSpeed web server.

Is the LiteSpeed Cache Plugin for WordPress free?

Yes, LSCWP will always be free and open source. That said, a LiteSpeed server is required for the cache features, and there are fees associated with some LiteSpeed server editions. Some of the premium online services provided through QUIC.cloud (CDN Service, Image Optimization, Critical CSS, Low-Quality Image Placeholder, etc.) require payment at certain usage levels. You can learn more about what these services cost, and what levels of service are free, on your QUIC.cloud dashboard.

What server software is required for this plugin?

A LiteSpeed solution is required in order to use the LiteSpeed Exclusive features of this plugin. Any one of the following will work:

  1. LiteSpeed Web Server Enterprise with LSCache Module (v5.0.10+)
  2. OpenLiteSpeed (v1.4.17+)
  3. LiteSpeed WebADC (v2.0+)
  4. QUIC.cloud CDN

The General Features may be used with any web server. LiteSpeed is not required.

Does this plugin work in a clustered environment?

The cache entries are stored at the LiteSpeed server level. The simplest solution is to use LiteSpeed WebADC, as the cache entries will be stored at that level.

If using another load balancer, the cache entries will only be stored at the backend nodes, not at the load balancer.

The purges will also not be synchronized across the nodes, so this is not recommended.

If a customized solution is required, please contact LiteSpeed Technologies at [email protected]

NOTICE: The rewrite rules created by this plugin must be copied to the Load Balancer.

Where are the cached files stored?

The actual cached pages are stored and managed by LiteSpeed Servers.

Nothing is stored within the WordPress file structure.

Does LiteSpeed Cache for WordPress work with OpenLiteSpeed?

Yes it can work well with OpenLiteSpeed, although some features may not be supported. See Plugin Features above for details. Any setting changes that require modifying the .htaccess file will require a server restart.

Is WooCommerce supported?

In short, yes. However, for some WooCommerce themes, the cart may not be updated correctly. Please visit our blog for a quick tutorial on how to detect this problem and fix it if necessary.

Are my images optimized?

Images are not optimized automatically unless you set LiteSpeed Cache > Image Optimization > Image Optimization Settings > Auto Request Cron to ON. You may also optimize your images manually. Learn more.

How do I make a WP nonce cacheable in my third-party plugin?

Our API includes a function that uses ESI to "punch a hole" in a cached page for a nonce. This allows the nonce to be cached separately, regardless of the TTL of the page it is on. Learn more in the API documentation. We also welcome contributions to our predefined list of known third party plugin nonces that users can optionally include via the plugin's ESI settings.

How do I enable the crawler?

The crawler is disabled by default, and must be enabled by the server admin first.

Once the crawler is enabled on the server side, navigate to LiteSpeed Cache > Crawler > General Settings and set Crawler to ON.

For more detailed information about crawler setup, please see the Crawler documentation.

What are the known compatible plugins and themes?

The vast majority of plugins and themes are compatible with LiteSpeed Cache. The most up-to-date compatibility information can be found in our documentation

Screenshots

  1. Plugin Benchmarks
  2. Admin - Dashboard
  3. Admin - Image Optimization
  4. Admin - Crawler
  5. Admin Settings - Cache
  6. Admin Settings - Page Optimization
  7. Admin Settings - CDN
  8. Admin Settings - DB Optimizer
  9. Admin Settings - Toolbox
  10. Cache Miss Example
  11. Cache Hit Example

Instalar

composer require meteorgpl-plugin/litespeed-cache

Las comprobaciones de licencia del proveedor están intactas: activa el plugin en WordPress con una clave de licencia comprada al proveedor.

Licencia

El plugin no declara ninguna licencia. El código se redistribuye bajo la licencia que el proveedor declaró en las cabeceras del propio plugin.

Las ilustraciones, fuentes, archivos multimedia y documentos que puedan tener una licencia independiente no se redistribuyen; la página de licencias explica qué se sustituye o elimina, y la pestaña de seguridad lo detalla por versión. El soporte y el derecho a actualizaciones vienen con la licencia que compras al proveedor.

Enviar comentarios

Qué funciona, qué no, qué falta: unas palabras ayudan.

Solo si quieres una respuesta.

Se toma en tu navegador, sin esta ventana. Las contraseñas, lo que escribiste en formularios, las claves y los tokens se omiten como bloques grises; puedes ocultar más antes de enviarla. Conservamos las capturas 90 días.

Lo guardamos con la dirección de la página, tu idioma, el tamaño de la ventana, el navegador y la dirección IP, y tu dirección de correo electrónico si nos la das. La dirección IP y el navegador se eliminan a los 90 días. Política de privacidad.

Todos los idiomas