E_COMPILE_ERROR

  • lilybabydoll1873

    (@lilybabydoll1873)


    1 week, 4 days ago

    Hi,

    I created a website for online sales, and completed the website and on testing I go this error,

    Error Details

    =============

    An error of type E_COMPILE_ERROR was caused in line 59 of the file /home/u254561127/domains/astronautsandrockstars.co.za/public_html/wp-content/plugins/the-courier-guy/vendor/guzzlehttp/psr7/src/Request.php. Error message: Declaration of GuzzleHttp\Psr7\Request::getRequestTarget() must be compatible with Psr\Http\Message\RequestInterface::getRequestTarget(): string

    I believed that I fixed the error related to the plugin, yet, I still get a notice on my website stating: There has been a critical error on this website. and I cannot get the site back-up and running. Please assist.

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator threadi

    (@threadi)

    1 week, 4 days ago

    The message appears in files of the plugin “The Courier Guy Shipping for WooCommerce”. I would recommend contacting their support forum: https://wordpress.org/support/plugin/the-courier-guy/

    Imran – WPMU DEV Support

    (@wpmudev-support9)

    1 week, 4 days ago

    Hello @lilybabydoll1873,

    I hope things are going well for you.

    I tried installing the https://wordpress.org/plugins/the-courier-guy on my Local WP site with Nginx / PHP 8.2.27 / MySQL 8.0.35 database and WordPress 6.9-RC2-61266 Beta. I couldn’t replicate the issue with the plugin, which suggests there is no problem with the plugin itself, but it could be conflicts with other plugins.

    For example, the issue is more likely that another plugin is loading a different Guzzle version, which seems to cause a conflict.

    Here, I recommend a full conflict test to narrow it down. I see that currently the site is live, which seems maybe you’re getting to backend pages, the critical error.
    0. If your hosting offers a staging service, then create it and conduct the remaining steps there.
    1. Create an entire site backup for safety
    2. Deactivate all the plugins.
    3. Deactivate the current theme and set the WordPress default theme.
    4. To ensure that all the plugins and themes are deactivated, whether the issue reproduces or not. If not, then.
    5. Reactivate the theme and check whether the error reproduces. If not, keep reactivating the plugin until it produces the error.
    6. The last activated plugin will be causing the issue.

    Here is the conflict test documentation, which you can refer to if you feel stuck while doing a conflict test.
    https://wpmudev.com/docs/getting-started/getting-support/#conflict-test
    https://wpmudev.com/wp-content/uploads/2015/09/Support-Process-Support-Process.gif`

    Feel free to conduct the test and share the outcome with us.

    –
    Kind Regards,
    Imran Khan

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

You must be logged in to reply to this topic.