Filter (Sort order) by Highes rated (review)

Hi there,
currently we are having an issues with this setting. In general it works fine BUT:
If a review is set for a post, the post appears in the blog which is configured to show the highest rated. But if you remove the review the specific post won’t disappear within this block. It is still there but not showing any stars (well this works as intended).
We also tried not to only set the review setting to “no” but also delete every single “feature name” and the description. Looking into the db entry for that post, all information about the “review” seem to be removed correctly. Anyhow, the post – as already said – still appears in every block using this filter method.

Are there any additional tables which are holding these review information or how could we solve this issue?

By the way, adding the review information automatically by writing them into the database works fine and all information about the review are correctly shown on the post itself. In a Block using the filter method highes rated these post first show up after saving the post through the backend without making any changes. This behavior also makes me belief that additional review information are stored somewhere else in the database?!

Ah, before you ask, there is no caching plugin oder CDN aktive.

Thanks in advance and sorry for my english…
Best regards.

• This topic was modified 10 years by generics.
• This topic was modified 10 years by generics.

After further investigation of that issue we might have found the “bug”

Looking at td_review.php you find the following code snippet:


static function save_post_hook($post_id) {
//$td_review = get_post_meta($post_id, 'td_review', true);
$td_review = get_post_meta($post_id, 'td_post_theme_settings', true);
if (self::has_review($td_review)) {
update_post_meta($post_id, self::$td_review_key, self::calculate_total_key_value($td_review));
}


Just maybe there is an else snippet missing to remove the td_review_key in case someone “disables” the review for a post?!
Anyhow, for our problem we manually removed the entry from the database to synchronize the backend view and the db.

Cheers!