WTF have you done?

  • Every site I had wp-smtp installed on with an SMTP connection working has been disabled! Since your update the active connection is disabled on all sites, and hundreds of our sites have been sending mail to nowhere for the past 2 days:

    Additionally the interface now looks like a bucket of crap and your mail logs are now useless.

    You took a nice simple plugin and destroyed it, next time spend the same amount of time testing as you do developing!!

    I will be uninstalling it and replacing it with something not designed by idiots.

    Best of luck to you, cause you will need it.

    Thanks for destroying my weekend!

    • This topic was modified 1 week, 3 days ago by mcrea1248.
    • This topic was modified 1 week, 3 days ago by mcrea1248.
Viewing 7 replies - 1 through 7 (of 7 total)
  • WebCodePoet

    (@senjoralfonso)

    Same here. Great, your now publish first update and you start making shit out of this wonderful plugin. How and which way is it it useful to have this switch if it is not enabled by default? Now I have to change this switch in all domains I work with, this takes me about 30 minutes of lifetime for nothing.

    Thread Starter mcrea1248

    (@mcrea1248)

    • The Active Connection switch is activated correctly when performing manual plug-in updates, it seems to only be affecting the unattended auto updates.
    • Occasionality I got an error at the top saying something like “SMTP Authentication failed during plug-in upgrade” but the majority showed no error and just had a deactivated Connection switch.
    • On 2 or 3 occasions the SMTP username field was overwritten with what looked like a MD5 or similar hash value, possibly from the database?
    • Some of the sites were still sending mail through the correct SMTP route even though there was no Active Connection set.
    • This reply was modified 1 week, 3 days ago by mcrea1248.
    helsinkisystems

    (@helsinkisystems)

    • Occasionality I got an error at the top saying something like “SMTP Authentication failed during plug-in upgrade” but the majority showed no error and just had a deactivated Connection switch.
    • On 2 or 3 occasions the SMTP username field was overwritten with what looked like a MD5 or similar hash value, possibly from the database?

    We observed the exact same behavior for WordPress Sites we are operating, and we already had the problem with the “hash”-like values in the last update. So the counter is at two out of two updates breaking existing setups since the relaunch.

    Since the “top-notch technical support for all users” advertised in the plugin-FAQ has so far ignored this issue, we will also look for an alternative.

    Matt Cromwell

    (@webdevmattcrom)

    HI all,

    I oversee Customer Experience at StellarWP which includes all things related to SolidWP as well.

    Thanks for these reports of this issue. I flagged this today with our devteam and we’re working on replicating the issue, clearly something is off, but so far we’ve tried all of the below without being able to replicate the behavior you’re seeing:

    • updating from 1.2.3 to 2.1.0 -> No issues
    • updating from 1.2.7 to 2.1.0 -> No issues
    • updating from 2.0.0 to 2.1.0 -> No issues

    However, two different members of our team found this to be problematic:

    1. Install 1.2.3 version
    2. Setup the SMTP.
    3. Confirm that it’s working as intended
    4. Then update to 1.2.7 and see if the setting still persist

    In each case upgrading to version 1.2.7 removed the previously existing settings.

    So can each of you confirm from which versions you upgraded from and to?

    And just as an olivebranch, we’ll work hard to resolve this as best we can, but keep in mind that we acquired the plugin when it was at version 1.2.7 and we had to do a lot of clean up before we had confidence in version 2.0. This wasn’t done hastily it without due diligence, just like we are taking your input and feedback seriously and working towards resolution today as well.

    Thank you!

    Thread Starter mcrea1248

    (@mcrea1248)

    As mentioned it seems to only be affecting the unattended auto updates:

    The Active Connection switch is activated correctly when performing manual plug-in updates, it seems to only be affecting the unattended auto updates.

    We dont see the issue when the update is manually triggered.

    The plug-ins were all set to auto update so they should have been at the latest versions.

    The issue was only evident after the [2.1.0] 2024-10-09 version update.

    Matt Cromwell

    (@webdevmattcrom)

    Hi folks, we were finally able to replicate the issue as you all experienced it. This is what we found:

    1. Install 1.2.7 and configure
    2. simulate auto-update to 2.0.0
    3. simulate auto-update to 2.1.0

    That resulted in the breakage that you’re all reporting. We have a release that’s going through QA now to fix this.

    Of course, fixing this in the new release won’t give you your time back you spent this past weekend, or reverse any of that work that you did over the past few days. We wish we were able to perfectly predict these situations every time, but we’re fallible just like you are. Nevertheless, your reports and feedback helped us identify this issue to prevent it going forward.

    Watch for that update coming soon. Thank you!

    Same here, but it gets worse.
    Every form that’s using this plugin to send mail are automatically added to a marketing mailing list…
    This goes against to RGDP, right?!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.