• Resolved HKP

    (@hiskingdomprophecy)


    Hi Folks,

    Was just checking for server errors messages and find thousands of the following:

    [Tue May 26 09:47:16.656439 2026] [proxy_fcgi:error] [pid 680000:tid 680056] [remote 149.232.133.196:32916] AH01071: Got error 'PHP message: PHP Warning: include_once(/xxxxxx/wp-content/plugins/fast-velocity-minify/libs//matthiasmullie/minify/src/Exceptions/PatternMatchException.php): Failed to open stream: No such file or directory in /xxxxxx/wp-content/plugins/fast-velocity-minify/inc/frontend.php on line 29; PHP message: PHP Warning: include_once(): Failed opening '/xxxxxx/wp-content/plugins/fast-velocity-minify/libs//matthiasmullie/minify/src/Exceptions/PatternMatchException.php' for inclusion (include_path='.:/usr/local/php83/lib/php') in /xxxxxx/wp-content/plugins/fast-velocity-minify/inc/frontend.php on line 29'

    Will leave it with you.

    Regards and thanks,
    Angus


    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • We’re seeing the same issue, but not specific to WordPress 7.0. It’s happening on a site with 6.9 and a site with 7.0, so I suspect it was caused by a change in FVM 3.5.5 that both sites auto-updated to.

    I would guess the problem is the double slash in the include path, but have not dug into it enough yet to confirm. If we fix before an update is released I will share here.

    It seems like the file has been removed since the last update or was never there. We commented out that line and everything went back to normal. But i’m sure the error will come back if auto update happens.

    Plugin Author Raul P.

    (@alignak)

    Looks like there was a missing file on the phpminify update.

    Thread Starter HKP

    (@hiskingdomprophecy)

    @alignak Hi Paul.
    Thank you for your speedy resolution of the issue. I am pleased to report that after the update, the matter is fully resolved.

    Regards and thanks,
    Angus

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

You must be logged in to reply to this topic.