Home Page › Forums › WP Related Items › WRI not working in my published Site but working in my local PC
- This topic has 1 reply, 2 voices, and was last updated 10 years, 7 months ago by
WebshopLogic.
-
AuthorPosts
-
Participant
Hi there,
I use WP Related Items in my site. I worked on my site while running on a local PC using XAMPP for Windows.
As soon as I uploaded and published my website online (hosted by Siteground) I noticed my related posts don’t appear at all, altough in my local PC they are correctly apperaing. I also noticed a really big (11Mb!) PHP error log on my root folder, containing hundreds of errors! I guess they can be related to WP Related Items.
Here are just a few of errors I read on my php_errorlog file:
[12-Jun-2014 14:08:54 UTC] WordPress database error The used table type doesn't support FULLTEXT indexes for query (SELECT 2396 as reference_ID, ID, ROUND(0 + (MATCH (post_content) AGAINST ('')) * 1 + (MATCH (post_title) AGAINST ('guitar moonshine')) * 1 + (1 = 0) * 1 + (1 = 0) * 1,1) as score from wp_posts left join wp_term_relationships as terms on ( terms.object_id = wp_posts.ID ) where post_status in ( 'publish', 'static' ) and ID != '2396' and post_password ='' and post_type = 'product' group by ID having score >= 2.00 and ID != 0 and bit_or(terms.term_taxonomy_id in (0)) = 0 order by score desc limit 3) made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/plugins/woocommerce/templates/single-product.php'), wc_get_template_part, load_template, require('/plugins/woocommerce/templates/content-single-product.php'), do_action('woocommerce_after_single_product_summary'), call_user_func_array, woocommerce_output_product_data_tabs, wc_get_template, include('/plugins/woocommerce/templates/single-product/tabs/tabs.php'), call_user_func, woocommerce_tab_manager_tab_content, WC_Tab_Manager->get_product_tab, apply_filters('the_content'), call_user_func_array, WRI->the_wri_content_page_bottom, WRI->wri_display_related, yarpp_related, YARPP->display_related, YARPP_Cache_Bypass->begin_yarpp_time [12-Jun-2014 14:08:54 UTC] WordPress database error The used table type doesn't support FULLTEXT indexes for query (SELECT 2396 as reference_ID, ID, ROUND(0 + (MATCH (post_content) AGAINST ('')) * 1 + (MATCH (post_title) AGAINST ('guitar moonshine')) * 1 + (1 = 0) * 1 + (1 = 0) * 1,1) as score from wp_posts left join wp_term_relationships as terms on ( terms.object_id = wp_posts.ID ) where post_status in ( 'publish', 'static' ) and ID != '2396' and post_password ='' and post_type = 'product' group by ID having score >= 2.00 and ID != 0 and bit_or(terms.term_taxonomy_id in (0)) = 0 order by score desc limit 3) made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/plugins/woocommerce/templates/single-product.php'), wc_get_template_part, load_template, require('/plugins/woocommerce/templates/content-single-product.php'), do_action('woocommerce_after_single_product_summary'), call_user_func_array, woocommerce_output_product_data_tabs, wc_get_template, include('/plugins/woocommerce/templates/single-product/tabs/tabs.php'), call_user_func, woocommerce_tab_manager_tab_content, WC_Tab_Manager->get_product_tab, apply_filters('the_content'), call_user_func_array, WRI->the_wri_content_page_bottom, WRI->wri_display_related, yarpp_related, YARPP->display_related, YARPP_Cache_Bypass->begin_yarpp_time
Any ideas on how to solve this problem?
Thanks
-FilippoKeymasterHi Filippo!
YARPP plugin (it is the background of WP Related Post plugin) uses full text search.
According to YARPP support forum, the problem can be solved if you use MySQL database server and MyISAM table type for the post table. If you use InnoDB table type, “you can change your wp_posts table to MyISAM and you’ll be all set.”
http://wordpress.org/support/topic/the-used-table-type-doesnt-support-fulltext-indexesHere is a post, how can you do this:
http://www.plugish.com/2014/03/wordpress-doesnt-support-fulltext-indexes/
“This solution is made specifically for the InnoDB engine, if you’re getting this issue and you are trying to install a plugin, then the plugin may be built for the MyISAM engine, which means you will want to switch it. to do this, just do an ALTER TABLE query.ALTER TABLE wp_posts ENGINE = MYISAM;
Then re-activate that plugin/theme and you’re good to go.”We hope this will solve your problem.
You may see YARPP forums about further information.
Best Regards,
Peter Rath
WebshopLogic -
AuthorPosts
- You must be logged in to reply to this topic.