Support » Plugin: WP Mail SMTP by WPForms » Bug: latest version collides with mailster plugin

  • Resolved krko

    (@krko)


    Hello,

    Upgrading to the latest version of WP Mail SMTP causes the mailster plugin to hang indefinitely preventing it from sending any emails. Not a developer, cannot debug any more than this but rolling back to 0.x version solves the issue. The conflict occurs with both latest version of . plugins activated. As I said, 0.x versions of WP SMTP do not collide with mailster.

    Thanks

    krko

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Slava Abakumov

    (@slaffik)

    Which version do you mean by 0.x? 0.11 or 0.10 or 0.9?

    Could you please switch to 1.0.2 for a moment, go to Email Test page and try to send it, copy the debug output there in case of error and then revert back to the working version for now?

    Plugin Author Jared Atchison

    (@jaredatch)

    @krko,

    In addition to what Slava mentioned, when you get a chance can you provide a link for the exact Mailster plugin you are using?

    Looking forward to more details 🙂

    Hey guys,

    Thanks for getting back to me.

    By 0.x I mean any version prior to 1.x. I reverted specifically to 0.11.2.

    Mailster plugin is this – https://codecanyon.net/item/mailster-email-newsletter-plugin-for-wordpress/3078294. It’s not on WP repo but rather Code Canyon.

    I’m able to send email through WP Mail SMTP on 1.0.2. WP Mail SMTP is sending emails properly. However when I have 1.0.2 installed it causes Mailster plugin to hang and trigger Error 500. 0.11.2 and Mailster play nicely.

    The error I see in console is: “Failed to load a resource: the server responded with wp-admin/admin-ajax.php a status of 500 ()”. That happens when sending through Mailster. So I’m not sure what’s going on but definitely 1.0.2 doesn’t play nicely with Mailster.

    I contacted Mailster’s developer as well.

    I hope this helps.

    krko

    • This reply was modified 1 year, 11 months ago by krko.
    • This reply was modified 1 year, 11 months ago by krko.
    Plugin Author Jared Atchison

    (@jaredatch)

    Hey @krko,

    Thanks for the additional information, we really appreciate it.

    It turns out the reason the update is giving you an issue is because since 1.x, we offer a native Google integration, which requires us to include the Google API library in the plugin.

    Mailster offers a Google Analytics integration, so they _also_ load the Google API library.

    So the issue is the two copies/versions of the Google API are conflicting.

    I created an issue for this in GitHub.

    https://github.com/awesomemotive/wp-mail-smtp/issues/82

    We’re going to investigate further and decide the best course of action to get this fixed in an upcoming update. This will likely be taken care of by an update next week, as it will take some thorough research and testing to resolve.

    In the mean time, rolling back to v0.11.2 will restore functionality and get things working again. That version can be downloaded here https://wordpress.org/plugins/wp-mail-smtp/advanced/

    I apologize for the trouble!

    @jaredatch Thanks a lot!
    Keep up the good work.

    krko

    Hey guys, I see 1.1.0 is released. Does it solve this issue?

    krko

    Plugin Author Slava Abakumov

    (@slaffik)

    Hi @krko,

    No, WP Mail SMTP 1.1.0 doesn’t have a fix for a Google library class names collision.
    You can check the progress here: https://github.com/awesomemotive/wp-mail-smtp/issues/82
    When that issue will be closed – that means that it will soon be released.

    Just wanted to let you know that the latest version of mailster (2.2.16) solves this issue. They no longer collide.

    krko

    Plugin Author Slava Abakumov

    (@slaffik)

    That’s awesome, @krko!

    Thanks for sharing.

    But for the next minor release, we plan to improve this on our end as well.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Bug: latest version collides with mailster plugin’ is closed to new replies.