Using this with WP 3.4.1 multisite, it breaks the blog. Only half of the page loads (up to the point where the plugin should display its data).
When you are finished, will you be re-releasing 2.3?
I’m currently trying to fix the problem with the missing
day_no_timefield. Once I’m done with that and if no other bugs are reported I will release it as version 2.3.1.
Update and good news:
Just found out why the plugin failed to add the new
day_no_timetable field during the upgrade and I’m working on a quick fix now. Will inform you guys when the 2.3.1 update is available for download.
Sounds good Héctor!
Héctor, I had emptied the cache this morning, hoping that would resolve the issues. Is there anyway, whatsoever, to get my 30 day cache back?
I could, likely, ask my provider to restore my (sql) database to yesterday’s date. I think that would work, wouldn’t it?
Yes, then you could just restore your
wp_popularpostsdatacachetable to your database and get your info back.
To all: my sincere apologies for all the trouble this update caused you. Once everything gets fixed, I’m sure you guys will really enjoy all the new stuff WordPress Popular Posts has now!
“Yes, then you could just restore your wp_popularpostsdatacache table to your database and get your info back.” Wouldn’t the wp_popularpostsdatacache table be restored, automatically, once the database is restored to yesterday’s date?
“To all: my sincere apologies for all the trouble this update caused you.” That’s OK Héctor! Accidents happen from time to time. 🙂
Or, are you saying that I could just export out the wp_popularpostsdatacache table, once the database is restored, then import it into my current database, that I am now using?
Héctor, thanks for your efforts. I’ll reinstall your plug in with pleasure!
Yes, that’s true. However, I would advice to restore just the
wp_popularpostsdatacachetable. That way, you would not affect other areas of your blog eg. comments received in the last hours since the update, pingbacks and other activities registered in your database by WordPress or other plugins you may have as well.
And thank you for your words. I do know that shit happens, I just hate it when it does hehe.
Alright, the fix is ready and I would appreciate it if anyone is willing to give it a try. Please download version 2.3.1 here. If the feedback is positive, I will push the update into the WordPress Plugins directory.
“However, I would advice to restore just the wp_popularpostsdatacache table. That way, you would not affect other areas of your blog eg. comments received in the last hours since the update, pingbacks and other activities registered in your database by WordPress or other plugins you may have as well.”
Yes, that makes perfect sense. Thank you!
I will try downloading the new version right now.
Now, to exclude categories, in the new version, we have to use dashes, correct? For example: -1,-68,-114,-121,-148,-169,-181,-202,-223,-225,-226,-227
Yes, that is correct. Just like WordPress does natively, a minus sign in front of the Category ID will exclude it from the listing.
Keep in mind, though, that if a post belongs to different categories it will still be shown in the list unless you also exclude the other categories it belongs to. Hope that makes sense.
I had to deactivate and delete the plugin as well. It gave me errors on every single post. Please let us know when this glitch has been resolved.
This is the error I received:
WordPress database error: [Unknown column ‘day_no_time’ in ‘field list’]
INSERT INTO wp_popularpostsdatacache (id, day, day_no_time) VALUES (9451, ‘2012-09-01 17:46:20’, ‘2012-09-01’) ON DUPLICATE KEY UPDATE pageviews = pageviews + 1, day = ‘2012-09-01 17:46:20’, day_no_time = ‘2012-09-01’;
- The topic ‘[Plugin: WordPress Popular Posts] Version Version 2.3.0 breaks the blog’ is closed to new replies.