thehaze
Member
Yep - top add on. Really useful
Wait until you see what he has up his sleeve for his next add-on! Glad you like this one though, shows how something so simple can be so useful.
Yep - top add on. Really useful
Wait until you see what he has up his sleeve for his next add-on! Glad you like this one though, shows how something so simple can be so useful.
Thanks!Yep - top add on. Really useful
I will try to update the addon with your 2nd suggestion. The first one, I don't know if I will be able to make it! :-/Couple of suggestions/questions.
1. Would it be possible to specify the timezone. For example our server is hosted in the US but we're based in Aus so the post counter ticks over at about 1pm, not midnight.
2. Not display until there's at least 1 post or registration?
Thanks for a great little addon too .
I will try this one too!Suggestion. It may be interesting to allow it to display your post per day ratio since registration. vBulletin used to have this at some point IIRC.
I will try to update the addon with your 2nd suggestion. The first one, I don't know if I will be able to make it! :-/
The addon will now list the number of posts/registration only when there's at least one.
Thanks to CFodder for this awesome Suggestion.
And sorry about the time it took to respond also CFodder. I think Mr Xpl0iter was a silly billy and lost his back-ups xD
It will work with 1.2 as expected.will this work with 1.2?
This is the query in this add-on for daily posts vs my query in the version I didTip to the developer, that query you run is very extensive on larger forums. If the post table has a lot of rows, it's going to take a while to run and possibly jam the database like @ineedhelp is talking about. I ran into a similar problem with my hashtag add on, it runs practically the same query (just for different results obviously). You should look into caching the numbers and extending the post datawriter and adding a deferred method after insert to update the stats for that person.
[EDIT] @Chris Deeming pointed out it's an entirely different query. My recommendation for caching and deferring still applies though.
mysql> SELECT COUNT( * ) AS posts, FROM_UNIXTIME( post_date, '%Y-%m-%d' ) AS DATE
-> FROM xf_post
-> WHERE FROM_UNIXTIME( post_date, '%Y-%m-%d' ) = CURDATE( );
+-------+------------+
| posts | DATE |
+-------+------------+
| 24 | 2013-10-07 |
+-------+------------+
1 row in set (0.13 sec)
mysql> SELECT COUNT(*)
-> FROM xf_post
-> WHERE post_date > UNIX_TIMESTAMP(CURDATE( ));
+----------+
| COUNT(*) |
+----------+
| 24 |
+----------+
1 row in set (0.00 sec)
We use essential cookies to make this site work, and optional cookies to enhance your experience.