Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: basic blog stats plugin
Woo hoo!
If you wouldn’t mind repackaging it, that would be great.
My thought is, one of us could host it and link to it, for the next person who wants it. If you’d rather not host it, I’d be happy to.
Offline
#17 2005-06-07 01:22:27
- Andrew
- Plugin Author
- Registered: 2004-02-23
- Posts: 730
Re: basic blog stats plugin
I wouldn’t mind hosting it in its current state, and what I’ll likely do is take your feature suggestions and redistribute it. What’s it need?
Offline
Re: basic blog stats plugin
Oh, that would be so wonderful! :)
The top commenter portion doesn’t work in RC3.
And I think someone else mentioned a “word count” option but I don’t know if that would be outside the scope of this plugin.
And while I’m flinging wish lists at you (I have GOT to learn PHP soon!), I’d love to be able to restrict the count of entries and comments by section.
That’s all. :)
Offline
Re: basic blog stats plugin
Andrew: now that would be fantastic.
One of the (arguable) hacks I made on my version of it was to hyperlink to the commenter’s website in the top commenter’s list (remembering to enclose the thing in zem_prblock of course). The problem with this is that it picks up the first URL that your commenter using that name entered – which may have changed. Also, it does not distinguish between commenters with the same name but different email addresses and/or websites. Is there a way to key the commenters off something other than name (e.g., email address, or name + email address)?
Just some thoughts.
Alan Macdougall — http://halfpie.net/
Offline
#20 2005-06-07 02:04:52
- Andrew
- Plugin Author
- Registered: 2004-02-23
- Posts: 730
Re: basic blog stats plugin
Ok, a reconstructed version of this plugin is now available for download: gbl_blog_stats
This is strictly a resurrection version, so no new features except for fixing the broken top commenter function. I’ll release future versions with new features under a new name (most likely ajw_blog_stats) just so it doesn’t confuse people.
Offline
Re: basic blog stats plugin
That was quick! :) It works perfectly. Thank you!
Offline
Re: basic blog stats plugin
Thanks!
edit: I’m now using Andrew’s new comment count plugin to achieve the same effect.
Last edited by dubh (2005-06-12 23:28:33)
Alan Macdougall — http://halfpie.net/
Offline
Re: basic blog stats plugin
Sounds good andrew – how about a number of times an entry has been viewed? But allowing the tag or a tag of sorts to be placed within the entry itself – so something like:
this is my entry
monday 17 december 2008
viewed 3 million times
Offline
#24 2005-06-07 13:11:52
- davidm
- Member
- From: Paris, France
- Registered: 2004-04-27
- Posts: 719
Re: basic blog stats plugin
Thanks Andrew for this !
I had missed the original post of this simple yet missing plugin :D
.: Retired :.
Offline
#25 2005-06-11 01:46:40
- Andrew
- Plugin Author
- Registered: 2004-02-23
- Posts: 730
Re: basic blog stats plugin
So… at what point do I split a feature request out into its own separate plugin? Does it make sense to have like 10 sub-plugins contained by this one, or should I break a few of these feature requests into their own individual ones?
Offline
Re: basic blog stats plugin
it depends if these separate features could grow or be improved upon on their own, or whether ti’s better to have more functioanlity in one plugin with several variables.
Offline
#27 2005-06-11 18:00:27
- Andrew
- Plugin Author
- Registered: 2004-02-23
- Posts: 730
Re: basic blog stats plugin
In response to the word count request… you’re in luck – it already exists: klp_word_count
Offline
#28 2005-06-11 18:35:58
- Andrew
- Plugin Author
- Registered: 2004-02-23
- Posts: 730
Re: basic blog stats plugin
And in response to the pageviews request, I’ve managed to implelement the feature successfully (as a separate plugin). However, the main problem is storage of the pageview data itself. The “suggested” place to store plugin-related information is in txp_prefs, but that field is varchar(255), which basically means there isn’t a chance it’d be able to store serialized data for over a few dozen articles.
So then we’re back to external data storage in a flat file, which seems a bit kludgy but could be done (opinions?). It could also be done as a separate table, but if you’re going to take that route you might as well develop a full-featured statistics plugin, which I’m not really interested in developing.
I’ve added a few features to this particular package and am planning on re-releasing it under the name ajw_blog_stats (I spoke with Gordon and he’s too busy with studies to continue supporting it). I’ll probably be done testing/tweaking it sometime today or tomorrow.
Offline
Re: basic blog stats plugin
I wish I had something intelligent to input here, or a suggestion to make – data storage choices for this are over my head, I’m afraid.
I just felt the need to throw in a bit of cheerleading on this (hip hip hooray) so you’d know I’m still watching this intently to see what you put together on this. :)
Offline
Re: basic blog stats plugin
thanks for the link andrew:)
andrew, how about releasing the plugins indivudually, but with the option to have them work together in some form? I know Mary did something like that between upm image popper and upm quicktags.
If it’s going to limit how and what features are implemented in order to achieve a certain effect, then it might be best to break it down than have an all in one solution I suppose
Offline