Title: Fatal error without wp-image class
Last modified: February 21, 2025

---

# Fatal error without wp-image class

 *  Resolved [phoenixuprising](https://wordpress.org/support/users/phoenixuprising/)
 * (@phoenixuprising)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/fatal-error-without-wp-image-class/)
 * Since update 5.2.7, Meow Lightbox has been throwing the following fatal error
   on some pages on my site:
 *     ```wp-block-code
       Fatal error: Uncaught Error: Call to undefined method DiDom\Element::tag() thrown in .../plugins/meow-lightbox/classes/core.php on line 579
       ```
   
 * After much trial and error, I discovered that this only happens on any page with
   an image that lacks the wp-image-### class. Adding that class, whether the ID
   number at the end belongs to the image or not, fixes the issue. Obviously, this
   can be solved by adding that class, but any images with an external source don’t
   have a WP ID. In addition, some plugins might add images that are stored locally
   in the WP media library, but not add that class because it’s unnecessary for 
   the image to render properly.
 * My site is using WordPress 6.7.2. These pages work fine when Meow Lightbox alone
   is disabled, and when the plugin has been rolled back to version 5.2.6.

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

 *  Plugin Support [Val Meow](https://wordpress.org/support/users/valwa/)
 * (@valwa)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/fatal-error-without-wp-image-class/#post-18322896)
 * Hey [@phoenixuprising](https://wordpress.org/support/users/phoenixuprising/)!
   👋
 * Thanks for reporting this! There was indeed a typo that caused the issue. This
   will be fixed in the next release.
 * In the meantime, you can go to the Performance tab and switch from **DiDom** 
   to **HtmlDomParser**, which should resolve the issue.
 * Thanks!
 *  [Gioxx](https://wordpress.org/support/users/gioxx/)
 * (@gioxx)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/fatal-error-without-wp-image-class/#post-18338378)
 * Not exactly the problem described by [@phoenixuprising](https://wordpress.org/support/users/phoenixuprising/),
   but it is still something related to the wp-image class. Since installing the
   latest version of the plugin, this is only a very small part of the PHP error
   file that keeps getting gigantic because of these warnings.
 * [https://privatebin.cerbero.cc/?0617831c076007cd#CpJhT93z3bk6LzGnYxM3jPbfx9iHbXZTh4jgJzm8P2XJ](https://privatebin.cerbero.cc/?0617831c076007cd#CpJhT93z3bk6LzGnYxM3jPbfx9iHbXZTh4jgJzm8P2XJ)
 *  [Blamedutchie](https://wordpress.org/support/users/blamedutchie/)
 * (@blamedutchie)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/fatal-error-without-wp-image-class/#post-18346375)
 * Adding my two cents, not sure if related, but…
 * Like in [@gioxx](https://wordpress.org/support/users/gioxx/) log, my error log
   is filled with classes: wp-image-###.
 * Not a very descriptive error, obviously. On my site, it appears to be limited
   to inline images, which is why am not sure it is connected to this issue, but
   also not willing to rule it out.

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

The topic ‘Fatal error without wp-image class’ is closed to new replies.

 * ![](https://ps.w.org/meow-lightbox/assets/icon-256x256.gif?rev=3004933)
 * [Meow Lightbox](https://wordpress.org/plugins/meow-lightbox/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/meow-lightbox/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/meow-lightbox/)
 * [Active Topics](https://wordpress.org/support/plugin/meow-lightbox/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/meow-lightbox/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/meow-lightbox/reviews/)

 * 3 replies
 * 4 participants
 * Last reply from: [Blamedutchie](https://wordpress.org/support/users/blamedutchie/)
 * Last activity: [1 year, 3 months ago](https://wordpress.org/support/topic/fatal-error-without-wp-image-class/#post-18346375)
 * Status: resolved