Viewing 11 replies - 1 through 11 (of 11 total)
  • Hello @allenfreeman,

    Would you mind sharing with us the current version of MailPoet that is having the conflict with our plugin?

    Many thanks!

    I had the same conflict between NextGen Gallery and MailPoet (MailPoet 3 (Nuevo) and MailPoet 3 Premium (New) both). Latest versions. I deactivated NextGen Gallery plugin. https://www.sendadarwin.cl/inicio/boletin/

    Thread Starter Allen Freeman

    (@allenfreeman)

    Both plugins are the most up-to-date versions. I keep all plugins up to date, always…

    Hello @allenfreeman,

    We currently do not have any open reports or conflicts with MailPoet.
    We’d like to take a closer look to see if we can reproduce the problem. We may need to temporarily deactivate plugins and switch the theme while troubleshooting. Would you feel OK with that? If so, please send us a bug report here: https://www.imagely.com/report-bug, refer back to this forum thread, and let them know Gaby referred you.

    Many Thanks.

    Thread Starter Allen Freeman

    (@allenfreeman)

    Another user above is also having this same issue.

    It is unlikely a theme conflict.

    Have you tested the latest versions of these two plugins on your own systems?

    That would be better than doing testing on my live site…

    Hi @allenfreeman,

    The dev team requires a bug report in order to work in any particular conflict.
    It’s just part of our protocol. So please, if you have some time, report that back using the following URL https://www.imagely.com/report-bug, refer back to this forum thread, and let them know Gaby referred you.

    Many thanks!

    Thread Starter Allen Freeman

    (@allenfreeman)

    Wow that’s annoying. You’re asking me to fill out a super long form to provide most of the same information I’ve outlined above.

    If your techs install both plugins and test, they’ll see exactly what I’m talking about.

    https://neohgolf.com/email-newsletter-archive/

    Wow, that IS annoying. And by “that” I mean you. Again.

    They offered to help you but you don’t want them to do it directly on your site (which most developers won’t offer because of the work involved) and when they tell you to submit a bug report, you insist that they should take the limited info you provided in a support forum about config issues and work from there. Then you assume that it is a universal problem and if they “simply install both”, they’ll see the error. You have a VERY strange way to ask people for help. I don’t work for them and you’re even p***ing me off.

    Fact — it won’t necessarily show up on their site, because I have both installed on my site, and they’re both working FINE. Hence it is specific to YOUR site and YOUR config, which they offered to try to diagnose for you, but you were too busy being rude.

    Fact — you’ve encountered a potential bug since they normally work together and insist on reporting it in the wrong place which means it won’t be tracked with your email and won’t be followed up and prioritized in the right places, but sure, just because they have a process designed to ensure you get support and corrections by the right people, why should they not just adjust all their processes to do it the way you think they should and is the most convenient for you?

    Fact — On top of all of it, Mailpoet’s help files SPECIFICALLY ADDRESS YOUR ERROR, you muppet, with a page entitled “After an Update, Newsletters Are Missing”. Which you said you make sure they’re always up to date. Because you know, how rude they were in asking you which versions you were using. Which you didn’t even answer, you just said latest. Latest beta? Latest public? Latest as of that day? Who knows, you couldn’t even be bothered to check your versions to confirm the info they asked for so they could attempt to replicate the same environment as you.

    But, good news, MP knows it’s a problem and it’s a PROBLEM WITH THEIR PLUGIN. So you can ask them about how to correct it. You know, like a normal person would when they find a problem with smaller Plugin A instead of asking larger Plugin B developer to fix it.

    I apologize to NGG personnel that they have to put up with muppets like allenfreeman, who has a bit of reputation around the forums for being regularly both rude and condescending. You’re doing a great job trying to solve configuration issues across a gazillion different platforms and setups, most of which work out of the box, and some of us appreciate the effort more than others.

    Paul

    Thread Starter Allen Freeman

    (@allenfreeman)

    It’s always good to read something that took 20 minutes to write from an uninvolved third party.

    Apologies @allenfreeman,

    That form is a requirement and part of our workflow.
    It will allow the developers to set aside time after we have replicated the conflict.

    Thanks for your understanding.

    Because it has been a month or more since your last reply, I am going to mark this as resolved as I assume you have found a solution. Please feel free to reply again if you still have questions.

    Thanks!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘plugin conflict between NextGen Gallery and Mailpoet’ is closed to new replies.