Releases: loco/wp-loco
Releases · loco/wp-loco
2.8.3
- Bumped WordPress compatibility to 6.9.4
- Additional restrictions on viewing source code refs
- Fix for CVE-2026-4146: Thanks Jack Pas (Dark.)
2.8.2
- Fix for LLMs retaining escaped forward slashes
- Bumped WordPress compatibility to 6.9.1
- New security features for viewing source code refs:
-
- Access permission via
code_viewsetting
- Access permission via
-
- JSON schemas must validate as blocks|theme.json
-
- PHP/JS sources must contain extractable strings
2.8.1
- DeepL uses
quality_optimizedwithloco_deepl_modelfilter - DeepL beta languages enabled when next-gen model is used
http_request_timeoutfilter returns maximum value- Splitting chat completion jobs into maximum 5KB batches
- Added support for other chat completion APIs via
vendorconfig field - Fixed single colon usage bug during chat completions
- Autoloader no longer throws when Loco_ class not found
- Refreshing Ajax nonces on WordPress heartbeat
- Bumped WordPress compatibility to 6.9
2.8.0
- Bugfix for PHP 8.0 compatibility
- Dropped support for PHP < 7.4
2.7.3
- PHP 8.4 compatibility
- Bumped WordPress compatibility to 6.8.1
2.7.2
- DeepL client moved to back end, because CORS
- Rolled in support for OpenAI / ChatGPT translation
- Workaround for JSON file references with no line number
- Bumped WordPress compatibility to 6.7.2
2.7.1
- Debug logging of unloaded domains reduced to a summary
2.7.0
- Raised minimum requirements to WordPress 6.6
- Minimum PHP version becomes 7.2.24 as per WordPress 6.6
- Locale-filtered bundle list now searches for base language
- Loading helper forcefully removes prematurely loaded text domains
- Machine translation hooks now have access to message context
- Persistent UI state for code view and invisible character modes
2.6.14
Critical fix: A relative path passed to load_textdomain no longer throws exception.
2.6.13
- Fix for direct calls to
load_textdomainwith custom paths - This resolves a regression in 2.6.12