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

True, but that does not cause this problem. The old lua parser only produced the wrong output at numeric keys, but CP only uses numeric keys in some spots for the actual data (bag contents, mailbox contents, that kind of stuff).

We have had the problem with no DBversion being read before, but that was at CP 2.0, when the location of the DBversion variable in the CP.lua changed.

Did update got



Parsing files

Parsed CharacterProfiler in 0.03 seconds

NOT Updating character [Evillives]
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.
Updating Character [Rbanktwo]
Rbanktwo is not in the list of guild members so their data will not be inserted.

Updating Guild [xxxxxxxxxx]
Member Log
Updated: 0
Added: 0
Removed: 0


Updating Members


So it updated and alt but not a main



Also the info from my CP lua states it is 2.0.0

It is possible to 'force' the usage of a i.e. 2.0.5 CharacterProfile version.

Just set up the roster to accept 2.0.5 as a CharacterProfiler version .... this is easy part.

Then - beware: you have to make it possible for your Guild Members to download a latest CharacterProfile.zip from a unique souce, controlled by you - the Roster maintainer. You could even adapt the links for this, present in the (localized) help code. Most Guilds have support forums - so throw it in the Download chapter.

Open de zip file : look for the CharacterProfiler.lua file.
Open it up - and change the version number (even the 2.0.5b public file version has an internal version of 2.0.0 but you already knew this - if not, you weren't reading this )

Look for this line (line 18):

PROFILEDB = "2.0.0";

and make it look like this :

PROFILEDB = "2.0.5";

ZIP it all up.
Make it public.

Your Guilder members are now obliged to use this 'patched' version.
Any other version (even the original 2.0.5b from RGPO are even later) will be refused.

YOU keep care of the "looking after the update" and you patch it.
Your Roster users will all use the same (latest) CharacterProfiler version.

Be careful: I tested this - and it works as presumed.
But I tend to ask myself 2 question:
1) Is the version number being thrown in the database (it is) - and what is its side effect (usage afterwards) ? In case of a downgrade because bug found afterwards etc..... I’ll have a look and re-edit here if needed.
2) It's already hard to push Guild Members to use the Roster (read : upgrade their character) make the download part as easy as possible.

One thing is for sure : this method helps to keep all needed Add On’s synchronised -, as it was meant to be in the first place.

Not very scienfitic or proper testing, but this issue seems to affect the PUBLIC update.php page.

When I update while logged into config it works fine, but when the public tries to upload they get this error.

any resolution for this problem yet? I'm getting that same message
"Data is from CharacterProfiler v
The version of CharacterProfiler used to capture data for this character is older than the minimum version" only when using uni-uploader. I can successfully upload using the roster update web forms page.

Upgraded from 1.7.0 to 1.7.2 and replaced the parser and wowdb files.

Anyone have an idea how to fix this?

Delete CharacterProfiler.lua and CharacterProfiler.lua.bak from your WTF/Account/<accountname>/SavedVariables/ directory and re-scan your characters

Sorry forget to mention I'd done that also. Repeated it just for grins.
No change. Same error. Next?

I don't know what to tell ya then
Re-Download CharaterProfiler

Version 2.05b straight off the site here. It's odd - seen various posts in a few threads of people getting this error - most seemed to have clear up for them - thought I'd covered all the issues, version 1.7.2, updated parser and wowdb, latest cp, clear the files. Upload by web form works - uni-uploader gives the minimum cp version error. Not sure where to look next?

ps my output from uni-uploader shows the cp version error,
then does PvPLog data fine
but then ends with:
Could not update "%s". Maybe its not set in configuration?
where the guild roster would be.
So both those fail here. Don't know if that means anything but thought I'd mention it.

Bump - still getting this problem with CharacterProfiler 2.06

Would sure love to fix this problem but still looking for ideas to try.

Anyone have anything else not already mentioned in this thread?

Marsman wrote:Bump - still getting this problem with CharacterProfiler 2.06
Would sure love to fix this problem but still looking for ideas to try.
Anyone have anything else not already mentioned in this thread?

So, if I get it well, updating using the update.php page 'by hand' goes well...
When using Uniloader, it won't work.
That's it ?

In that case : it's a UniLoader (settings) problem.

Let me assure you that a 1.7.3 WoWRoster & CharacterProfiler 2.0.6 'work from the box' when your ISP has the good version of (SQL, PHP etc - most have).

PS UniLoader has some 'debug option' - what are their results ?

Yes correct, manually uploading the data via web page seems to work.
Here again is a sample of what I'm getting with Uni-Uploader:

NOT Updating character [Character] <- this is odd
Data is from CharacterProfiler v <- roster set to 2.0.0
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.
Updating PvP Data for [Metalkane]
Updating PvP data
Wins: 21
Losses: 24
Set PvP ratio to 0.875

PvPLog data seems to be fine. I've purged, deleted the CP.lua file completely - gone over my uni-uploader settings with a fine tooth comb - nothing seems to be wrong, yet this is what I get. Extremely frustrating.
Just don't know where else to look at this point. Just did a roster diag for 1.7.3 and all files show green. I just can't imagine what the problem could be so I'm just begging for help at this point. ANY idea where to even look would be appreciated.

Are you using the right upload target file? This might be a result of uploading to admin/update.php, which isn't used anymore and isn't in the downloaded archive, but might still be there from an old install.

PleegWat wrote:Are you using the right upload target file? This might be a result of uploading to admin/update.php, which isn't used anymore and isn't in the downloaded archive, but might still be there from an old install.

This problem showed up after an upgrade from 1.7.0 to 1.7.2
All files were replaced at that time and I jsut upgraded to 1.7.3 - again replacing all files. As mentioned in the previous post - I ran a roster diagnostic and all file versions show sync with the SVN. Thus I'm pretty certain the update.php file is current. My upload target URL has been unchanged since version 1.7.0 so it should be pointed at the correct location.
This really has me stumped.

roster/admin/update.php isn't used
Make sure you are using roster/update.php