Since WowAce and Curseforge were migrated a few days ago all WoW addons that have updates available are shown as "modified" in the Curse App. This is not only wrong but also annoying because it renders the "update all" button useless. This even applies to addons that were already updated multiple times since the migration - e.g. BigWigs.
Some addons - for me at least BigWigs - also get reset to install alpha versions each time the App is started or the refresh button is used. Even if I manually select beta versions again and update once so that only a beta (or in the case right now a release) is installed, the next refresh resets the option to alpha again. Resetting all addons to beta via the option menu also doesn't fix it.
Also broken since the site migration is the display of the changelogs generated by a Git commit log. Line breaks are missing there which makes those changelogs very hard to read.
I'm using the latest Curse App (version 7.1.6164.2253).
I can confirm that the "modified" tag is both prevalent, and random which AddOns get the tag. It isn't always the same AddOns each time the Curse App loads.
I've seen libraries, Ace3, and core AddOns being affected.
And yes, once you select a "modified" AddOn and update it, it corrects itself until the next time the Curse App refreshes itself, checking for updates. I use the default setting of once per hour. Therefore, every hour, the app randomly selects new Addons to have the "modified" tag, but that does not mean existing affected AddOns are cured. In fact, they remain "modified".
This was fixed the day after, can you confirm its correct now?
Yes. Quite literally, I read this, went to the Curse App, clicked Reinstall, which corrected the install. Then I clicked Refresh and it is instantly back to modified.
This was fixed the day after, can you confirm its correct now?
Yes. Quite literally, I read this, went to the Curse App, clicked Reinstall, which corrected the install. Then I clicked Refresh and it is instantly back to modified.
I have most of my AddOns, including LibGuildBankComm, set to Beta as the preferred release type to install. In the Curse App, I have it set to install libraries separately.
Update: in order to force a new zip, I added some spaces to the header of the main Lua file, and updated the SVN repository keywords (TortoiseSVN - Properties). Then I tried to push a commit, to which I got the following error:
Command: Commit
Modified: G:\bankcomm\LibGuildBankComm-1.0.lua
Sending content: G:\bankcomm\LibGuildBankComm-1.0.lua
Committing transaction...:
Error: Commit failed (details follow):
Error: Commit blocked by pre-commit hook (exit code 1) with output:
Error: This repository has been migrated and is permanently in read-only mode. Please
Error: see https://www.curseforge.com/docs/repomigration for details.
Error: If you want to break the lock, use the 'Check For Modifications' dialog or the repository browser.
Completed!:
The URLs have changed, you need to update them. Also the packager currently bugs out with SVN External and it's old/bad practice to use them anyway, so might wanna stop doing it.
Okay, I can update all my URLs and check out the repo with the new link. I'll bite on why SVN Externals are bad. The .pkgmeta docs still have it listed, albeit any support libraries will also need updated URLs. And the example on the linked doc page will need updating as well.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSince WowAce and Curseforge were migrated a few days ago all WoW addons that have updates available are shown as "modified" in the Curse App. This is not only wrong but also annoying because it renders the "update all" button useless. This even applies to addons that were already updated multiple times since the migration - e.g. BigWigs.
Some addons - for me at least BigWigs - also get reset to install alpha versions each time the App is started or the refresh button is used. Even if I manually select beta versions again and update once so that only a beta (or in the case right now a release) is installed, the next refresh resets the option to alpha again. Resetting all addons to beta via the option menu also doesn't fix it.
Also broken since the site migration is the display of the changelogs generated by a Git commit log. Line breaks are missing there which makes those changelogs very hard to read.
I'm using the latest Curse App (version 7.1.6164.2253).
That's for the reports, these are being looked into :)
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorI can confirm that the "modified" tag is both prevalent, and random which AddOns get the tag. It isn't always the same AddOns each time the Curse App loads.
I've seen libraries, Ace3, and core AddOns being affected.
And yes, once you select a "modified" AddOn and update it, it corrects itself until the next time the Curse App refreshes itself, checking for updates. I use the default setting of once per hour. Therefore, every hour, the app randomly selects new Addons to have the "modified" tag, but that does not mean existing affected AddOns are cured. In fact, they remain "modified".
There turned out to be a few bugs resulting in this, this should be fixed today after all of the files finish reprocessing.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYay! When I refreshed it just now the 5 addons at top that said Modified all switched to Update!
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorI see LibGuildBankComm-1.0 is still modified.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorI have most of my AddOns, including LibGuildBankComm, set to Beta as the preferred release type to install. In the Curse App, I have it set to install libraries separately.
LGBC is installed as part of MobileVault.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorI just deleted Mobile Vault, which removed LibCompress and LibGuildBankComm. Then I reinstalled Mobile Vault. LGBC is still modified.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorUpdate: in order to force a new zip, I added some spaces to the header of the main Lua file, and updated the SVN repository keywords (TortoiseSVN - Properties). Then I tried to push a commit, to which I got the following error:
https://www.curseforge.com/docs/repomigration gets a 404 "That was unexpected" missing page, so that's no help. Why on earth is this project in read-only mode?
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorThe URLs have changed, you need to update them. Also the packager currently bugs out with SVN External and it's old/bad practice to use them anyway, so might wanna stop doing it.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorOkay, I can update all my URLs and check out the repo with the new link. I'll bite on why SVN Externals are bad. The .pkgmeta docs still have it listed, albeit any support libraries will also need updated URLs. And the example on the linked doc page will need updating as well.