Error after 2.1.1 update

  • Resolved julien

    (@leguennecj)


    4 years, 8 months ago

    Extension was well working before 2.1.1 update.

    now if I activate extension I have wordpress error.

    Please see the error email that I receive:

    Current extension : WP Mail SMTP (version 2.1.1)
    PHP version 7.4.7

    Error details
    ======================
    Une erreur de type E_COMPILE_ERROR a été causée dans la ligne 19 du fichier /home/leju0642/public_html/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/migration/Config.php. Message d’erreur : Cannot declare class Action_Scheduler\Migration\Config, because the name is already in use

    Can you help me for that ?

    Regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Gregor Capuder

    (@capuderg)

    Hi Julien,

    It looks like something else (probably a plugin or a theme) is already defining the Action Scheduler library that is also used in our plugin.

    Could you please let us know the list of active plugins on your site, so we can investigate which plugin might be causing this? Also please share the theme you are using.

    Thanks and take care!

    Thread Starter julien

    (@leguennecj)

    Hi Gregor

    I have find the incompatibility. Indeed it’s with WPML Multilingual CMS Version 4.3.12 by OnTheGoSystems

    • This reply was modified 4 years, 8 months ago by julien.
    Thread Starter julien

    (@leguennecj)

    Problem seems to come from compatibility with WPML Multilingual CMS Version 4.3.12

    • This reply was modified 4 years, 8 months ago by julien.
    Plugin Author Gregor Capuder

    (@capuderg)

    Hi Julien,

    I don’t have access to that plugin’s code, so I can’t look at how they are adding the Action Scheduler library to their plugin.

    Could you please contact the support of WPML and ask them if they are using Action Scheduler library and if they are loading it correctly? Maybe they are using an older version of the library?

    Take care!

    Hi @leguennecj – We haven’t heard from you in about a week, so I’m going to go ahead and mark this ticket resolved. If you still have questions, though, please feel welcome to continue the conversation.

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