Support » Plugin: Gmail SMTP » Plugin Conflicts

Viewing 9 replies - 1 through 9 (of 9 total)
  • I’m having this problem as well, with Use-Your-Drive. Help would be appreciated! Thanks!

    The author of the Use-Your-Drive plugin has provided me with 2 files, Drive.php and MediaFileUpload.php, to deal with the fact that the Gmail SMTP plugin is using V2 and not V3 of the Google API. These 2 files are intended to overwrite their counterparts for the Gmail SMTP plugin. I haven’t had a chance yet to test this solution but hope to do so this weekend. I’ll report back the results asap.

    Plugin Author naa986

    (@naa986)

    Hi, I’m working on updating the Google API client library to the latest version. Unfortunately some functions were modified significantly which may affect existing SMTP users. I’m running some tests to make sure it will work for both new and existing users.

    Thank you! This is greatly appreciated. The author of the Use-Your-Drive plugin told me by e-mail that should you need any assistance in updating your plugin to use the latest Google API library version, he would be more than happy to oblige.

    We have many users of WP-Stateless complaining about conflicts with your plugin. From what we can tell, it is because you’re using an outdated version of the Google SDK on every page load.

    Thanks for looking into this! 🙂

    ref: https://wordpress.org/support/topic/invalid-client-secret-json-file-after-activing-gmail-smtp-plugin/

    Hello,

    To prevent the issues with other plugins, which are using Google SDK, you should not load Google SDK on every page load ( on plugin initialization ). In other case, you will face with another conflicts: when other third-party plugins are using legacy Google SDK ( < v2.0 ).

    Plugin Author naa986

    (@naa986)

    I have just released an update. Please update the plugin and see how it goes.

    To solve the issue with Gmail SMTP plugin, we added back compatibility with Google SDK 1.x. to our WP-Stateless plugin. But, suddenly you launched new version of plugin which contains cut version of latest Google SDK. And… it just broke our plugin again….

    Please, look through my comment above.

    you should not load Google SDK on every page load ( on plugin initialization ). In other case, you will face with another conflicts: when other third-party plugins are using legacy Google SDK ( < v2.0 ).

    It also belongs to other Google SDK versions, since you’re using cut version of SDK…. And, even more fact, Google SDK 2.0.0 has conflicts with Google SDK 2.2.0… So, I’m absolutely sure you will get much more support topics now, regarding conflicts with other plugins which also use Google SDK.

    I believe, that the problem is not a version of Google SDK, but how you’re initializing it. To prevent the most potential issues with other plugins, you just needed to start loading your Google SDK ONLY when it’s really needed, but not on every plugin’s initialization…

    Regards.

    • This reply was modified 1 year, 2 months ago by  Maxim Peshkov.
    • This reply was modified 1 year, 2 months ago by  Maxim Peshkov.
    Plugin Author naa986

    (@naa986)

    @maximpeshkov, Just released another update. The plugin will now include the library only when needed.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Plugin Conflicts’ is closed to new replies.