Title: psr/Cache modernization update
Last modified: May 27, 2026

---

# psr/Cache modernization update

 *  Resolved [skagia](https://wordpress.org/support/users/skagia/)
 * (@skagia)
 * [1 week, 5 days ago](https://wordpress.org/support/topic/psr-cache-modernization-update/)
 * Hi Weglot team!
 * We use Weglot on a client production site and ran into a fatal error today on
   the WordPress plugins screen. From what we could trace, it involves the psr/cache
   library that Weglot bundles and another plugin on the same site that bundles 
   a newer version of the same library. They both live in the global Psr\Cache namespace,
   so PHP ended up with the older interface in memory when the other plugin tried
   to load its modern class, and the signatures no longer matched.
 * Wanted to share this in case it’s something you’d want to look at. We can send
   over more details, error trace, or the list of plugins involved if any of that
   helps.
 * Thanks for keeping the plugin going.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Contributor [Edson Galina Fortes](https://wordpress.org/support/users/glx77/)
 * (@glx77)
 * [1 week, 4 days ago](https://wordpress.org/support/topic/psr-cache-modernization-update/#post-18921810)
 * Hi,
 * Thanks for the detailed report — really appreciate you taking the time to trace
   it down.
 * To give you some context on the library version: Weglot still targets PHP 7.4
   as its minimum requirement, and psr/cache 2.0+ dropped PHP 7 support
   entirely.
   Jumping to a newer version would break compatibility for a significant portion
   of our users, so we’re intentionally staying on 1.0 for now.
 * As a short-term workaround while we investigate, we have a filter called weglot/
   skip_contexts that lets you tell Weglot to skip its initialisation in
   specific
   admin screens or pages. If the fatal happens on a predictable screen, that can
   at least keep the plugins screen stable:
 * add_filter( ‘weglot/skip_contexts’, function( $contexts ) {
   $contexts[‘screens’][]
   = ‘plugins’; // example: WP admin plugins screenreturn $contexts;} );
 * That said, to properly reproduce and test a fix on our end, could you share:
    - The name of the conflicting plugin (and ideally its version)?
    - The exact screen or action that triggers the fatal (plugins page, a specific
      admin page, frontend, etc.)?
    - The full error trace if you have it? With that we can set up the same environment
      locally and look at the best path forward. 
      Thanks again!
 *  Plugin Contributor [Edson Galina Fortes](https://wordpress.org/support/users/glx77/)
 * (@glx77)
 * [6 days, 12 hours ago](https://wordpress.org/support/topic/psr-cache-modernization-update/#post-18926413)
 * Hi [@skagia](https://wordpress.org/support/users/skagia/) ,
   hope you’re fine ?
   do you still facing your issue ?

Viewing 2 replies - 1 through 2 (of 2 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fpsr-cache-modernization-update%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/weglot/assets/icon-256x256.gif?rev=3333666)
 * [Translate WordPress with Weglot - Multilingual AI Translation](https://wordpress.org/plugins/weglot/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/weglot/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/weglot/)
 * [Active Topics](https://wordpress.org/support/plugin/weglot/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/weglot/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/weglot/reviews/)

## Tags

 * [bug fix](https://wordpress.org/support/topic-tag/bug-fix/)

 * 2 replies
 * 2 participants
 * Last reply from: [Edson Galina Fortes](https://wordpress.org/support/users/glx77/)
 * Last activity: [6 days, 12 hours ago](https://wordpress.org/support/topic/psr-cache-modernization-update/#post-18926413)
 * Status: resolved