ebiven
Forum Replies Created
-
Forum: Plugins
In reply to: [Recently Popular] [Plugin: Recently Popular] Hundreds of select statementsIt will do one select statement with every page visit. I’ve said it before and I’ll say it again: this plugin isn’t for highly traffic’d blogs.
Forum: Plugins
In reply to: [Recently Popular] [Plugin: Recently Popular] WP-GeniusIsn’t this more of a question for the WP-Genius folks? I’m not sure what challenges you’re having getting it installed that would be specific to the plugin.
Jack, can you check your web server logs for errors?
I’m using it in several 3.3.1 sites with no problem. Is there anything in your web server logs?
Forum: Plugins
In reply to: [Recently Popular] [Plugin: Recently Popular] Love it , small usage issueThe plugin is MU compatible but segments posts by blog. It doesn’t apply counts network wide, across blogs like you’re looking for. I’ve never considered how that would work but it may be possible.
Are you trying to do this using the widget or calling the function directly? If you’re calling the function directly, what is the call you’re using?
Just found the same bug.
Thanks for the write-up on modifying it.
Copy the new sunrise.php file from wp-content/plugins/wordpress-mu-domain-mapping/sunrise.php to wp-content/sunrise.php and you’ll be fine.
Forum: Plugins
In reply to: [Plugin: Recently Popular] Why adding db row prt each page view ?Some people may want the hourly data. Even then you could aggregate by timestamp if you wanted to aggregate. I didn’t want to aggregate. I wanted the most accurate representation possible. I even warn people with very busy blogs to not use this plugin.
The plugin now allows you to purge data from the table through a settings page in the admin. Additionally, the table is indexed and the plugin first selects out only the rows that match the time criteria, making it very efficient as long as you use a reasonable timespan. Don’t do “most popular for the last year” and you’ll be fine in almost all cases.
Finally, the plugin is licensed under the FreeBSD license precisely because I knew that it wouldn’t do what everyone wanted. It can’t be all things to all people. The FreeBSD license is as liberal as they come. Take it, make a fork, and make any changes you want. That’s part of the beauty of open source.
Forum: Plugins
In reply to: [Plugin: Recently Popular] Upgrade to 0.6.2 – visit count got resetThat one bothers me, but I don’t think there’s anything I can do about it. Some number of downloads have a random bad bit one file or another. I tried retagging a new version, but the same thing is happening. Since I don’t have control over the zip file or the download servers there isn’t much else I can do.
Forum: Plugins
In reply to: [Plugin: Recently Popular] Upgrade to 0.6.2 – visit count got resetWhich version of the plugin are you trying to install and what version of WordPress are you using? Are you seeing errors in your Apache logs? What are they?
“It no worky” isn’t going to help.
Forum: Plugins
In reply to: [Plugin: Recently Popular] Upgrade to 0.6.2 – visit count got resetThere’s something going on with either WP’s SQL delta function or procedure on when uninstall is called that is different than previous versions, causing it to drop data. That said, this isn’t a stats package, so it isn’t an issue I care to correct. If you’re trying to display info from the beginning of time there are other plugins FAR better suited to that.
Forum: Plugins
In reply to: [Plugin: Recently Popular] ErrorAs the author I’d like to know, too. There have only been a couple of instances where we couldn’t get it to work, and only a handful where it didn’t work right out of the box.
I’ve used it successfully in every release of 2.8.
Forum: Plugins
In reply to: Popular Articles/Recent Articles WidgetYou might check out Recently Popular.
Forum: Plugins
In reply to: Need post popularity plugin that works with WP-Cachehttp://eric.biven.us/2008/12/03/recently-popular-wordpress-plugin/
This will correctly count posts even when you are using WP-Cache. It allows you to specify a time period to count for, if you set the time limit to 99 years old (or something similarly outrageous) then you will effectively get all post for all time. It was written to be very database friendly and uses joins instead of multiple round trips and has proper indexes on the one table it adds.