I set the rosterconfig to require a minimum CP version of 2.0.3. When uploading data created with CP 2.0.4 the roster (1.7.2) gives me an error saying that my CP data is version 2.0.0.

I deleted all CharacterProfiler data, installed CP 2.0.5b and tried again with the same results. Roster still tells me I'm trying to upload CP 2.0.0 data.

Then I checked the CharacterProfiler.lua file and found there's two values there:

database version = 2.0.0
cp version = 2.0.5

Is roster by any chance looking at the wrong version number?

DMrazor.

Roster checks the database version in CP and GP
As of right now, it is still 2.0.0

Ok, thanks for clarifying that. The way it's set in the config *is* kind of confusing though.

Anyway... I'll just leave it at 2.0.0 for now.

Dmrazor.

I'm having the same problem. The values for both CP and GP in config are 2.0.0. I'm using the latest addon versions CP 2.0.5b and GP 2.0.3. I get this error:

Data is from CharacterProfiler v
The version of CharacterProfiler used to capture data for this character is older than the minimum version allowed for upload.
Please ensure you are running at least v2.0.0 and have logged onto this character and saved data using this version.
Could not update "". Maybe its not set in configuration?

I did update my luaparser.php and wowdb.php files.

Did you manage to resolve this? How?

Some of my users are reporting the same problem.

Clean install of all their addons after TBC, with CP 2.0.5b and some are reporting getting that error about CP being to old.

/bump

Same issues, clean installs and latest versions

/cp purge all (in WoW)

This normally fixes this error for me.

purging in game doesnt help

The CP version that is being tested is the dbversion property. This is only incremented if the data format version of CP changes. Since the way the CP data is stored has not changed since CP 2.0.0, the dbversion is still 2.0.0, and you should put that version in your roster config.

I believe the current use of these variables is flawed. The DBVersion should be a hard coded define in the lua parsing of WoW Roster. If this should ever change -- Meaning the db structure has changed this would mean that the actual code/db would need to be updated thus the update process should not be allowed to complete. Currently the configuration option to set this min version level is rather pointless. It makes much more sense to use the CPVersion flags for version checking. This would allow the admin of the roster to force certain mod versions for uploading character profiles.

Roster: 1.7.2
CP : 2.0.5b
GP : 2.0.5

Error:

Data is from CharacterProfiler v
The version of CharacterProfiler used to capture data for this character is older than the minimum version allowed for upload.
Please ensure you are running at least v2.0.0 and have logged onto this character and saved data using this version.
Could not update ""


RPG outfitters said I need to ask you guys what the issue may be.

All are clean installs.
Old files were deleted before installing the new ones.
In game /cp purge all was done.

not sure where to look from here

Evillives wrote:Data is from CharacterProfiler v

Character Profiler is not even storing the variable information. It is a patch day so are you loading out of date addons? Is some other addon breaking the scanning of CP? Try to disable all addons except for CP/GP then make sure CP is actually saving your info by opening the CP.lua file. (or post the file here and we can look for you).

I just checked th cp.lua file
the version is set up with 2.0.0 whereas I installed the 2.0.5

To ANYONE
Make sure you get the patch for 1.7.2
http://www.wowroster.net/Forums/viewtopic/t=2289.html

Zanix

I have a fresh install as of about 3 hours ago, with the patched files you are pointint me to.

I was able to initally update my guild roster and personal profile.

I went in game and changed some ranks of people, came back out and got this save error with no V number in it.

So I went in game purged all and re-exported.

Now its saying Could not update "%s". Maybe its not set in configuration?

Theres definately a problem