Experiencing the same issue (Premium). On a couple sites.
Yep. And the manual download does not seem to be updated (still in 4.24)
Thanks ! 🙂
Definitely a major bug. The plugin repository contains V4.33.0, but when we upload it manually, we get this (not good): https://prnt.sc/h6KdrmtQGNIT
Fix appreciated!
Same problem here. Mailpoet Premium keeps installing 4.24 and then again reports ‘You have an older version of the premium plugin…’.
-
This reply was modified 2 years, 8 months ago by
ambientblog.
Just in case, I also opened GitHub Ticket No. 5237.
Cheerio!
Also having the same issue and can’t upgrade (multiple attempts) and the download version is still 4.24.
Also means premium features are disabled.
“You have an older version of the Premium plugin. The features have been disabled in order not to break MailPoet. Please update it in the Plugins page now.”
Same problem here and I can’t use any feature.
“Invalid API endpoint.”
and
“You have an older version of the Premium plugin. The features have been disabled in order not to break MailPoet. Please update it in the Plugins page now.”
Seems (partly) solved by now: both Mailpoet and Mailpoet premium are now on 4.32 so the error message in Mailpoet is gone. But WordPress still keeps saying there’s a 4.33 update available (which there isn’t). Seems like a good enough workaround for now?
Hi everyone,
Thanks for your feedback. There was indeed an issue with the 4.33.0 release process and our team has just released 4.34.0 which fixes this issue. Updating both plugins now will fix it so I am marking this ticket as resolved.
Thank you all for your patience.
Great! Thanks for the quick solution!
I can confirm V4.34.0 fixed the issue. Thank you!
PS: Don’t ever let that happen again. Have a great cup of coffee and a doughnut before releasing any changes 🙂
Thank you for confirming that 4.34 fixed the issue 🙂
Of course we try really hard to avoid this kind of scenario and we test a lot before releasing a new version but sometimes issues are not picked up prior to release. In these cases the community is really good at informing us so we can fix it in a timely manner so we thank you for your patience.
While we obviously cannot promise that this will not happen again, we do try hard to make it very infrequent and we move to fix it fast.
