• Resolved barkeyo

    (@barkeyo)


    Update 3.2.18 crashed my site with the following error details –

    Error Details
    =============
    An error of type E_ERROR was caused in line 161 of the file xxx/public_html/wp-content/plugins/wp-optimize/vendor/rosell-dk/webp-convert/src/Convert/Converters/ImageMagick.php. Error message: Uncaught Error: Call to undefined function WebPConvert\Convert\Converters\escapeshellarg() in xxx/public_html/wp-content/plugins/wp-optimize/vendor/rosell-dk/webp-convert/src/Convert/Converters/ImageMagick.php:161

    Reverted back to 3.2.16 (previous install) to resolve.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Kowsar Hossain

    (@kowsar89)

    Hi @barkeyo ,

    We greatly appreciate your report, and we apologize for any inconvenience you’ve experienced. While we are committed to resolve this issue, we are currently facing challenges in reproducing it on our end. To assist us in this investigation, could you kindly provide us with the following information:

    1. Which Operating System/Server architecture are you using? What version of PHP is installed? What is your web server (e.g., Apache, NginX, etc.)? You can find these information in the screenshot provided here, screenshot: https://prnt.sc/aumv3wJPUcOA

    2. What WebP conversion tools are available on your website? You can find this information in the screenshot provided here, screenshot: https://prnt.sc/5JaOVgJiznW9

    Thank you for your cooperation.

    Thread Starter barkeyo

    (@barkeyo)

    Hi @kowsar89 ,

    Thanks for your reply, details as requested.

    Server Details –

    1. Server architecture – Linux 4.18.0-372.9.1.lve.el7h.x86_64 x86_64
    2. Web server – LiteSpeed
    3. PHP version – 8.1.21 (Supports 64bit values)

    WebP Tools –

    1. imagick
    2. gd
    Plugin Support vupdraft

    (@vupdraft)

    HI,

    Can you take a backup of your plugins with UpdraftPlus and share it with us using something like We Transfer (it’s just so I can test for a plugin conflict)

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘E_Error with 3.2.18’ is closed to new replies.