• Resolved cookda

    (@cookda)


    When running a backup with the current version, we now get the following error: Exception caught in TypeError: Argument 1 passed to Symfony\Component\EventDispatcher\EventDispatcher::dispatch() must be an object, string given, called in /srv/wordpress/staging/wp-content/plugins/backwpup/vendor/guzzle/guzzle/src/Guzzle/Common/AbstractHasDispatcher.php on line 40

    Server has PHP 7.4.33, WordPress 6.5.5, which are listed as compatible with this plugin. Log file below.

    Are these versions no longer supported, or could there be some other issue with our setup?

    [INFO] BackWPup 4.1.7; A project of WP Media
    [INFO] WordPress 6.5.5 on ????
    [INFO] Log Level: Normal
    [INFO] BackWPup job: DB Backup to Rackspace
    [INFO] Logfile is: backwpup_log_908cbf_2025-01-06_13-05-17.html
    [INFO] Backup file is: fairfood-wordpress-staging-2025-01-06_13-05-17_LN7FT5YM01.zip
    ...
    [06-Jan-2025 13:05:32] 3 Files with 46.75 MB in Archive.
    [06-Jan-2025 13:05:32] 1. Trying to send backup file to Rackspace cloud …
    [06-Jan-2025 13:05:32] ERROR: Exception caught in TypeError: Argument 1 passed to Symfony\Component\EventDispatcher\EventDispatcher::dispatch() must be an object, string given, called in /srv/wordpress/staging/wp-content/plugins/backwpup/vendor/guzzle/guzzle/src/Guzzle/Common/AbstractHasDispatcher.php on line 40
Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter cookda

    (@cookda)

    Sorry, just looked back at previous logs and found that this error began with BackWPUp 4.1.5

    Plugin Support BWU Support

    (@saranshwpm)

    Hi,

    Thank you for reaching out.

    The Guzzle library was recently updated in BackWPUp latest version. So it could be that any other plugin is still relying on older version causing the issue.

    Can you please try deactivating other plugins to see if it helps?

    Best Regards,

    Thread Starter cookda

    (@cookda)

    Thanks, good idea. I found a couple of other plugins using Guzzle, so I removed those (it turns out they weren’t needed). But the error remains.

    grep -rli guzzle | cut -d "/" -f1 | uniq

    So I had a look for any using Symfony. There was a larger list and I updated/deactivated all of those, but the problem persists ??

    Do you have any other ideas?

    Plugin Support BWU Support

    (@saranshwpm)

    Hi,

    Thank you for your reply.

    Can you try using older version of the BackWPUp plugin to see if it makes any change?

    Best Regards,

    Thread Starter cookda

    (@cookda)

    Hi, yes I’ve reverted to 4.1.3 and it is working again.

    I realise that my WordPress version is out of date, so I will try upgrading to v6.7 before trying again.

    [INFO] BackWPup 4.1.3; A project of WP Media
    [INFO] WordPress 6.5.5 on https://????/
    [INFO] Log Level: Normal
    [INFO] BackWPup job: DB Backup to Rackspace
    [INFO] Logfile is: backwpup_log_1d564d_2025-01-24_16-19-34.html
    [INFO] Backup file is: fairfood-wordpress-staging-2025-01-24_16-19-34_UR7FT55Y01.zip
    ...
    [24-Jan-2025 16:19:58] Job done in 24 seconds.
    Thread Starter cookda

    (@cookda)

    Upgraded to WordPress 6.7.1 but still receive the same error.

    So I tried removing all plugins that referenced Symfony also. I wasn’t sure if just deactivating is enough, so I moved them entirely out of the wordpress folder. But I still get the same error.

    So it must be something else do with my environment. I’m not sure what else to do at this time.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.