please consider to use the 1.3 RC1 release, that solves all reported bugs, and add’s some nice config options. The only think I espect to add to the 1.3 final release is a button to clean uninstall database entries of the plugin. Enjoy!

I will release a new version on next days that solves this bug, and some other changes…

By now you can change the line 154 from
`t4`.`term_taxonomy_id` AS `cat_ID`
to
`t4`.`term_id` AS `cat_ID`

(note this only works with your current configuration)

The two id’s are different only when we have deleted some old category and then added a new one, so this bug was not detected before by myself…

I have it set up here. http://usws.isgreat.org/popular

Thank you so much once again! 🙂

I’m sorry but I cannot figure out what can be happening… I don’t think that can be a compatibility problem with other plugins but you can do the tedious job (I know) of disable / enable plugins to test it. You should debug the plugin in your envoirment by yourself.

Another thing that you can try if your template(s) are calling the “wp_footer” is change the tracker to this wp hook. Just change the line 299 from: add_action (‘shutdown’, ‘tpbc_tracker’); to add_action (‘wp_footer’, ‘tpbc_tracker’); and disable/enable the plugin to install the function into this hook. Or you can also can play with priorities adding a third argument to the add_action, p.e. add_action(‘shutdown’, ‘tpbc_tracker’, 1); or add_action(‘shutdown’, ‘tpbc_tracker’, 1); (Note that plugin must be disabled/enabled each time you change this function. Priorities goes from 1 (first) to 10 (last)).

Good luck !

I’m happy to have helped you !
You are right, there is no limit in table size at this moment. I note for future release… (I also have other improvements in mind, but any date…)

And, thanks to you for use it 😉