Add-on Update Notifier 1.1.8

mazzly · Sep 30, 2023

mazzly updated Add-on Update Notifier with a new update entry:

Show buttons for download/changelog in new update notice

As suggested by @Mouth & @benFF: Show buttons for download/changelog in the notice on top of the add-ons page:
View attachment 291821

Read the rest of this update entry...

securedme · Oct 5, 2023

Can you please add the installed and new version number in the notification?

Semper Fidelis · Oct 15, 2023

Am I the only one who has Password Tools "stuck"? The AddOn is updated, but the alert remains.

Semper Fidelis · Oct 20, 2023

Any idea why this is happening:

mazzly · Oct 20, 2023

Semper Fidelis said:
Any idea why this is happening:

View attachment 292760

XoN's versioning that has some bug not automatically switching over to his new versioning, now manually fixed on backend so that it should work going forward...

webbouk · Nov 9, 2023

Just a quick 'credit given where credit is due' post from me....

This bit is awesome, saves so much time and work scrolling to find the add-on that needs upgrading. Quick reference to which add-ons have upgrades, one click to download the upgrade, one click to start the download (standard XF proceedure), job done

Awesome add-on, keep up the good work @mazzly

Recep Baltaş · Nov 15, 2023

Updates exist for the following addons:

[Liam W.] Post Macros

Nope, it's already up to date.

mazzly · Nov 15, 2023

Recep Baltaş said:
Updates exist for the following addons:

[Liam W.] Post Macros

Nope, it's already up to date.

This is because the page at https://xenforo.com/community/resources/liam-w-post-macros.5631/ has a string that is not "standard XF version", we can sometimes work around this on the backend, but in this case the new version is 5020230 which is equivalent to 5.2.2 Beta...

@Recep Baltaş you can click "ignore this version" to get rid of the notification until next time it changes

@XenSoluce please read https://xf-addon-update-notifier.com/how-does-xf-addon-versioning-work

TL;DR; When releasing a new addon version, set the "New version number"-field to match the addon.json version_string-value (and don't modify that value yourself, xf:addon bump-version sets that for you...)

SyTry · Nov 16, 2023

mazzly said:
This is because the page at https://xenforo.com/community/resources/liam-w-post-macros.5631/ has a string that is not "standard XF version", we can sometimes work around this on the backend, but in this case the new version is 5020230 which is equivalent to 5.2.2 Beta...

@Recep Baltaş you can click "ignore this version" to get rid of the notification until next time it changes

@XenSoluce please read https://xf-addon-update-notifier.com/how-does-xf-addon-versioning-work

TL;DR; When releasing a new addon version, set the "New version number"-field to match the addon.json version_string-value (and don't modify that value yourself, xf:addon bump-version sets that for you...)

Hello, so we need to stop adding "Fix" and it should be ok ?

Regards, SyTry

mazzly · Nov 16, 2023

SyTry said:
Hello, so we need to stop adding "Fix" and it should be ok ?

Regards, SyTry

You should use the value of version_string from the file addon.json of the add-on

Then our backend can understand it and map it to the correct version.

mazzly · Dec 17, 2023

mazzly updated Add-on Update Notifier with a new update entry:

Backend fix to handle XF2.3 new <xf:time> format

Note: This is a backend change, meaning: there is no new package to install

Since XF2.3 the pages have <time>-elements with slightly different markup to denote timestamps.

Our backend is now updated to correctly read the timestamp for add-on updates

Read the rest of this update entry...

Recep Baltaş · Dec 17, 2023

[XFA] Core
[XFA] Nodes Icon Tweak

Already up to date but getting a notification.

mazzly · Dec 18, 2023

Recep Baltaş said:
[XFA] Core

[XFA] Nodes Icon Tweak

Already up to date but getting a notification.

Core: from our backend, I can see your forum is on version 901120090 while version 901140170 should be available (other forums are using it), maybe you need to update the license or similar to get a newer version?

Nodes Icon Tweak: It seems they have used the wrong version for that release, so I put it in our backend to match and ignore the "correctly parsed" version. Hopefully, for the next release they will have it correctly set

Recep Baltaş · Dec 18, 2023

mazzly said:
Core: from our backend, I can see your forum is on version 901120090 while version 901140170 should be available (other forums are using it), maybe you need to update the license or similar to get a newer version?

Downloaded again. Rebuilt with overwriting existing files. Still not up to date.

mazzly · Dec 20, 2023

Recep Baltaş said:
Downloaded again. Rebuilt with overwriting existing files. Still not up to date.

If you unzip the add-on file and open the addon.json file, what is the value for version_id ?

The newest version is 901140170, if it doesn't contain that then they are not giving you the latest version for some reason

Recep Baltaş · Dec 21, 2023

Code:

{
    "legacy_addon_id": "",
    "title": "[XFA] Core",
    "description": "Core functions for Xen-Factory team add-ons.",
    "version_id": 901140100,
    "version_string": "1.14.1",
    "dev": "XFA",
    "dev_url": "http://www.xen-factory.com",
    "faq_url": "https://www.xen-factory.com/index.php?forums/manuals.127/",
    "support_url": "https://www.xen-factory.com/index.php#xf2-support",
    "extra_urls": [],
    "require": {
        "XF": [
            2020270,
            "XenForo 2.2.2+"
        ]
    },
    "icon": "icon.png"
}

btmgreg · Jan 23, 2024

Hey Mazzly, Hope you're well. I've been trying to investigate an issue being caused to Bobs addons. It was suggested from a stack trace it may be this addon or the XAMP addon.

Post in thread '[OzzModz] Custom Field Default Value [Paid]'

Jan 23, 2024

btmgreg said:
Have been having issues for the past day or so - not sure why suddenly. I've probably got about 30 pages of errors with the same error.

We don't have any canViewArticleAttachments method calls in this add-on
This may be caused by AMP/AUN add-ons with outdated templates.

Updated - Developer Information: Method canViewArticleAttachments has been deprecated and will be removed in AMS 3.0

This is a notice to 3rd party developers that extend AMS... As per title, the method canViewArticleAttachments in the Article Item Entity has been deprecated and will be permanently removed in AMS 3.0. /** * @deprecated Use canViewAttachments instead * */ public...

xenaddons.com

Interested to see what you think

btmgreg · Feb 14, 2024

@mazzly Hey bud, I'm using a new setup (moved hosting) and I'm getting a callback error -

The callbacks for add-on updates seem to be blocked
Something seems to be blocking the callbacks about new add-on updates and API key changes. This prevents faster updates about new versions.
Instructions on how to unblock it with e.g. Cloudflare
(This message can be disabled from the add-on's options)

I don't use cloudflare and I'm cautious about changing server settings. Any tips specifically for this? I know I can disable the message, but I'd like it to work properly.

mazzly · Feb 15, 2024

btmgreg said:
@mazzly Hey bud, I'm using a new setup (moved hosting) and I'm getting a callback error -

I don't use cloudflare and I'm cautious about changing server settings. Any tips specifically for this? I know I can disable the message, but I'd like it to work properly.

It seems the /aun/-page on your site returns a normal page (with some message about multitracks) instead of the JSON endpoint that the add-on provides, (and the callback expects).
Also, the page is returned with the HTTP code 503 (Service Unavailable).

When working correctly and you visit the /aun/-page it should show you something like:

JSON:

{
    message: "GET is not valid",
    status: 400,
    visitor: {
        conversations_unread: "0",
        alerts_unviewed: "0",
        total_unread: "0"
    }
}

btmgreg · Feb 15, 2024

mazzly said:
It seems the /aun/-page on your site returns a normal page (with some message about multitracks) instead of the JSON endpoint that the add-on provides, (and the callback expects).
Also, the page is returned with the HTTP code 503 (Service Unavailable).

When working correctly and you visit the /aun/-page it should show you something like:

JSON:

{ message: "GET is not valid", status: 400, visitor: { conversations_unread: "0", alerts_unviewed: "0", total_unread: "0" } }

I just rebuilt the addon, and when visiting /aun/ I now get -

{
"message": "GET is not valid",
"status": 400,
"visitor": {
"conversations_unread": "24",
"alerts_unviewed": "3",
"total_unread": "27"
}
}

Hopefully that's that sorted out.

The callbacks for add-on updates seem to be blocked
Something seems to be blocking the callbacks about new add-on updates and API key changes. This prevents faster updates about new versions.
Instructions on how to unblock it with e.g. Cloudflare
(This message can be disabled from the add-on's options)

^ Message still there.

Add-on Update Notifier 1.1.8

Well-known member

Active member

Active member

Active member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

The callbacks for add-on updates seem to be blocked​

Similar threads

We value your privacy

The callbacks for add-on updates seem to be blocked