Releases: lcache/wp-lcache
Releases · lcache/wp-lcache
Version 0.6.1
- Switches back to
utf8
for LCache tables [#149].
Version 0.6.0
- Supports
utf8mb4
as a database charset [#131, #143]. - Updates to LCache v0.4.0.
- Improve readme and grunt tasks [#130].
Version 0.5.2
- Normalizes address key to comply with DB column length.
- Always runs database table initialization on the
enable
CLI command. - Doesn't require APCu to be enabled in CLI.
- Test improvements.
Version 0.5.1
- Uses the correct DSN format in all DB_HOST scenarios.
- Only loads LCache library for PHP 5.6+, to ensure WordPress doesn't fatal on older versions.
- Test improvements.
Version 0.5.0
- Splits WordPress' alloptions cache into separate cache keys to mitigate cache pollution caused by race conditions. See #31245 for further detail.
- Emits warnings in CLI when LCache isn't properly configured.
- Incorporates a variety of test suite improvements.
Version 0.4.0
- Switches to stub file approach for enabling object cache drop-in, because symlink changes aren't detected by opcode cache in PHP 5.5+.
Version 0.3.1
- Updates LCache to v0.3.4, which automatically detects and handles misuse of the TTL as an expiration timestamp.
Version 0.3.0
- Introduces the
wp lcache enable
WP-CLI command to create theobject-cache.php
symlink. - Updates LCache to v0.3.2, which is more noisy about failed L2 serialization.
- Better admin notices: alerts when LCache database tables are missing, or if the plugin is active but
object-cache.php
is missing.
Version 0.2.2
- Updates LCache to v0.3.1, which has L2 cache guard against returning failed unserializations.
- Sets
STRICT_ALL_TABLES
on the database handler to fail and give warnings if there are issues with database inserts. - Bug fix: Uses
LONGBLOB
column type for lcache_eventvalue
column. Previously, thevalue
column wasBLOB
which meant that long cache values (e.g. alloptions) could be unexpectedly truncated.
Version 0.2.1
- Bug fix: Properly flushes entire LCache with
wp_cache_flush()
is called. Previously, LCache was called improperly, meaning none of the cache was flushed.