Hi Vlad, Yes, this was a bug. With 1.9.1, new topics would be able to use your new comment_state_metrics definitions, but not existings ones.
I have just committed the fix into CVS. It was a minor change in Comment.pm, which I'll email to you. In general, with changing comment_state_metrics, there is no need to re-run install.pl, it should all just work automatically. Cheers, David Vysotsky, Vladimir wrote: > After using Codesrtiker for a while, I've decided to edit > codestriker.conf and add > one new entry in $comment_state_metrics. The UI picked the change right > away, but wouldn't let me change the value of the new new metric for any > comment. > The Topic Information page showed zeroes for all categories of the new > metric. > > Running install.pl didn't help. After some poking around in the the code I > was able to fix the problem by running the following statement in MySQL: > > insert into commentstatemetric > select distinct id, <new metric name>, <new metric default value> from > commentstatemetric; > > Is there a better way to update the set of comment state metrics once > the database has been initialized? (I'm using 1.9.1) Would it make sense > to put this logic in install.pl? > > -- Vlad _______________________________________________ Codestriker-user mailing list Codestriker-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/codestriker-user
