i am a happy user of sideblog, but when upgrading to WP 2.1 noticed it created duplicates of every post. I went to download 3.6 but the version still say 3.5 and does the same thing as before. Am I doing something wrong?
This error gets thrown up with 3.6 sideblog on a 2.1 wordpress:
WordPress database error: [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY post_date DESC LIMIT 0, 20' at line 1]
SELECT SQL_CALC_FOUND_ROWS DISTINCT newnmk_posts.* FROM newnmk_posts LEFT JOIN newnmk_post2cat ON ( newnmk_posts.ID = newnmk_post2cat.post_id) WHERE 1=1 AND (post_type = ‘post’ AND (post_status = ‘publish’ OR post_status = ‘private’)) AND category_id NOT IN () ORDER BY post_date DESC LIMIT 0, 20
Thanks Katie, that worked. However, now I’m getting this on a post not in the main page:
WordPress database error: [Not unique table/alias: 'newnmk_post2cat']
SELECT SQL_CALC_FOUND_ROWS DISTINCT newnmk_posts.* FROM newnmk_posts LEFT JOIN newnmk_post2cat ON (newnmk_posts.ID = newnmk_post2cat.post_id) LEFT JOIN newnmk_categories ON (newnmk_post2cat.category_id = newnmk_categories.cat_ID) LEFT JOIN newnmk_post2cat ON ( newnmk_posts.ID = newnmk_post2cat.post_id) WHERE 1=1 AND (((post_title LIKE ‘%press%’) OR (post_content LIKE ‘%press%’))) AND category_id IN (0) AND (post_type = ‘post’ AND (post_status = ‘publish’ OR post_status = ‘future’ OR post_status = ‘draft’ OR post_status = ‘private’)) AND category_id NOT IN (19,1) GROUP BY newnmk_posts.ID ORDER BY post_date DESC LIMIT 0, 20
Hey Kate – Thanks for the update to Sideblog, it’s a great plugin. Have a question about a minor adjustment. I’d like to create some space between my sideblog entries, they’re too tight right now. What code do I need to tweak for that?
Something else to be aware of, or at least that I ran into over the course of the past week, is related to how WP 2.1 now handles/treats “static” pages.
I ran into major problems when I created a new page (after upgrading), as the new page wouldn’t work right with Sideblog (404 errors would get displayed).
I think that it was caused by my having ‘asides’ as the default category, and this was somehow getting attached to the new pages I created. Once I changed the default category to something other than my ‘asides’ category (which is what Sideblog is set to use/filter/display), things started working again.
There’s still something that needs to be tweaked in the plugin, but at least now there is (I think) a reasonable workaround…
it's going to be my 3rd straight year of being unable to join the main ilonggo festival. missing the rich and varied colors of the tribes. http://www.dinagyangsailoilo.com/.
my 2009 is so fucked up i can't get myself to finish writing a digest of the year. it was the worst year of my life yet. i hope to not see it again. want it zapped from my memory. not everything, though. i found new great friends. that alone was enough to get me through the hellish year.
Blown away by Pencil. Pencil is a wireframing and mockup tool implemented as a firefox add-on. It's not as sleek as other commercial products but this one gets the job done for web developers who needs to do the design themselves.
i am a happy user of sideblog, but when upgrading to WP 2.1 noticed it created duplicates of every post. I went to download 3.6 but the version still say 3.5 and does the same thing as before. Am I doing something wrong?
Also the “Subscribe to” plugin breaks when you try to make a comment here, same as on my site.
I’m so sorry. I was in a hurry to get it out. I’m in the process of launching another site and was fixing bugs left and right.
The download link is already fixed.
I disable subscribe to comments at the moment. Until I figure out which plugin of mine causes it.
I had an older version of this http://txfx.net/code/wordpress/subscribe-to-comments/ plugin, and it did the same thing yours was doing.
Hi KG – I still had some problems with the plugin here is a screenshot http://www.flickr.com/photos/prh/367028135/
Hi –
This error gets thrown up with 3.6 sideblog on a 2.1 wordpress:
WordPress database error: [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY post_date DESC LIMIT 0, 20' at line 1]
SELECT SQL_CALC_FOUND_ROWS DISTINCT newnmk_posts.* FROM newnmk_posts LEFT JOIN newnmk_post2cat ON ( newnmk_posts.ID = newnmk_post2cat.post_id) WHERE 1=1 AND (post_type = ‘post’ AND (post_status = ‘publish’ OR post_status = ‘private’)) AND category_id NOT IN () ORDER BY post_date DESC LIMIT 0, 20
Thank you much, I updated to WP 2.1 yesterday and SideBlog was one of the only plugins that didn’t work.
@Jim
It might mean you haven’t selected a category to be your aside category. Go to Admin->Options->Sideblog and select from the Select Categories column.
@wess
I upgraded my subscribe-to-comments and the problem went away.
Thanks Katie, that worked. However, now I’m getting this on a post not in the main page:
WordPress database error: [Not unique table/alias: 'newnmk_post2cat']
SELECT SQL_CALC_FOUND_ROWS DISTINCT newnmk_posts.* FROM newnmk_posts LEFT JOIN newnmk_post2cat ON (newnmk_posts.ID = newnmk_post2cat.post_id) LEFT JOIN newnmk_categories ON (newnmk_post2cat.category_id = newnmk_categories.cat_ID) LEFT JOIN newnmk_post2cat ON ( newnmk_posts.ID = newnmk_post2cat.post_id) WHERE 1=1 AND (((post_title LIKE ‘%press%’) OR (post_content LIKE ‘%press%’))) AND category_id IN (0) AND (post_type = ‘post’ AND (post_status = ‘publish’ OR post_status = ‘future’ OR post_status = ‘draft’ OR post_status = ‘private’)) AND category_id NOT IN (19,1) GROUP BY newnmk_posts.ID ORDER BY post_date DESC LIMIT 0, 20
Hey Kate – Thanks for the update to Sideblog, it’s a great plugin. Have a question about a minor adjustment. I’d like to create some space between my sideblog entries, they’re too tight right now. What code do I need to tweak for that?
Thanks again…
Hi there K!
I have exactly the same problem as Jim….
Thnx in advance for a reply…
Martin
Something else to be aware of, or at least that I ran into over the course of the past week, is related to how WP 2.1 now handles/treats “static” pages.
I ran into major problems when I created a new page (after upgrading), as the new page wouldn’t work right with Sideblog (404 errors would get displayed).
I think that it was caused by my having ‘asides’ as the default category, and this was somehow getting attached to the new pages I created. Once I changed the default category to something other than my ‘asides’ category (which is what Sideblog is set to use/filter/display), things started working again.
There’s still something that needs to be tweaked in the plugin, but at least now there is (I think) a reasonable workaround…
-ghp
Hey Kat! will u update your lovely plugin for the issues me and “Jim Munroe” and many others have???