I'm having problems installing CosmosUI addons. The ones in the list aren't updating, and when I pick Install From > CosmosUI, the list is empty.
My uneducated guess is that it's because the URL http://www.cosmosui.org/addons.php doesn't list the addons anymore. I don't know if this is a temporary issue over at cosmosui.org, or if it's a permanent design change for their site. Anyone have any thoughts?
Looking at the news on their front page, it looks like they are having some data corruption issues with their server(s), and that the files are currently unavailable.
1) Generic SVN Support, so that all you put in for a Site ID is a proper svn path - or it auto detects the directory (or it's flaged) and just does a svn up on it.
2) Generic git Support. Either same, automatic interaction or flagging of the directory. because git is much more complicated than svn we figured out that it should do a few things first so it dosn't mess things up.
IIRC and someone is going to need to correct me, but it was "git fetch" then do a compare of the local structure and make sure it's not been locally modified then do a "git pull" else warn the user and keep moving. as a beta tester we're prolly not going to be making local changes but if it's an author we don't want to loose local changes.
1) Generic SVN Support, so that all you put in for a Site ID is a proper svn path - or it auto detects the directory (or it's flaged) and just does a svn up on it.
2) Generic git Support. Either same, automatic interaction or flagging of the directory. because git is much more complicated than svn we figured out that it should do a few things first so it dosn't mess things up.
IIRC and someone is going to need to correct me, but it was "git fetch" then do a compare of the local structure and make sure it's not been locally modified then do a "git pull" else warn the user and keep moving. as a beta tester we're prolly not going to be making local changes but if it's an author we don't want to loose local changes.
1) SVN is definitely something I'll implement, since that's fairly easy to handle (revision numbers are ever increasing, so a newer version is easy to detect)
2) Git, however, is something I don't know much about - I played a bit with Git on Windows, and it doesn't have any "version numbers" per se, so I guess a major change on some level would have to be done to handle "version number-less" addons (looking for changes would be one way to do it, the other way is to assume it's updated and just "git fetch" every time)
Uploading a new version with some bug fixes right now, hoping to get 1.8 out before September ;)
Hello,
since a few days I can't update Addons from Curse. I think Curse changed the download links. I'm using v1.6.520. Can someone tell me how to fix it or release a fix for v1.6.520?
Thank you.
Hello,
since a few days I can't update Addons from Curse. I think Curse changed the download links. I'm using v1.6.520. Can someone tell me how to fix it or release a fix for v1.6.520?
Thank you.
Cu
Cigaro
Try to download the beta version. I'm pretty stable and my Curse updates are working ok here.
If I install a new addon and setup it as curse, the addon fetches the online version but can't update(local version stays as ?). If I try to install through the url, I get error. Using beta.
Yes, now I noticed the problem too. Probably it started a while ago. Maybe Curse changed the path as someone said.
By the way, another good modification would be a small change in the online DB. Sometimes it has a wrong path for an addon and I have to setup it manually. That's not really a problem, but when I send my own DB online to try to correct the path, it seems the online DB stays with the wrong one. I don't know how it's updated, but it'd be nice if the last modification of an addon's path remained in the DB as the default path.
Yeah, Curse hasn't updated for me either. However, thanks to WUU being open source, and that I know regular expressions, I took a shot at fixing the problem. Being a Unix geek, I know regular expressions, so...
In your WUU directory, open the "site_re.txt" file. Look for the line starting with "curse_realdl" and replace that line with this one:
Note that this is not for the beta version, this is for 1.6.520. Don't see why it wouldn't work for the beta, if it has the same problem. Hopefully this will work for anyone else having this problem. Seems to work for me. I just deleted an addon and was able to update it back into existence.
A huge thanks to the author of this program... You kick ass. I hope this will continue to be updated and maintained in the future! Not feeling optimistic about that at the moment, however. Previously, such things were fixed very quickly, and that hasn't happened this time. So if the author is around and reads this, a comment on the future of this excellent program would be highly appreciated.
And hope this helps you all get back to updating properly.
Yeah, Curse hasn't updated for me either. However, thanks to WUU being open source, and that I know regular expressions, I took a shot at fixing the problem. Being a Unix geek, I know regular expressions, so...
In your WUU directory, open the "site_re.txt" file. Look for the line starting with "curse_realdl" and replace that line with this one:
Note that this is not for the beta version, this is for 1.6.520. Don't see why it wouldn't work for the beta, if it has the same problem. Hopefully this will work for anyone else having this problem. Seems to work for me. I just deleted an addon and was able to update it back into existence.
A huge thanks to the author of this program... You kick ass. I hope this will continue to be updated and maintained in the future! Not feeling optimistic about that at the moment, however. Previously, such things were fixed very quickly, and that hasn't happened this time. So if the author is around and reads this, a comment on the future of this excellent program would be highly appreciated.
And hope this helps you all get back to updating properly.
Grep.
Really don't know why, but it seems this fix is not working with beta. Getting this error:
2008-08-14 18:58:17: (WARN) No download URL found for Dominos
Really don't know why, but it seems this fix is not working with beta. Getting this error:
Hm, I'll have to install the beta client and give it a try. Perhaps something changed in the regular expressions. Not a clue.
May be a bit before I have a chance to try, however, as I have raiding tonight through Sunday. I'll try and mess around with it see if I can figure it out as soon as I have a chance.
Wish it printed the URL it tried to use in the error message...
EDIT: I think I found the problem. Between curse_realdl and the rest of the line, there should be a tab character. Seems like it gets turned into spaces on this forum. I tried it with the beta, and it works with a tab character there, but seemed to fail when it had spaces.
I just got home from vacation, and I'm dead tired from being on the move for about 10 hours, but I pushed your change to SVN and auto-update, so all clients should have it now :)
Thanks for the fix of curse downloads, it works perfect with v1.6.520. Now I've found a new download problem at the Auctioneer Addon. I use the AuctioneerClassicSuite, it shows zhe new Version, but can't download it. Can you fix it?
I just got home from vacation, and I'm dead tired from being on the move for about 10 hours, but I pushed your change to SVN and auto-update, so all clients should have it now :)
My pleasure, glad to help!
Cigaro, not sure, as I have the same problem. I just grab the version off WoWInterface, atm, problem solved for me, in a way. In the middle of my raid days, so doubt I'll have time to work out all the regular expressions for it in the short term.
Might be something on WUU's Wiki. I'll let you know if I get it working, if nobody beats me to it. And glad this worked for you with Curse!
Will the changes to Wowace and curse having their own updater affect Wowui?
Also curse is not updating for me also.
To be honest, I don't know much about the changes - I barely glanced at the threads earlier this morning, but couldn't get a full picture. I'll probably look into it when I get time, but WUU (and any other "third-party" addon manager) is pretty much a freeloader on this site, so I guess we won't get high priority.
As for me, I'll keep updating WUU as long as it actually does some work and people use it - and if that day comes when it's basically useless (and/or the number of bugs overtake the number of active users ;)) I'll release whatever I have as the "final" version and let that be the end of it.
To quote the "future of WoWAce" thread:
Quote from Kaelten »
No the new WowAce will have project pages. As far as the third party updaters, in the future we are looking at the possibility of having an api for third party updaters. However it'd be a feature for Premium users. I'm not sure of any timelines on when that'll become a reality and I can't promise anything, but I am working to get this pushed through.
(emphasis mine)
I'll probably implement this API when it becomes available - I try to keep WUU as friendly to the addon pages as possible (with regards to bandwidth usage and general hitting of pages), but other than that I guess WUU development won't be very active after I release 1.8 - there's little new to do, and the major bugs/problems require huge changes in code to "work right" (the things you've learnt to accept as "WUU peculiarities", and that every new user posts in this thread when they start using the program ;))
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
My uneducated guess is that it's because the URL http://www.cosmosui.org/addons.php doesn't list the addons anymore. I don't know if this is a temporary issue over at cosmosui.org, or if it's a permanent design change for their site. Anyone have any thoughts?
This is with 1.7.583.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWondering / 2 feature requests
1) Generic SVN Support, so that all you put in for a Site ID is a proper svn path - or it auto detects the directory (or it's flaged) and just does a svn up on it.
2) Generic git Support. Either same, automatic interaction or flagging of the directory. because git is much more complicated than svn we figured out that it should do a few things first so it dosn't mess things up.
IIRC and someone is going to need to correct me, but it was "git fetch" then do a compare of the local structure and make sure it's not been locally modified then do a "git pull" else warn the user and keep moving. as a beta tester we're prolly not going to be making local changes but if it's an author we don't want to loose local changes.
1) SVN is definitely something I'll implement, since that's fairly easy to handle (revision numbers are ever increasing, so a newer version is easy to detect)
2) Git, however, is something I don't know much about - I played a bit with Git on Windows, and it doesn't have any "version numbers" per se, so I guess a major change on some level would have to be done to handle "version number-less" addons (looking for changes would be one way to do it, the other way is to assume it's updated and just "git fetch" every time)
Uploading a new version with some bug fixes right now, hoping to get 1.8 out before September ;)
WUU 1.7.584 osx
WUU 1.7.584 osx light version
WUU 1.7.584 source/linux
MD5 sums:
1.7.584 beta (2008.08.05):
* Bugfix: "NoneType is not iterable"
* Better handling of website issues when smartupdating
* Bugfix: RAR file unpacking on non-Windows platforms
I still have some minor bugs to fix here, but they require lots of fine tuning to work correctly :(
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBtw, can you add a column to show the last time the addon was update insde WoWAce window? It's useful to know if an addon is abandoned or not.
since a few days I can't update Addons from Curse. I think Curse changed the download links. I'm using v1.6.520. Can someone tell me how to fix it or release a fix for v1.6.520?
Thank you.
Cu
Cigaro
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTry to download the beta version. I'm pretty stable and my Curse updates are working ok here.
If I install a new addon and setup it as curse, the addon fetches the online version but can't update(local version stays as ?). If I try to install through the url, I get error. Using beta.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBy the way, another good modification would be a small change in the online DB. Sometimes it has a wrong path for an addon and I have to setup it manually. That's not really a problem, but when I send my own DB online to try to correct the path, it seems the online DB stays with the wrong one. I don't know how it's updated, but it'd be nice if the last modification of an addon's path remained in the DB as the default path.
Is this normal behavior for the processing of addon packages? I don't recall seeing these errors in the past.
This is using the newest beta: 1.7.584
EDIT:
BTW, I'm also experiencing the CurseGaming addons no longer being fetched properly in this version.
Also curse is not updating for me also.
In your WUU directory, open the "site_re.txt" file. Look for the line starting with "curse_realdl" and replace that line with this one:
curse_realdl <a\shref="(http://media\d{0,2}.+?)" class="button button-pop">Note that this is not for the beta version, this is for 1.6.520. Don't see why it wouldn't work for the beta, if it has the same problem. Hopefully this will work for anyone else having this problem. Seems to work for me. I just deleted an addon and was able to update it back into existence.
A huge thanks to the author of this program... You kick ass. I hope this will continue to be updated and maintained in the future! Not feeling optimistic about that at the moment, however. Previously, such things were fixed very quickly, and that hasn't happened this time. So if the author is around and reads this, a comment on the future of this excellent program would be highly appreciated.
And hope this helps you all get back to updating properly.
Grep.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumReally don't know why, but it seems this fix is not working with beta. Getting this error:
Hm, I'll have to install the beta client and give it a try. Perhaps something changed in the regular expressions. Not a clue.
May be a bit before I have a chance to try, however, as I have raiding tonight through Sunday. I'll try and mess around with it see if I can figure it out as soon as I have a chance.
Wish it printed the URL it tried to use in the error message...
EDIT: I think I found the problem. Between curse_realdl and the rest of the line, there should be a tab character. Seems like it gets turned into spaces on this forum. I tried it with the beta, and it works with a tab character there, but seemed to fail when it had spaces.
So try that and let me know if it works.
I just got home from vacation, and I'm dead tired from being on the move for about 10 hours, but I pushed your change to SVN and auto-update, so all clients should have it now :)
My pleasure, glad to help!
Cigaro, not sure, as I have the same problem. I just grab the version off WoWInterface, atm, problem solved for me, in a way. In the middle of my raid days, so doubt I'll have time to work out all the regular expressions for it in the short term.
Might be something on WUU's Wiki. I'll let you know if I get it working, if nobody beats me to it. And glad this worked for you with Curse!
To be honest, I don't know much about the changes - I barely glanced at the threads earlier this morning, but couldn't get a full picture. I'll probably look into it when I get time, but WUU (and any other "third-party" addon manager) is pretty much a freeloader on this site, so I guess we won't get high priority.
As for me, I'll keep updating WUU as long as it actually does some work and people use it - and if that day comes when it's basically useless (and/or the number of bugs overtake the number of active users ;)) I'll release whatever I have as the "final" version and let that be the end of it.
To quote the "future of WoWAce" thread:
(emphasis mine)
I'll probably implement this API when it becomes available - I try to keep WUU as friendly to the addon pages as possible (with regards to bandwidth usage and general hitting of pages), but other than that I guess WUU development won't be very active after I release 1.8 - there's little new to do, and the major bugs/problems require huge changes in code to "work right" (the things you've learnt to accept as "WUU peculiarities", and that every new user posts in this thread when they start using the program ;))