We have been doing some tuning work on the 80,000+ product Sparkle Gear WP e-Commerce store and wanted to share one experience with the WordPress SEO Plugin by Yoast.
Unless you are a SEO expert, Yoast’s WordPress Plugin is a a tool that will save you alot of work, and keep much the SEO process understandable and accessible to mere mortals. It’s a great addition for any WordPress site, and especially useful for WPEC that create lots of posts (products are posts) and have lost of taxonomies (variations and categories are taxonomies). IMHO. the dynamic sitemap generation feature of the WorpPress SEO plugin alone makes it a must have.
However, there are some details about how WPEC is implemented that need to be addressed when you install the SEO plugin.First item, WPEC stores products as posts. WPEC stores
variations of products as child posts of product posts. These child posts are used to hold information about an individual product variation. Details like the variation image, price, stock. etc. The important detail to note is that these child posts are not directly accessible to the outside world. In WP speak, the permalink for these posts will give you a 404!
if anyone is reading this, it is outdated as of 1/30/2015.
after some reading i think i figured something out, the new coding you said to replace has changed it is now:
$query = $wpdb->prepare( “SELECT COUNT(ID) FROM $wpdb->posts {$join_filter} WHERE post_status IN (‘publish’,’inherit’) AND post_password = ” AND post_author != 0 AND post_date != ‘0000-00-00 00:00:00’ AND post_type = %s ” . $where_filter, $post_type );
i read a post where i person said he fixed it but didnt give any instructions, just said the plugin was set to inherit posts.
so i took the above code and removed: ,’inherit’
and it seems to generate the proper amount of product pages!
if someone could revisit this post it would be great, i am not far enough into testing to say for sure, but at least anyone reading this will know its outdated and maybe have the fix
thanks man, i never would have figured out that other guys comment without you pointing out the general code that needed changed.
sorry my previous fix doesnt work. still looking for a new fix for new code.
Nice work and thanks for sharing!