WordPress.org

Ready to get started?Download WordPress

Forums

SiteTree
[resolved] Bugs? (2 posts)

  1. rrhobbs
    Member
    Posted 1 year ago #

    PHP error: [07-Dec-2012 23:56:24 UTC] WordPress database error Column 'ID' in where clause is ambiguous for query SELECT p.ID, p.post_author, p.post_date, p.post_content, p.post_title, p.post_status, p.post_name, p.post_type, p.post_author, u.user_nicename AS author_nicename, u.display_name AS author_name FROM wp_posts AS p INNER JOIN wp_users AS u ON p.post_author = u.ID WHERE p.post_type = 'post' AND p.post_status = 'publish' AND p.post_password = '' AND ID NOT IN (2542,1735) ORDER BY u.display_name, p.comment_count DESC made by do_action_ref_array, call_user_func_array, SiteTree->rebuild_sitemap, SiteTreeFactory->get_sitemap, SiteTreeHTML5Factory->posts

    I am using (with some apprehension) WordPress-SEO (Yoast) to noindex and redirect some "dead wood" posts and anything like that I will usually tell SiteTree to exclude the originating post from the sitemaps.

    I also have installed (but will soon be removing) Ultimate Noindex Nofollow Tool II - it no longer seems to work in WP3.42 :( I need a way to noindex a considerable number of "dead wood" posts as I may have requested as a SiteTree Feature.

    Also I encountered a blank SiteTree xml sitemap today; I deactivated / reactivated SiteTree and cleared my cache (WP-SuperCache) and the xml sitemap came back. Please do note I had also recently cleared my transient options at that time.

    Should the xml sitemap be excluded from caching, and if so what is the proper string to use?

    Thx

    http://wordpress.org/extend/plugins/sitetree/

  2. Luigi
    Member
    Plugin Author

    Posted 1 year ago #

    Hi,

    first I would ask: how do you cleared the transient cache?

    Without going into details (I'll write some documentation once published SiteTree 1.4), you shouldn't need to clear the (super)cached version of the Google sitemap because it actually shouldn't exist. The caching of the sitemap is handle by SiteTree.

    I think the problem arose from the flushing of the transient cache. Anyway, the behaviour you describe is unusual. Perhaps the transients were not cleared properly.

    Finally, I confirm that that php error is caused by a bug: there is a typo in the where clause. It will be fixed with the next update. However, it isn't something critical.

    You can continue to use SiteTree with WordPress SEO on the side, there shouldn't be conflicts.

    Thank you for the report!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.