mazzly
Well-known member
I'll need to look into why that might be happening...
Add-on Update Notifier 1.1.8
- Thread starter mazzly
- Start date
mazzly
Well-known member
mazzly updated Add-on Update Notifier with a new update entry:
Added tiers for 90 & 120 extra add-ons to API key
Read the rest of this update entry...
Added tiers for 90 & 120 extra add-ons to API key
Read the rest of this update entry...
mazzly
Well-known member
Ozzy47
Well-known member
Excellent, just upgraded to top tier, thanks.
Oblivion Knight
Well-known member
SeToY
Well-known member
Is happening again, just now with a different add-on (which was already updated yesterday):
Forsaken
Well-known member
Add-on Update Notifier
@Painbaker @mazzly Set in the backend to ignore the currently mismatching version id on the resource page. Will be updated in ~6h. Also @XFA This will look like this until the addon dev releases a version with correctly matching version_id and version_string. If you hover over the text it...
xenforo.com
SeToY
Well-known member
This.Add-on Update Notifier
@Painbaker @mazzly Set in the backend to ignore the currently mismatching version id on the resource page. Will be updated in ~6h. Also @XFA This will look like this until the addon dev releases a version with correctly matching version_id and version_string. If you hover over the text it...
And even then this addon shouldn't show some half-correct information in these cases.
Forsaken
Well-known member
The point of me posting Xon's prior response was to point out that Xon has a justification as to why he cannot update certain add-ons; most of his add-ons are fine, but some are not. Not every case is developer incompetence.
@mazzly is doing an excellent job at offering the update notifications, while also adjusting for any issues with versions or other issues. If you have an issue with how the add-on works, don't use it.
SeToY
Well-known member
lol, nice assumption you did there.
Never said otherwise.
Oooooor... report the issue as an issue to the add-on developer? Like I just did?
Please stop insinuating.
Edit: lol you even edited your sly post. Nice job.
Forsaken
Well-known member
I removed the first part you quoted, because it was redundant when added at the end
.He's aware of the issue, however the issue is not something he can do anything about other than to correct it visually and also alert developers, which he does; he even goes as far to give access to developers to handle their own versioning such as he did with @Bob.
Not sure what else you want from him, because god knows he's done more than the other developer did with way less attitude.
SeToY
Well-known member
That's why I reported it. Thanks for explaining.
I reported a quirk with the add-on. Whether it's his "fault" or the developers' - I don't care. I see an issue that I, myself, cannot fix, since it's not within my reach - I report it.
I don't understand why you bring up these arguments - I have never said anything negative about him let alone attacked him in any way, shape or form.
I simply reported a quirk in his add-on. If you want to attack me for that, go on. Have at it. I wish you the most pleasure doing that.
The canonical version id for my add-ons is the
version_string. As I've explicitly stated before, the version_id handling in XenForo means I can not be changed for most of my add-ons to the format this add-on expects.Plus the only field that is shown in the admincp? An add-on's
version_string and not version_id field. So when parsing fails (and it will fail), it will fail in ways that look silly.XF's informal
version_id schema is fairly restrictive, and the build part simply isn't designed for frequent releases. There are very good reasons why package managers resort to parsing version strings instead of trying to impose formatting rules on an integer id.
mazzly
Well-known member
Worst case scenario if we can't get this "solved" you can always click "ignore this version" and it won't show up until the next time a release is released of this add-on
I'm not 100% sure I understand the reason that e.g. the Alerts Improvements package could not be released with
version_id: 2090000 which would match the version_string: "2.9.0", now it is released with version_id: 2090011 which is the same as version_string: "2.9.0 Alpha 1".- If your own/legacy add-ons check
version_stringfor the actual version, then that can be kept "as is" and you just putversion_idto be the matching value. - If your add-ons use
version_id, then just release the add-ons on XF with aversion_stringthat matches the actualversion_id
The XF add-on installer code requires the
I've been meaning to migrate the version_id to being automatically set using a unix-timestamp on build, simply so the version_id is always being increased automatically without needing a complex schema of what an int should look like.
version_id increase to trigger template/phrase import/rebuilds. My private deployment pipeline means I will often deploy multiple versions (ie they require the version_id to be incremented) before the final release.I've been meaning to migrate the version_id to being automatically set using a unix-timestamp on build, simply so the version_id is always being increased automatically without needing a complex schema of what an int should look like.
Last edited:
mazzly
Well-known member
Hmm yeah I guess the buttons should be hidden there
This is when using ftp upload for addon files or?
SeToY
Well-known member
Yep.This is when using ftp upload for addon files or?
