Fatal errors persist in 5.0.5

  • Resolved thartl

    (@hartl)


    1 year, 1 month ago

    The same fatal error I reported previously is still occuring in 5.0.5.

    “[23-Oct-2023 15:20:38 UTC] PHP Fatal error: Uncaught TypeError: date(): Argument #2 ($timestamp) must be of type ?int, string given in …wp-content/plugins/meow-lightbox/classes/core.php:279”

    The same fix still works: cast to INT on line 264.

    Can you have a look?

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

    (@valwa)

    Hey @hartl ??

    What version of PHP are you using, and what type of server are you using? This shouldn’t be happening as the timestamp type should be an integer when received to begin with.

    Anyway, we’ve made modifications to ensure that the type is converted before being used. This should be available in an upcoming update soon. Thanks for your patience and understanding. ??

    Thread Starter thartl

    (@hartl)

    Thanks, @valwa.

    Our servers are Ubuntu 20.04/22.04, running nginx 1.24 and PHP 8.0/8.1.

    • This reply was modified 1 year, 1 month ago by thartl.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal errors persist in 5.0.5’ is closed to new replies.