Title: Can&#8217;t activate because fatal errors
Last modified: May 28, 2026

---

# Can’t activate because fatal errors

 *  [i1100a](https://wordpress.org/support/users/i1100a/)
 * (@i1100a)
 * [1 week, 6 days ago](https://wordpress.org/support/topic/cant-activate-because-fatal-errors/)
    - Fatal error: Declaration of DI\Container::has($name) must be compatible with
      Psr\Container\ContainerInterface::has(string $id): bool in /…/plugins/auto-
      alt-text/vendor/php-di/php-di/src/Container.php on line 210
    - Fatal error: Declaration of DI\Container::has($name) must be compatible with
      Psr\Container\ContainerInterface::has(string $id): bool in /…/plugins/auto-
      alt-text/vendor/php-di/php-di/src/Container.php on line 210
 * I got these errors when trying to activate the plugin for the first time
   Running
   WP 6.9 using Sage 9 theme by RootsThanks in advance

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

 *  Thread Starter [i1100a](https://wordpress.org/support/users/i1100a/)
 * (@i1100a)
 * [1 week ago](https://wordpress.org/support/topic/cant-activate-because-fatal-errors/#post-18927853)
 * Any idea on how can this be mitigated, please?
 *  Plugin Author [Valerio Monti](https://wordpress.org/support/users/valeriomonti/)
 * (@valeriomonti)
 * [1 week ago](https://wordpress.org/support/topic/cant-activate-because-fatal-errors/#post-18928022)
 * Hi,
   Sorry for the late reply.I’ll try to reproduce the error. I’ll let you know
   as soon as possible.
 *  Plugin Author [Valerio Monti](https://wordpress.org/support/users/valeriomonti/)
 * (@valeriomonti)
 * [5 days, 16 hours ago](https://wordpress.org/support/topic/cant-activate-because-fatal-errors/#post-18930251)
 * Hi,
   Thanks a lot for the detailed report, it really helped me track down the 
   problem quickly.
 * The error you saw was caused by a conflict between the plugin and your Sage 9/
   Roots theme: both were loading their own version of the same underlying library,
   and the two versions weren’t compatible with each other. That clash is what stopped
   the plugin from activating.
 * I’ve just released version 2.8.2, which fixes exactly this kind of conflict, 
   so the plugin can run side by side with Roots without stepping on each other.
 * Please update to 2.8.2 and try activating again, it should work now. Let me know
   if you run into anything else, and thanks again for flagging it!
   Cheers!
    -  This reply was modified 5 days, 16 hours ago by [Valerio Monti](https://wordpress.org/support/users/valeriomonti/).

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

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

 * ![](https://ps.w.org/auto-alt-text/assets/icon.svg?rev=3052057)
 * [Auto Alt Text](https://wordpress.org/plugins/auto-alt-text/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/auto-alt-text/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/auto-alt-text/)
 * [Active Topics](https://wordpress.org/support/plugin/auto-alt-text/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/auto-alt-text/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/auto-alt-text/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Valerio Monti](https://wordpress.org/support/users/valeriomonti/)
 * Last activity: [5 days, 16 hours ago](https://wordpress.org/support/topic/cant-activate-because-fatal-errors/#post-18930251)
 * Status: not resolved