weiser

Hi,

Thanks for reporting this. We traced the problem to incorrect bundled translation files in PVC Pro, which could trigger a fatal error in the Insights / Traffic Signals logic on some localized sites.

As a temporary workaround, if you cannot update right away, please remove or rename the PVC Pro translation files for your site language from wp-content/plugins/post-views-counter-pro/languages/ for example post-views-counter-pro-fr_FR.mo and post-views-counter-pro-fr_FR.po. This will make PVC Pro fall back to English and should prevent the fatal error.

We have fixed the bundled translation files in PVC Pro 1.7.12, so the recommended permanent solution is to update to that version. If the issue still appears after updating, send us the exact error message and your site language, and we will investigate further.

The tooltip is the browser showing the native title attribute from the gallery thumbnail link.

In Responsive Lightbox & Gallery, gallery image titles/captions can be generated from the media attachment fields: title, caption/legend, alt text, or description. In your case, the link title appears to be coming from the media caption/legend.

The numeric encoded format looks like coming from the PrettyPhoto lightbox. PrettyPhoto handling in RLG encodes caption text and copies it into the link’s title attribute because it uses that attribute for captions. The browser then displays that raw encoded value as a hover tooltip.

You do not need to edit hundreds of images one by one. Please try one of these options:

1. Go to Responsive Lightbox -> Settings -> General -> Galleries and change Gallery Image Caption to None.
2. If this is an RLG builder gallery with its own settings, edit the gallery and check the Lightbox tab. Set Image Caption to None, or set it to Global after changing the global setting.
3. If you want to keep captions in the lightbox but avoid this hover tooltip behavior, switch the selected lightbox script from PrettyPhoto to another script, for example GLightbox.

Hope this helps

Hi,

In PVC, both JavaScript mode and REST API mode use the same frontend bootstrap script, so switching from JS to REST API usually won’t avoid this kind of Autoptimize issue by itself. The important part is keeping PVC’s inline config and frontend script out of AO’s JS optimization flow so their execution order stays intact.

Please try adding these to Autoptimize → JS → Exclude scripts from Autoptimize:

post-views-counter/js/frontend.js,pvcArgsFrontend

After adding the exclusions, please:

1. Save AO settings
2. Clear Autoptimize cache
3. Clear any page/server/CDN cache
4. Retest on a single post page

If you still see odd counting after that, also check whether AO has “Minify excluded JS/CSS” enabled. In some setups, excluded files can still be minified, which is worth disabling for troubleshooting.

Hi,

We have checked if this can be achieved and decided to implement it for you – this will be possible in the upcoming release.

We are goinf to add a a new filter, rl_folders_term_drag_and_drop_enabled, which lets you disable dragging folders in the Media Folders tree while still allowing users to click folders normally.

For example, to allow folder drag and drop only for administrators:

add_filter( 'rl_folders_term_drag_and_drop_enabled', function( $enabled, $user_id ) {
    return user_can( $user_id, 'manage_options' );
}, 10, 2 );

You’ll be able to adjust this to use any capability or custom rule you prefer.

@davidpeake can you check your browser console? there should be some error message related to the Javascript or failed request

Vielen Dank für diese wunderbare Rückmeldung. Das ist tatsächlich eine der schönsten Bewertungen, die wir je für dieses Plugin erhalten haben. Für jemanden, der seit über 15 Jahren WordPress‑Tools entwickelt, ist es ein ganz besonderes Vergnügen, eine solche Geschichte zu lesen – von Installationen, Wechseln, Rückkehr und schließlich der erneuten Überzeugung nach so vielen Jahren.

Es freut mich sehr, dass das Plugin Ihnen wieder zuverlässig dient. Ihre Worte bedeuten uns wirklich viel. Vielen Dank dafür!

Hi all,

And thanks for your reports. Most probably we have already identified the issue and working on a fix.
An update should be published today/tomorrow.

Hi, thanks for reporting this.

We’ve looked into it and this does appear to be related to Yoast SEO, but not as a direct RLG code conflict. The most likely cause is a broader WordPress CSS-loading issue that Yoast can trigger on some sites. In RLG, the Basic Grid layout depends on its stylesheet loading correctly, so when that CSS is skipped or loaded incorrectly, the grid breaks while the lightbox still continues to work.

If possible, please test with the Load Combined Core Block Assets plugin (https://wordpress.org/plugins/load-combined-core-block-assets/), or ask your developer to temporarily disable separate core block asset loading. If that restores the grid, it would confirm this is the same issue. If you can also share your WordPress version, Yoast version, and theme name, that would help us compare setups.

You’re right to check with Yoast as well, since they’ve had similar reports from other plugins.