Anyone else having the issue that the Client doesn't find available updates for some Addons?
Currently it doesn't find the following ones for me:
* PitBull4 v4.0.0-beta9-6 (shows v4.0.0-beta9-1 as latest)
* SickOfClickingDailies v6.3.7b-beta (shows v6.3.7a-beta as latest)
* BigWigs r7456 (shows r7455 as latest)
(Of course I've set them all to install type Alpha.)
And for SickOfClickingDailies it also seems like the copy from WowAce to Curse is broken because v6.3.7a-beta is also there shown to be the latest.
But for other Addons (like !BugGrabber and Recount) it finds the latest version like normal.
i have also some addons listed as installed, but i dont have them. and i dont want to use them. some examples are titan panel (i use bazooka) or gearscore (i will never use gs).
i'm on a mac and the client is really bad now. v3 died, and v4 does not have the option to install libs separately
Tools => Options => Games & AddOns => Select "World of Warcraft" => Tick "Install separately (not recommended)" at "Library Preference:" => Click "Reset All" => Re-install all AddOns
If you don't know exactly what this does, and what the consequences are, don't do it. The default setting was chosen for a reason. Normal users should not change this. If addons aren't showing up in the Curse Client, that's either a bug in the Curse Client, or a temporary glitch with the Curse.com server. Creating a giant mess in your addons folder that you don't actually understand is not a good solution. :|
Maybe this will help, maybe it won't: Tools menu, Options, Games & Addons, World of Warcraft, and change the release type from the default "Release" to "Beta". It is not recommended to blanket-case change the type to "Alpha" as you could seriously mess up your addons.
Anyway, changing to "Beta" has worked for me, finding some updates that the normal "Release" scan doesn't catch.
Release: Thoroughly tested, stable, intended for use by everyone. Should never generate errors, at least in the version of WoW it was written for. Most users should only use versions designated at "Release".
Beta: Somewhat tested, generally stable, probably okay for use for by everyone, but if you're in the "I can install an addon but that's about it" crowd you should probably avoid it. May generate an occasional error.
Alpha: May not have been tested at all, possibly unstable, not recommended for use by anyone who isn't comfortable with having to revert to earlier versions at inconvenient times and/or edit Lua to fix errors. May generate lots of errors, or not work at all.
----
If the Curse Client isn't finding any new versions, make sure that there actually are new versions for it to find. Unless an addon is broken, there's not really any need to update, so many authors go quite a while between new "Release" versions.
Okay, well, the Client is definitely not finding some updates.
I last updated my addon GridStatusHealingReduced on April 25th, and that update (3.3.3.42) correctly appears on both the addon's CurseForge page and Curse page, and is what you get when you click the primary Download button on either page.
However, the Curse Client is still showing a version from December 18th (3.3.0.39). This is especially problematic because that old version isn't even compatible with current versions of Grid anymore.
Setting the Client's download preference for Release/Beta/Alpha made no difference, though I wouldn't expect it to since all of my addon files are manually uploaded and marked as Release versions.
I can't see how this could be a temporary server issue, as it's had about two weeks to pick up on the update, and hasn't, despite having picked up thousands of updates for other addons during the same time period. :|
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumCurrently it doesn't find the following ones for me:
* PitBull4 v4.0.0-beta9-6 (shows v4.0.0-beta9-1 as latest)
* SickOfClickingDailies v6.3.7b-beta (shows v6.3.7a-beta as latest)
* BigWigs r7456 (shows r7455 as latest)
(Of course I've set them all to install type Alpha.)
And for SickOfClickingDailies it also seems like the copy from WowAce to Curse is broken because v6.3.7a-beta is also there shown to be the latest.
But for other Addons (like !BugGrabber and Recount) it finds the latest version like normal.
edit: Seems like everything is working again :)
i'm on a mac and the client is really bad now. v3 died, and v4 does not have the option to install libs separately
If you don't know exactly what this does, and what the consequences are, don't do it. The default setting was chosen for a reason. Normal users should not change this. If addons aren't showing up in the Curse Client, that's either a bug in the Curse Client, or a temporary glitch with the Curse.com server. Creating a giant mess in your addons folder that you don't actually understand is not a good solution. :|
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAnyway, changing to "Beta" has worked for me, finding some updates that the normal "Release" scan doesn't catch.
Beta: Somewhat tested, generally stable, probably okay for use for by everyone, but if you're in the "I can install an addon but that's about it" crowd you should probably avoid it. May generate an occasional error.
Alpha: May not have been tested at all, possibly unstable, not recommended for use by anyone who isn't comfortable with having to revert to earlier versions at inconvenient times and/or edit Lua to fix errors. May generate lots of errors, or not work at all.
----
If the Curse Client isn't finding any new versions, make sure that there actually are new versions for it to find. Unless an addon is broken, there's not really any need to update, so many authors go quite a while between new "Release" versions.
I last updated my addon GridStatusHealingReduced on April 25th, and that update (3.3.3.42) correctly appears on both the addon's CurseForge page and Curse page, and is what you get when you click the primary Download button on either page.
However, the Curse Client is still showing a version from December 18th (3.3.0.39). This is especially problematic because that old version isn't even compatible with current versions of Grid anymore.
Setting the Client's download preference for Release/Beta/Alpha made no difference, though I wouldn't expect it to since all of my addon files are manually uploaded and marked as Release versions.
I can't see how this could be a temporary server issue, as it's had about two weeks to pick up on the update, and hasn't, despite having picked up thousands of updates for other addons during the same time period. :|