In Collaboration System value of a rating in Thread and Collaboration sometimes does not coincide. As far as I remember, in the winter it corrected, the additional column in a database has been added. Nevertheless, sometimes value in these columns (Thread.threadRating & Post.rating) can sometimes not coincide themselves and with amount of voices (table: Post_rating). At a divergence of values I have not noticed any law.
I tried manually to count voices (it the table: Post_rating) and to correct value directly in base (Thread.threadRating & Post.rating), but in due course values again started to differ.
It occurs not to all records, but only with the some from them.
This is rather a not small like intranet portal (assets-9334, users-1183, groups-3642). Sometimes we add contest. CS has not more then 10 threads. Thread has no more then 10 posts.
I can send you url, login and password if you'll agree to look at example of that i was described.
So what we have here are three different "cached" ratings, and a master Post_rating table.
The Collaboration's rating is an average of all the Thread ratings, A Thread's rating is the sum of all the Post ratings, and a Post's rating is all the Post_rating.rating values for the asset.
I've posted a fix to some portions of the rating system that were not working correctly, which should fix the problem.
I'm attaching a script that will determine if you have any Threads that do not have the correct rate. It belongs in the WebGUI/sbin folder and requires a --configFile=<your webgui config> option.
If, after 7.4.3 is released and you've updated, this script still returns threads with wrong ratings, let me know.
Closing as resolved.
I've upgraded to 7.4.3 and started script:
[root@mail sbin]# ./checkRating.pl --configFile=name_of_configfile.conf
###------- a lot of lines -------
DONE: 380 errors out of 3322 threads[root@mail sbin]#
I tride the same on the some enother servers: I got less errors, but errors are.
Looks like I didn't submit my changes last time, but I did this time. Sorry for the inconvenience.
When 7.4.6 is released, please upgrade and run that script after a few days (or more) and let me know when errors start to occur.
Fixed in 7.4.6. Closing as resolved.
