Since XoN add-ons nowadays use their own magical versioning system, we managed to introduce a bug with the last release, which fixed add-ons using the "90-hack" to be picked up correctly.
This bug made various XoN add-ons show up as having an update, even if the latest one was already installed.
Thanks again @Fatih Ozcan for reporting this
I'm confused. You announce a package update but the version remained the same and when I go to upgrade it gives me the option to Rebuild the plugin. This was true yesterday as well when an UPdate notification went out.mazzly updated Add-on Update Notifier with a new update entry:
Another backend update to fix a bug with previous update
Read the rest of this update entry...
Another backend update
They were both "backend" updates, meaning no new version was needed to be installedI'm confused. You announce a package update but the version remained the same and when I go to upgrade it gives me the option to Rebuild the plugin. This was true yesterday as well when an UPdate notification went out.
Is this a plugin update?
I'm sure by now you're possibly somewhat aware of the unnecessary hassle this has unwittingly created.They were both "backend" updates, meaning no new version was needed to be installed
...The last three updates literally include backend in the title .I'm sure by now you're possibly somewhat aware of the unnecessary hassle this has unwittingly created.
Perhaps a simple post clarifying that in most cases people will need to check each of the indicated add-on's respective sources for any actual update and if there isn't, they should then hit 'ignore this version'.
I realize it's mentioned within the 'read the rest of this update entry'—however as a basic courtesy it would've been helpful to state this at the top of the "update" entries without requiring further digging.
Thank you for sharing your insight....The last three updates literally include backend in the title .
Backend updates do not push or notify of updates, only that changes have been made.
Updates are just development specific posts, not specific to a version.
That is because not all developers follow the recommended spec for versioning (not all of them can); @mazzly does what he can to mitigate the edge cases, however it is difficult to always do so.Thank you for sharing your insight.
This thoroughly elucidates why there have been false add-on update notifications appearing in the ACP since last weekend—with a few genuine add-on update notifications mixed amongst them.
The continued pugnacity is quite unnecessary.That is because not all developers follow the recommended spec for versioning (not all of them can); @mazzly does what he can to mitigate the edge cases, however it is difficult to always do so.
take it as you want, obviously not worth my time.The continued pugnacity is quite unnecessary.
I suggested a very simple means for additional mitigation which merely requires 20-30 words.
You are able to "ignore" updates for addons, both a specific version, and also all version updatesBugFix: Don't prompt for addon upgrades that are incompatible with your version. Eg. Addon requires XF 2.2.13 (or minimal PHP) but you only have XF 2.2.12 (or lower PHP version).
Suggestion: An option to not include/prompt for Disabled addons.
Can you send your API key in a private message and I can check if there is something special with it...It never worked for me. I never received any update notification. Do I have something wrong?
Sent you a PMCan you send your API key in a private message and I can check if there is something special with it...
We use essential cookies to make this site work, and optional cookies to enhance your experience.