Conflict on Amazon SDK

  • Resolved Stefano Lissa

    (@satollo)


    3 years, 9 months ago

    Hi, we’re registering a number of requests for issue when both Newsletter and your plugin are installed and active. The problem seems connected to the amazon sdk, which apparently is partially loaded by your plugin (maybe with autoloader) and blocks the loading of other amazon sdk classes.

    Does the plugin load the amazon sdk every time? Or strictly when needed?

    Is the full sdk with the default loader provided by your plugin? We detect is another amazon sdk is already present and avoid to load our version but then when we need classes to interface the amazon ses service they result unavailable.

    Thank you, Stefano.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support happyAnt

    (@duongcuong96)

    Hello @satollo
    Sorry about the delayed response.
    I was not at work that time
    BackWPUp uses composer autoload to load the AWS SDK library.
    I hope that it could help.

    Thread Starter Stefano Lissa

    (@satollo)

    Ops, i checked the trunk of your plugin but only a little part of the Amazon AWS SDK is included. That means if your plugin is the first to load your version of SDK, other plugins which need to use the SDK could miss some parts.

    Could you load the SDK only when you really need it. For example, one of our user does not use the S3 as backup method but the SDK seem to be loaded anyway.

    Thank you!

    Stefano.

    Hi Stefano, I’m running in to the same issue. They are overriding other implementations with their own, and as you noticed, they don’t include everything in the SDK.

    How is this marked as resolved? Were you able to come up with a solution?

    I’ve been a proud BackWPup user for years, but now that I’m working on another plugin using the AWS SDK, I may have to find an alternative if there is no way around this.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict on Amazon SDK’ is closed to new replies.