Version numbers of all the addon distributed with Roster were set to the current svn revision number (1.9.9.1431)

This will show that you have replaced an addon with an older version in RosterCP->Manage AddOns

To fix this, simply edit the database directly
Table: roster_addon
For each Roster bundled addon, change the version field to

Code: Select all

1.9.9.1432

Or you can use this sql code

Code: Select all

UPDATE `roster_addon` SET `version` = '1.9.9.1431' WHERE `basename` IN('guildbank','guildinfo','info','keys','memberslist','news','professions','pvplog','questlist');

This was done because it will be easier to upgrade these addons as the beta moves along and so they can be called 2.0.0 on the release of Roster

zanix wrote:...
Or you can use this sql code

Code: Select all

UPDATE `roster_addon` SET `version` = '1.9.9.1431' WHERE `basename` IN('guildbank','guildinfo','info','keys','memberslist','news','professions','pvplog','questlist');

Get it.

And me running arround with 1.9.9.1431 on my clipboard using PHPMyAdmin in the roster addon config table ....

At least, I know now for sure that I understood the purple-square problem.

Thanks for the one-liner ^^

LoL
Hover over the purple square

zanix wrote:Hover over the purple square

I did, saw
You have overwrote your current addon installation with an older version. Replace files with latest version
... when I was upgrading.
It was that, or Zanix went 'Paris mode fashion'.

Btw: Vault importing from Tabx, Log (per Tab) and Money works well. All 3 tables are filled up correctly.

I already yelled at zanix for that. Addon version numbers shouldn't decrease.

PleegWat wrote:I already yelled at zanix for that. Addon version numbers shouldn't decrease.

No they shouldn't
But they also shouldn't have been set to 2.0 yet either

I plead innocent on that one. I've never set one higher than 1.8.0-0

Yeah, its all my fault...

Who cares :shock:

You both earn many and for 1 thousand other reasons ^^