First, thanks very much for adding SVN read-only access. I admin a few repos and this is a really handy way to do updates on my colocated guild server. (I also use SVN to maintain most of my game addons, including Auctioneer, Omen, and Outfitter.)

I pulled the latest trunk, copied my conf.php from my old tarball-based install, and did the update from the web interface to update the database. I then clicked on the addons management page to install the vault addon. Went pretty smooth.

Most of my addons now show a purple square in the Installation column and complain that I overwrote them with an older version. (News and the freshly-installed Vault were the only ones showing anything else.)

From the main page, clicking on the Memberlist icon gets me the message/link "Click to Upgrade 2.0.0.0 to 1.9.9.1525". (Clicking on it appears to do nothing.)

Is this a DB issue? Do I need to tweak the DB to tell it the new version? Or should I be pulling addons from another place in the repo?

Here's what I see installed:

GuildBank v1.9.9.1431
Guild Info v1.9.9.1431
Character Information v1.9.9.1477
Instance Keys v1.9.9.1431
Members List v1.9.9.1525
News v1.9.9.1431
Professions v1.9.9.1431
PvP Log v1.9.9.1431
Quest List v1.9.9.1431
Guild Vault v1.9.9.1515

It's been a while since that, but the addon versioning changed from 2.0.0.0 to 1.9.9.svnrevision. The backend is coded not to accept decreasing version numbers, so you have to fix them in the DB manually.

UPDATE `roster_addons` SET `version` = '1.9.9';

Ok, thanks, that makes sense, and should be straightforward. I'll get to that right after my company xmas party today.

That worked. (I had to change the table name to roster_addon, singular.)

http://matureasskickers.net/wowroster/M ... list&a=g:2