Daniel K.

Hi @agentnew,

Thank you for your topic.

To investigate this question, please send:

1. Direct link to your website page where we can see and reproduce the issue;

2. Debug information from the page in wp-admin: Google Reviews / Settings / Advance tab. You need to click the ‘Copy Debug Information‘ button, paste copied to this reply and send it to us.

For the debug info, please use ‘Pastebin’ service.

Thansk!

Hi @mon777herdl,

Thank you for your topic.

Are you sure that you’re using the latest version 6.9.4.4? Could you please send a screenshot with this error?

Thanks!

Hi @greyturtle,

Thank you for your topic.

I found two issue.

1. Current reviews parent container does not have width and since the Slider is a flex based layout it uses whole available width. Please look at the screenshot below, the parent container prose-lg without width and it’s a problem:

Once added a w-full class (width: 100%) it instantly fixed the issue:

2. The second issue, it seems you’re using wrong row for the shortcode for the Slider in your page builder. JavaScript is showing like a plain text. Please make sure that you’re using a shortcode element or HTML especially to show it correctly.

Please let us know how it goes.

Thanks!

Hi @fesarlis,

Thank you for your topic!

Are you sure that you’re using the latest version 6.9.4.4?

If so, please send a link to the page where we can reproduce it.

Thanks!

Hi,

Thank you for your question.

At the initial connection stage, the plugin uses two Google Places APIs (the legacy Places API and the new Places API).

1. The legacy Places API returns the 5 most recent reviews.
2. The new Places API returns the 5 most relevant (popular) reviews.

This is why, during the first import, you may see up to 10 reviews in total.

However, sometimes Google includes some of the same reviews in both groups (for example, a review can be both recent and popular). In such cases, duplicates are automatically filtered out, and the total number of imported reviews may be lower – typically 7–9 reviews instead of 10.

After installation, the plugin user can create and add their own Google API key in the plugin settings. This is free of charge, but Google requires adding a payment method in Google Cloud Console for verification purposes.

Once a personal API key is added:

1. The plugin can request data from Google daily.
2. It can retrieve more new reviews over time. The number of reviews is not limited by the plugin – it depends only on how many reviews Google provides via the API.

If you need any further clarification, I’ll be happy to help.

Thanks!

Hi @markmck,

Thank you for your topic!

Could you please send debug information from the page in wp-admin: Google Reviews / Settings / Advance tab. You need to click the ‘Copy Debug Information‘ button, paste copied to this reply and send it to us.

Please use ‘Pastebin’ for the debug info.

If you already added this, please let us know the password.

Thanks!

Hi @bway2larj,

Please update the plugin to the version 6.9.4.1. We made a micro-patch to fix this.

Thanks!

Hi @kittmedia,

Thank you for taking the time to write this – you are absolutely right, and we fully agree with your point.

HTML classes are effectively a public API, and changing or removing them is a breaking change. From a SemVer perspective, this should not happen as part of a regular feature update, and your frustration in this situation is completely understandable – especially when the widget is used across hundreds of websites.

In our case, the 6.9.4 update was influenced by some long-standing technical constraints in the plugin that date back to around 2016. Unfortunately, those legacy decisions made it impossible to fully preserve the original markup and class structure in its entirety while moving forward with the new design structure.

That said, we were very careful not to remove everything:

1. The core and main classes were kept intact.
2. Flex containers were added on top of existing structures, not replaced wholesale.
3. Only a small number of very old classes were removed — specifically:
   • the global hard reset class wpac, and
   • a few legacy layout helpers (wp-google-left / wp-google-right) that predated proper flexbox support and were effectively emulating it.

We also want to highlight that the visual changes you noticed are very likely related to the removal of the global hard CSS reset (wpac). This reset forced the widget to look identical on all sites, but over time it became a major source of conflicts and layout issues, which ultimately made its removal necessary.

None of this is meant as an excuse – you are still absolutely correct. We take full responsibility for the impact this had, and we completely agree that this kind of change should be handled with extreme caution.

Going forward, we will make a strong effort to avoid removing or changing public classes and to treat the markup much more strictly as a stable API, precisely to prevent situations like this in future releases.

Thank you again for the clear and constructive feedback – it’s genuinely appreciated!