ws24

link to image/screenshot.
I just repaired the problem for the website by translating the Polylang string translation settings again, so it is no longer visible in the “live” result, sorry.
And yes, I marked the topic as resolved.

• This reply was modified 6 months, 2 weeks ago by ws24.

Hi, thanks, I know that ?? and that’s what I had as a result before.

But after the update I remarked that there were only 2 star images left… so just having selected %s Star / %s Stars in the section ‘Strings’ (before) in your plugin made that there were no longer 5 but only 2 star images visible above the form…

Tried to sort this out myself, am using your plugin together with Polylang multilanguage plugin. The only 2 stars where there because they were in your section ‘Strings’ (necessary to be able to translate them in the Polylang settings), it concerns the string: %s Star / %s Stars. This causes that there will only be 2 stars visible.
I tried to solve this by adding the string ‘Star’ again, but this ended in a total mess, nearly all my Polylang translations for the Reviews plugin strings were reset to the word ‘Star’….

Hi, thank you for your fast answer and investigation.

I’m indeed using your plugin with a Gallery plugin (Modula) and their built-in lightbox. Because I also have some singular images elsewhere on the website that I want to open in a lightbox I use your plugin too (the Modula lightbox only works with their own galleries). Modula recommends to use/install an extra, other Fancybox plugin if you have other singular images.
So I think that you are right and that this was causing the problem. In the Modula gallery settings I have now chosen the setting ‘direct link to lightbox’ (instead of their own lightbox). Now all the images on the website use your lightbox and the problem seems to be solved.
Thanks again.

• This reply was modified 7 months ago by ws24.

Hi, I had the same problem yesterday, selected category (Query build) and selected fields (Field selection) were not saved. There were no error messages in Inspector.
The latest version/update fixed the problem.

Just add !important to the css to overrule, that will help:
.main-container:after{opacity:0!important;}

Had the same issue, I just added !important to the css, that helps:
.main-container:after{opacity:0!important;}

But it would be more clear if this opacity default setting is just an option to turn on/off in the Maintenance configuration settings.

Thanks WebFactory, this plugin works good.

Thank you for responding so quickly, it seems indeed to be solved with the update.

Did that ?? (by mail)

Hi Antonio,

Installed the update but unfortunately the link to https://fonts.gstatic.com is still there (I cleared the cache).
Thanks anyhow!

Hi Antonio,

Unfortunately I can’t give the url (clients site) unless if this is possible via a PM.
The theme is: GeneratePress
The plugins are:
– Content views
– Default featured image
– Foogallery
– Generateblocks
– GP (generatepress) Premium
– Replace Google Fonts with Bunny Fonts
– SEOPress
– Simple CSS
– SiteGround Optimizer
– SiteGround Security
– Tablepress
– WP Featherlight
– WPCode – Insert Headers, Footers, and Code Snippets

Thanks.

Hi and thank you for your answer.
I refer to your info/instructions in the plugin (Site Reviews -> Settings -> Strings) about field labels, there you mention:
<quote>Here you can customise any English text of the plugin that is shown on the frontend of your website, including the field labels and placeholders of the review form. If you are using the Polylang plugin, any custom text you enter here will be translatable on the Polylang “Strings translations” page.</quote>

So I have set it up in this way: I customized some texts and then translated them in Polylang string translations, it worked perfectly, until I updated…
Now only the strings of Site Reviews -> Settings -> strings are displayed for all languages.

• This reply was modified 2 years, 2 months ago by ws24.

This plugin can be used with Polylang, no problem.
The general problem with Polylang is that it doesn’t work with the new ‘widgets block editor’ in WP. This can be solved by installing the ‘Classic Widgets’ plugin, after this you can assign indiv. widgets to indiv. languages again. This works fine, also for this plugin.

Yes indeed, updating and then re-activating helped, the errors are gone.
Thank you Benjamin.

• This reply was modified 2 years, 10 months ago by ws24.

Thanks, I followed your instructions above and it works fine now.