So, kinda newbie question here, but any reason why my addon would have stopped appearing in Curse Client? I uploaded a new version several weeks ago, and then a new one yesterday, and neither appears in Curse Client. An old version used to be in there, but that is gone now, too.
Weird. The curseforge.com page (the "project site") lists those files as formal releases, and going to the curse.com page correctly notes "last updated 84 minutes ago", but there's no actual file to download.
Nothing obviously wrong at your end, this may require an admin to fix. If you aim the Torhal-signal at the clouds, I'll go get fresh lightbulbs.
So - problem solved! The new upload (v2.1) does indeed populate to Curse Client. Here's what I've figured out, in case anyone else has this issue:
The folder name inside my package, at some point, picked up an errant space in the name. This space seems to have affected how the file gets handled on the Curse back end. Removed the space, now things seem to be fine.
Latest version now available at the link above or via Curse Client!
Aye - if the folder name doesn't match the name of the ToC file, WoW won't run it; the Curse Client takes this into account and doesn't serve it up to users.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
So, kinda newbie question here, but any reason why my addon would have stopped appearing in Curse Client? I uploaded a new version several weeks ago, and then a new one yesterday, and neither appears in Curse Client. An old version used to be in there, but that is gone now, too.
Addon is BetterTooltips (http://wow.curseforge.com/addons/bettertooltips/)
BTW, no repository; package & zip everything here on the desktop, then upload to CurseForge.
Any thoughts?
Thanks!
- Mal
Nothing obviously wrong at your end, this may require an admin to fix. If you aim the Torhal-signal at the clouds, I'll go get fresh lightbulbs.
I just uploaded a completely fresh build & package; let's see how that one goes... and then it's Torhal-signal time.
- Mal
So - problem solved! The new upload (v2.1) does indeed populate to Curse Client. Here's what I've figured out, in case anyone else has this issue:
The folder name inside my package, at some point, picked up an errant space in the name. This space seems to have affected how the file gets handled on the Curse back end. Removed the space, now things seem to be fine.
Latest version now available at the link above or via Curse Client!
Cheers, and thanks!
- Mal