with the new client being able to install libraries seperately i have encountered a few packages where the author did not set them up properly. The *-nolib packages are missing the required libraries which do not have a standalone version.
At the moment i need to flag the package as ignored and install the complete package by hand. The client clearly states that separate library installs are optional and not supported by all authors.
Would it be possible to flag the packages that do not work as no-lib on the homepage so the C-Client can install the full package instead ? (and maybe notify the author that his meta information is wrong)
Maybe start by making a ticket for each effected addon to inform the authors and they might make a fast fix?
A question to the client:
Why is it complaining about my modifications to teksLoot but not for PitBull?
And how can I disable that warning? Because I don't want to have teksLoot at the top of the list all the time.
And I had a little bug:
When it installed FuBar it also installed a standalone version of LibRock-1.0 although the library is included in FuBar (and I use the normal way, so embedded libraries).
right click and select "toggle ignore" on the modified addon.
Would it be possible to flag the packages that do not work as no-lib on the homepage so the C-Client can install the full package instead ?
That would be AWESOME, because there are apparently a number of authors who either don't understand how .pkgmeta works or slapped their "support" together without testing - and I'd rather not be forced to update/hack it to work manually if it's actually available under the client.
After clicking Help > Instructions in 2.1.1.18 RC1, I'm taken to http://www.curse.com/content/ClientInstructions.aspx which seems to have instructions for an older version of the client. It may be important to keep this page as-is for when older clients access it, but if future clients would pass along their version numbers in the URL, you could display instructions for the version the user actually has installed.
After clicking Help > Instructions in 2.1.1.18 RC1, I'm taken to http://www.curse.com/content/ClientInstructions.aspx which seems to have instructions for an older version of the client. It may be important to keep this page as-is for when older clients access it, but if future clients would pass along their version numbers in the URL, you could display instructions for the version the user actually has installed.
I'm pretty sure that page will get updated once the Client has reached its release state and is spread to the general public :)
I'm pretty sure that page will get updated once the Client has reached its release state and is spread to the general public :)
I too assume the page will be updated. However, for users who do not automatically update their clients (or have problems with updating it), it may be important to keep that page intact, perhaps editing it to read "Your version of the Curse Client is outdated and no longer supported. Please update to the current version." at the top of the page, while newer client versions would be directed to a page with instructions specific to that version.
I'm starting to think that this build is not really qualified to be tagged as a release candidate when such important information is unavailable. Documentation should not be an afterthought. No one should seriously ask the question, "Is this build ready to be released?" when the instructions for using it aren't available to the users.
Does the CC ignore addons marked as "Ignored" when it gives it's little yellow arrow and "Some of your addons are out of date" at the top? If not, well, it should :P.
Does the CC ignore addons marked as "Ignored" when it gives it's little yellow arrow and "Some of your addons are out of date" at the top? If not, well, it should :P.
A question to the client:
Why is it complaining about my modifications to teksLoot but not for PitBull?
And how can I disable that warning? Because I don't want to have teksLoot at the top of the list all the time.
I just found out that the Curse Client doesn't look for updates for modified Addons at all. That's not good :(
I've done some small modifications to some of my Addon, but still want to update them via the Curse Client!
Is there any way to disable that "changes detection"?
eh, if you locally modify an addon the client should ignore that addon and not update it till you manually tell it to do so.
I don't want the CC overwriting local changes i've made. Though most of the time i've checked it out from the repo if that's the case.
Ok, you are correct, it should not automatically update it.
But right now it doesn't even check if there are new versions.
It may not know to check for new versions, because by you editing it, it is no longer the same addon and has no meaningful version of its own. (If you want something that tracks all your changes, you may want to use a repository client instead of the Curse client.)
To me it seems like if the client can detect these user-modified addons, they should be moved to the "Unknown Addons" tab and dealt with there in the customary manner.
If the client detects that it is a modified addon, then it knows which addon it is and should therefore know which version is the latest. Moving it to the Unknown section makes absolutely no sense, since it is not unknown.
Not current version - latest version available. At the moment it gets stuck on latest installed in both the current and latest fields.
Yes, that's the problem.
I would like to update my modified Addons with the Client because I can redo my changes in some seconds.
And I don't think that the Client detects the installed version out of the Addon files. It will rather save the installed version of each addon somewhere.
And I don't think that the Client detects the installed version out of the Addon files. It will rather save the installed version of each addon somewhere.
The client used to store the installed addon version in a previous life. Now it tries to get it from the "X-Curse-xxx" lines added by the packager in the .toc file.
The client used to store the installed addon version in a previous life. Now it tries to get it from the "X-Curse-xxx" lines added by the packager in the .toc file.
Ah, ok.
So as long as you don't change that line updating of modified Addons should work (of course you loose all modifications then).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Maybe start by making a ticket for each effected addon to inform the authors and they might make a fast fix?
right click and select "toggle ignore" on the modified addon.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIgnore means that it won't be updated, right? Then I don't want to ignore it ;)
Btw: I edited my last post.
already done so Kerecha
-
View User Profile
-
View Posts
-
Send Message
Project AuthorThat would be AWESOME, because there are apparently a number of authors who either don't understand how .pkgmeta works or slapped their "support" together without testing - and I'd rather not be forced to update/hack it to work manually if it's actually available under the client.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorI'm pretty sure that page will get updated once the Client has reached its release state and is spread to the general public :)
I too assume the page will be updated. However, for users who do not automatically update their clients (or have problems with updating it), it may be important to keep that page intact, perhaps editing it to read "Your version of the Curse Client is outdated and no longer supported. Please update to the current version." at the top of the page, while newer client versions would be directed to a page with instructions specific to that version.
I'm starting to think that this build is not really qualified to be tagged as a release candidate when such important information is unavailable. Documentation should not be an afterthought. No one should seriously ask the question, "Is this build ready to be released?" when the instructions for using it aren't available to the users.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNoticed that too. Seems we should file a ticket.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI just found out that the Curse Client doesn't look for updates for modified Addons at all. That's not good :(
I've done some small modifications to some of my Addon, but still want to update them via the Curse Client!
Is there any way to disable that "changes detection"?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI don't want the CC overwriting local changes i've made. Though most of the time i've checked it out from the repo if that's the case.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBut right now it doesn't even check if there are new versions.
It may not know to check for new versions, because by you editing it, it is no longer the same addon and has no meaningful version of its own. (If you want something that tracks all your changes, you may want to use a repository client instead of the Curse client.)
To me it seems like if the client can detect these user-modified addons, they should be moved to the "Unknown Addons" tab and dealt with there in the customary manner.
-
View User Profile
-
View Posts
-
Send Message
Project Author-
View User Profile
-
View Posts
-
Send Message
Project Author-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYes, that's the problem.
I would like to update my modified Addons with the Client because I can redo my changes in some seconds.
And I don't think that the Client detects the installed version out of the Addon files. It will rather save the installed version of each addon somewhere.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe client used to store the installed addon version in a previous life. Now it tries to get it from the "X-Curse-xxx" lines added by the packager in the .toc file.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAh, ok.
So as long as you don't change that line updating of modified Addons should work (of course you loose all modifications then).