• Resolved shane3340

    (@shane3340)


    Hello,
    When running our CLI cron, we are getting the following error.

    Error: Callable “Queue_Command” does not exist, and cannot be registered as wp queue

    Any ideas on how to fix this?

    I have followed the instructions RE: turning off the worker and setting up the cron. The above error was sent to me by the web host

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter shane3340

    (@shane3340)

    I have also tried fully deleting the plugin, and disconnecting from Mailchimp and starting over.

    We are seeing the same problem after this latest plugin update to version 2.1.6. It seems that after the update there are some issues caused by this Mailchimp for Woocommerce plugin. The issues we are seeing is that trying to save any settings for themes or other plugins is not working and also changing plugins active/inactive doesn’t work in the backend. Also trying to use any CLI commands gives the error Shane mentioned: Error: Callable “Queue_Command” does not exist, and cannot be registered as wp queue

    Only way to deactivate the Mailchimp plugin was changing the name of that plugins folder. After deactivating this plugin everything started working again. WordPress doesn’t seem to allow reactivate the Mailchimp plugin (I did change the plugin’s folder name back to original). If trying to activate it from the backend it doesn’t stay enabled and trying the activation from CLI gives the previously mentioned “Queue_Command” error.

    I wonder if these errors are somehow related to the options autoload feature introduced in this version of the plugin. But clearly this should be fixed. Until then I think I’ll revert back to the previous version or just keep the plugin disabled.

    I am getting the same error Error: Callable “Queue_Command” does not exist, and cannot be registered as wp queue with the version 2.1.6 of the plugin

    Plugin Author ryanhungate

    (@ryanhungate)

    @andresva700 @tatutre @shane3340 You are right – we’ve spotted the reason as well – it’s in the bootstrap.php file – on line 69 – we need to change:

    /// wrong path
    ‘Queue_Command’ => ‘includes/vendor/queue/classes/cli-queue-command.php’,

    /// to the correct path
    ‘Queue_Command’ => ‘includes/vendor/queue/classes/cli/queue-command.php’,

    we will get a patch up right away. Thanks for pointing that out.

    Thread Starter shane3340

    (@shane3340)

    Thanks – looks like that has worked for me – the queue appears to be emptying…. i think

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Cron Error’ is closed to new replies.