While this module is a definite improvement over the "stock" most read module it has one glaring weakness.

If you set to the last N days, where N is say 60. Any articles published 61+ days ago are excluded EVEN if they are STILL the most read articles.

A really old article could still be read the most because it receives a lot of organic traffic from search engines and other sites.

To ignore this fact is not good.

The problem is the database would have to store each contentID number of hits by day for the last N days (60 in this case) and then do a query to retrieve the top X articles that have the most hits over the last N days.

More complicated to write and I can understand why the author did not do it.

Maybe a nice hack on this is where I will head to next.

This blog component is so far removed from being usable. I will list a few problems.

1) If you change the backend URI - the component is no longer accessible.
2) The front end blogging is nigh impossible, a few 1/2 baked hacks with sql errors present is possible
3) The title, meta description, meta keyword, etc is NOT updated with this component.
4) It's user management on a site with thousands of users is nearly impossible to navigate through

I could go on, but I will conclude with find another blog component, trust me.

So I ran into the "too many pages" problem with artio-sef and fireboard and decided to add this plugin.

URL's work fine, very happy with that but the notification emails have the wrong URL now, which worked BEFORE the plugin was put in.

Any ideas on a fix for this I hope soon? I posted to the owners forum but i saw most posts about bugs/issues have no replies even, not encouraging support.