is an article I wrote after encounternig similar problems and finding the "correct" way to fix them. It may help some people, but take the advice with a pinch of salt until I get more feedback on the article's accuracy.
Useful article, considering the vast number of Ace'd addons I'm using now I made the switch to standalone libraries instead of embedded with the help of your article. Only problem I had...
!!!StandaloneLibraries zip file and extract all the empty folders to your interface/addon folder
No matter how many times I downloaded and extracted the empty folder structure to my addon folder then updated my addons using WAU, I kept ending up with an empty !!!StandaloneLibraries folder except for 2 documents. The empty folder structure would be there prior to using WAU, gone afterwards and no libraries ever appeared. Eventually I used !!!Libs instead and everything is working as intended, no embedded libraries and everything present as a standalone.
Is this me doing something wrong or a correction to make to your article?
Either way, much appreciate the link, you should add it to the Tutorials wiki page.
Using the Tortoise Svn downloader, grabbing all the recent versions of my favorite addons hasn't been a problem nor has getting them to work which has been off the bat. Had a few issues with Errors coming up with 15264 downloading, then it finding 15265 then not being able to finish the download, but redownloading worked fine.
The problem stems from people expecting addons to be bugfree on svn.wowace.com or www.wowace.com/files.
The zipped files are snapshots from the SVN, created everytime a dev commits something to their addon. It is not at all guaranteed to work. Heck, half the time I just drycode stuff, commit and then a few hours later boot WoW to check if it works.
Complaining all your addons broke into smithereens because you updated them all and one of the libs contained an error will usually not work, since most of the time the lib itself will already be fixed, but all the .zip's that were generated during that time contain the bad lib.
So the solution is either to use a SVN client, or just wait for WoWi/Curse releases.
So then what is the point of aceupdater and /files/?
Speed, convenience, and not having load a SVN client.
My method of avoiding all this is:
1) I went and got !!!StandaloneLibraries and followed the instructions in the ReadMeDammit!
2)Use the updater to update most of my addons
3) Use Tortoise to update a few, lib intensive addons, grabbing the most recent for many that way.
Sure, it may be a bit heavy handed, but since I started doing this I have had next to nil Library issues. And since only one copy stays in memory and I really don't get panty-bunched due to initial load up times, I'm happy.
I also use Wizz RSS in Firefox to see what commits have happened and if'n I even need to update.