site_reviews shortcode display, pagination issues with Elementor about site-reviews HOT 14 CLOSED

I think I found the culprit. There was a post_type check missing when listening for the transition_post_status hook.

You can either wait for the next update which will fix this, or rollback to v5.10.4

from site-reviews.

Same here, 5 pages empty with the "There are no reviews yet. Be the first one to write one." and the last with 7 reviews. It looks like when the plugin query the reviews, it gets reviews and some other type of post which can't be display

from site-reviews.

Have you tried running the Repair Review Relations tool?

from site-reviews.

Have you tried running the Repair Review Relations tool?

No, it says "Repair is unnecessary because your database tables use the InnoDB engine! ✨"

from site-reviews.

Did you previously at some point run the Optimise Your Database Tables tool to convert tables from MyISAM to InnoDB, or have your database tables always used InnoDB?

from site-reviews.

Did you previously at some point run the Optimise Your Database Tables tool to convert tables from MyISAM to InnoDB, or have your database tables always used InnoDB?

I never ran that tool. DB has always been InnoDB to my knowledge.

from site-reviews.

@LoganStrike It would help me if you would use the Contact Support section on the Help page to contact me directly and send the Console Log (if applicable) and the Site Reviews System Info.

@BenPam This sounds like a different issue. Please try running the Repair Review Relations tool, and then run the Optimise Your Database Tables tool.

from site-reviews.

@LoganStrike

The System Info you sent shows that you have seven 0-star reviews and four 5-star reviews (11 reviews total).

Is this still true?

The reason I ask is because I am trying to reproduce your problem on a local site. Site Reviews will display all 0-5 star reviews by default, but your site shows only the four 5-star reviews.

from site-reviews.

@LoganStrike Next, if you have access to PHPMyAdmin, TablePlus, or SequelPro (or any other MySQL client), would you be able to run the following SQL query and post a screenshot of the results?

SELECT
    r.ID,
    r.review_id,
    r.rating,
    r.is_approved,
    r.is_pinned, 
    p.post_author, 
    p.post_date, 
    p.post_title, 
    p.post_status, 
    p.post_type
FROM wp_glsr_ratings AS r 
INNER JOIN wp_posts AS p ON r.review_id = p.ID 
ORDER BY p.post_date desc

Note: If you are using a custom table prefix, make sure to update the table names in the query (e.g. wp_ is the default WordPress table prefix).

For example, here is a screenshot of what it looks like when I run that query:

from site-reviews.

@BenPam

1. Did you ever run the "Optimise Your Database Tables" tool previously?
2. Did you import the database (or any of the database tables) from a different WordPress website?

Here is something to try, please let me know if it works:

You will need to edit the following file in the plugin:

/wp-content/plugins/site-reviews/views/pages/tools/general/repair-review-relations.php

Replace all text in that file with the following code: https://pastebin.com/iYzAi3er

Once you have done that, you should be able to run the "Repair Review Relations" tool.

from site-reviews.

@pryley There are only 4 reviews total. When I search the posts table for site-review post type, there are only 4 rows returned there as well.

Here is the result pf the query:

from site-reviews.

@LoganStrike Please see question no.2 in the reply above and the proposed solution.

from site-reviews.

@LoganStrike Please see question no.2 in the reply above and the proposed solution.

This site wasn't imported from anywhere. It started as a default Flywheel WordPress installation, and the 4 reviews were added by a logged-in administrator submitting each review via the front end form using [email protected] as the email for all of them.

This site will be used to create other WordPress installations using the Flywheel Blueprint feature, which is basically a saved WordPress instance that can be easily duplicated to use as a starting point for other sites.

The proposed solution seems to have fixed the issue. Do you know what caused it to happen in the first place? Do you anticipate that I'd need to do this repair process on all sites moving forward?

from site-reviews.

If you would like to stay on the latest version and patch the problem yourself, please see: ca33320

from site-reviews.