Hi @kanky00,
I’m sorry to hear that this update created this situation, and I wanted to share some context behind the message you saw. This version contained an update to an internal library which was not compatible with older versions of Event Tickets. One complication with updates that are not compatible with older versions is that WordPress doesn’t have a great way to communicate version dependencies prior to running the updates (when auto-updates are enabled). In order to avoid a potential fatal error or other negative side effects that could arise from running incompatible plugin versions, we soft-deactivate one of the plugins and display this message instead.
To prevent issues like this from happening in the future, we do recommend keeping auto-updates disabled. This gives the site admin the chance to test updates on a staging site first to ensure that everything is working as expected with the new version. There is always the chance that the code changed in the new version may not work the same way with third party themes and plugins as the previous version did, in addition to compatibility issues that could arise with older versions of our other plugins if those plugins are not also automatically updated at the same time.
With that being said, I realize that this functionality created a difficult situation for you, which is not our intent. We found the support ticket you submitted in our inbox and will follow up with you there to help get this resolved as quickly as possible and avoid this happening again in the future.
Best Regards,
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backward compatible manner
PATCH version when you make backward compatible bug fixes
Why choose to release this as a PATCH version? Why even use Semver at all?
@thijsvanloef this was identified as a problem in this version, I specifically talked to the development team about this, and it was the incorrect version number to be chosen.
We will make sure this mistake doesn’t happen again, we don’t use SemVer specifically but a similar structure and this release was definitely not a patch/minor .
