Version: 2.0.0, by hambil
Developer Last Online: Apr 2013
Category: Statistics Modifications -
Version: 3.6.5
Rating:
Released: 03-23-2007
Last Update: 04-10-2007
Installs: 133
DB Changes Uses Plugins Template Edits
Additional Files Is in Beta Stage
No support by the author.
Note: This product is now being supported at www.catnine.net
Keywords: Statistics, New members, joins, trends, Forum Home, threads, posts
ATTENTION:
If you download the latest version go into your usergroups and set the 'can view trends' permission. SAVE the usergroup even if you haven't changed the setting or things may not work. There is an odd permissions bug I haven't figured out yet.
Also note that overwrite will not work. Please uninstall the previous version before installing the new one.
Description:
Enhances the "YourBBS" Statistics box on the forum home to show trends of posts, threads and new users vs. the overall history of the board. Also allows you to display more than one "newest member".
Version 2.0.0:
Calculations exposed and modifiable in admincp.
Added ability to delay updates of stats to every x minutes in admincp.
Added a style setting for positive and negative trends.
Added custom hooks for all aspects of vbTrends, and moved code into said hooks.
Changed template to still show total threads when trend is negative and 'positive trends only' is enabled.
Usergroup permission to view trends.
Note: You cannot cause an error by messing up the calculations in the admincp. If the calculation you provide contains errors the stat in question will show as N/A.
This is a major rewrite, so I've set the hack to beta for now.
Version 1.2.6:
Made some minor tweaks for cleaner code
Made change to build datastore call to force serialization
You can just overwrite the product.xml if you are upgrading. Remember vbTrends has an option in the admincp to reset the counters. To see any changes/fixes you'll want to run that, or you'll end up having to wait for a new day before the changes will take affect.
Version 1.2.5:
fixed minor bug in auto-replace that was causing it not to work on some boards
It's all fixed. It appears the old template didn't get updated when you installed the new version. I have no idea why that would happen. I think perhaps it might be when people do an overwrite instead of an uninstall and reinstall, but I'm not sure.
I highly recommend anyone installing 2.0.0 do an uninstall and reinstall though.
It means that so far this month you've had four new threads. And compared to the last 2 months, that's 117% more than you usually have by this time of the month.
then there's something wrong in the way this mod is tracking new information because this is what I see in the admin panel and we're 11 days into the month already
New Threads Today 6
Is it 4 new threads from the date/time of install ?
then there's something wrong in the way this mod is tracking new threads because this is what I see in the admin panel and we're 11 days into the month already
New Threads Today 6
Is it 4 new threads from the date/time of install ?
No, it shouldn't be. Let me double check the code and get back to you.
Well, here is the query used, I don't see anything wrong with it off hand...
Code:
SELECT count(*) AS 'ThreadsThisMonth'
FROM " . TABLE_PREFIX . "thread
WHERE YEAR(FROM_UNIXTIME(dateline)) = YEAR(NOW())
AND MONTH(FROM_UNIXTIME(dateline)) = MONTH(NOW())
Ahha! I found an error in the template. I've uploaded the new zip. Uninstall/Reinstall to make sure the template change gets picked up and you should be good to go.
These stats are not accurate. I'm getting a 93% increase in threads, a 95% increase in posts and a 1% increase in members. This is on a 355,000-post board. The 90 numbers are waaay too high. Activity is steady. *disabled*
BTW I assume encryption's stats are incorrect, as well.
These stats are not accurate. I'm getting a 93% increase in threads, a 95% increase in posts and a 1% increase in members. This is on a 355,000-post board. The 90 numbers are waaay too high. Activity is steady. *disabled*
BTW I assume encryption's stats are incorrect, as well.
Very simple fix. Change the calculations used in the admincp settings as follows:
Before:
Code:
round(($current / $avg) * 100)
After:
Code:
round(($current / $avg) * 100) - 100
It's the difference between considering 100% to mean 'dead on track' or '0%' to mean 'dead on track'. That's why I've exposed the calculations in this release. The minute I change it to be one way, someone will want it the other way.