Latest version (10.8.5) causing PHP fatal error

  • Resolved alfy40

    (@alfy40)


    1 month ago

    Following the update to version 10.8.5 this morning, PHP fatal errors were being caused whenever a page was using an ARVE shortcode. This would be the typical log:

    2026/05/08 11:44:32 [error] 695873#695873: *3507281 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught TypeError: preg_match(): Argument #1 ($pattern) must be of type string, null given in /var/www/html/foobar.com/wp-content/plugins/arve-pro/php/fn-shortcode-filters.php:138
    Stack trace: 0 /var/www/html/foobar.com/wp-content/plugins/arve-pro/php/fn-shortcode-filters.php(138): preg_match() 1 /var/www/html/foobar.com/wp-content/plugins/arve-pro/php/fn-shortcode-filters.php(43): Nextgenthemes\ARVE\Pro\banned_video_graphql_data() 2 /var/www/html/foobar.com/wp-includes/class-wp-hook.php(343): Nextgenthemes\ARVE\Pro\shortcode_atts_extra_data() 3 /var/www/html/foobar.com/wp-includes/plugin.php(205): WP_Hook->apply_filters() 4 /var/www/html/foobar.com/wp-includes/shortcodes.php(690): apply_filters() 5 /var/www/html/foobar.com/wp-content/plugins/advanced-responsive-video-embedder/php/Video.php(192): shortcode_atts() 6 /var/www/html/foobar.com/wp-content/plugins/advanced-responsive-video-embedder/php/fn-shortcodes.php(77):” while reading response header from upstream, client: 104.56.117.207, server: foobar.com, request: “GET /this-is-a-webpage-example-url/ HTTP/2.0”, upstream: “fastcgi://unix:/run/php/php8.4-fpm.sock:”, host: “foobar.com”

    Note I also have the Pro plugin installed (v.7.1.2).

    I dowgraded the main/free plugin to 10.8.2 and it solved my issue.

    This needs to be addressed urgently.

Viewing 1 replies (of 1 total)
  • Plugin Author Nico

    (@nico23)

    4 weeks, 1 day ago

    You did not read the sticky post. Thanks anyway for reporting this even if here is the wrong place. I found a bug that caused outdated add-ons to be executed.

    This would not happen if you also updated pro to latest 7.1.4 but good that this helped catch a bug. If you now update ARVE only and not Pro it will simply not execute any code from the pro-addon (no errors) but you need the latest for it to work again.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.