weiser

Hi @johanneseva,

I’m sorry the plugin left you with that impression. Caching is a very important use case for Post Views Counter, and the free version is not meant to be useless with caching enabled.

The free plugin still includes cache-friendly counting options, including JavaScript and REST API counting modes. In many cached setups, switching from PHP counting to JavaScript or REST API is the recommended approach, because the page HTML can be cached while the view count is recorded separately.

Post Views Counter Pro adds more advanced performance and cache-related features for heavier or more complex setups, but basic cache-compatible view counting should not require Pro. If your site stopped counting views correctly with caching enabled, that sounds like something we should troubleshoot, not an intended limitation.

If you’re open to it, please share which caching plugin or server cache you were using, which counting mode was selected, and whether the issue was that views were not being counted at all or that the displayed number on the cached page was stale. Those are two different problems and the fix can be different.

I also understand your concern about freemium plugins in the WordPress ecosystem. We’ll review how we explain caching in the plugin and documentation so it’s clearer what works in Free and what Pro adds on top.

Thanks for the feedback, even though I’m sorry it came from a frustrating experience.

Hi,

Thanks for the detailed report and the Query Monitor screenshot – that really helped us track this down.

You were right that pvc_get_post_views() was the cause. On admin list screens it was running a separate database query for every row, which is what slowed things down.

We’ve reworked it so the views for all rows on a page now load in a single, faster query instead of one per row. These improvements will ship in the next releases of both Post Views Counter and Post Views Counter Pro.

Thanks!

Hi! Thanks for reporting this.

The error comes from the Most Viewed Posts widget trying to call pvc_most_viewed_posts() before the helper file is loaded. We’ve already fixed this for the next release: the widget now checks whether the helper is available, loads it if needed, and avoids the fatal error entirely.

It will be included in the upcoming release of PVC

Hi,

Thanks for sharing this. We enabled the new email summary by default because we wanted the feature to be immediately available and useful on existing sites, without requiring an extra setup step.

That said, we understand this can be too much for agencies and anyone managing a large number of websites, where even a weekly summary across many installs quickly becomes unwanted inbox volume and can affect email quotas.

You can disable it in Post Views Counter > Emails by turning off “Email Summary” and saving the settings. We’re also reviewing the upgrade behavior for existing sites so it better fits setups like yours.

Thanks again for pointing this out.

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.