• Resolved fogger

    (@fgruen)


    What have you guys been up to lately? The latest update to version 2.7.2 is causing another critical WordPress error (v 6.8.3) that forces deactivation.

    Fehler-Details
    ==============
    Ein Fehler vom Typ E_ERROR wurde in der Zeile 383 der Datei /homepages/.../wp-content/plugins/responsive-lightbox/responsive-lightbox.php verursacht. Fehlermeldung: Uncaught TypeError: array_merge(): Argument #2 must be of type array, string given in /homepages/.../wp-content/plugins/responsive-lightbox/responsive-lightbox.php:383
    Stack trace:
    #0 /homepages/.../wp-content/plugins/responsive-lightbox/responsive-lightbox.php(383): array_merge()
    #1 /homepages/.../wp-content/plugins/responsive-lightbox/responsive-lightbox.php(452): Responsive_Lightbox->__construct()
    #2 /homepages/.../wp-content/plugins/responsive-lightbox/responsive-lightbox.php(2230): Responsive_Lightbox::instance()
    #3 /homepages/.../wp-content/plugins/responsive-lightbox/includes/class-frontend.php(37): Responsive_Lightbox()
    #4 /homepages/.../wp-content/plugins/responsive-lightbox/includes/class-frontend.php(6): Responsive_Lightbox_Frontend->__construct()
    #5 /homepages/.../wp-content/plugins/responsive-lightbox/responsive-lightbox.php(36): include_once('/homepages/...')
    #6 /homepages/.../wp-settings.php(545): include_once('/homepages/...')
    #7 /homepages/.../wp-config.php(109): require_once('/homepages/...')
    #8 /homepages/.../wp-load.php(50): require_once('/homepages/...')
    #9 /homepages/.../wp-admin/admin.php(35): require_once('/homepages/...')
    #10 /homepages/.../wp-admin/index.php(10): require_once('/homepages/...')
    #11 {main}
     thrown

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support weiser

    (@weiser)

    Thanks for reporting this! We’ve been rolling out a large set of improvements recently, and while we perform extensive testing before every release, occasionally something can slip through – especially in edge‑case environments.

    In this case, the issue only occurs when a site has both: malformed options stored in the database and is running PHP 8+. That’s the reason why we have not noticed the issue during testing.

    That said, we’ve just released version 2.7.3, which includes hardened option‑caching logic and should fully resolve the error you encountered.

    Thread Starter fogger

    (@fgruen)

    Thank you very much for your prompt response and the update. Version 2.7.3 works perfectly.

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

You must be logged in to reply to this topic.