Title: weiser's Replies | WordPress.org --- # weiser [ ](https://wordpress.org/support/users/weiser/) * [Profile](https://wordpress.org/support/users/weiser/) * [Topics Started](https://wordpress.org/support/users/weiser/topics/) * [Replies Created](https://wordpress.org/support/users/weiser/replies/) * [Reviews Written](https://wordpress.org/support/users/weiser/reviews/) * [Topics Replied To](https://wordpress.org/support/users/weiser/replied-to/) * [Engagements](https://wordpress.org/support/users/weiser/engagements/) * [Favorites](https://wordpress.org/support/users/weiser/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 50 total) 1 [2](https://wordpress.org/support/users/weiser/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/weiser/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/weiser/replies/page/4/?output_format=md) [→](https://wordpress.org/support/users/weiser/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Post Views Counter] Message d’erreur : Uncaught ArgumentCountError](https://wordpress.org/support/topic/message-derreur-uncaught-argumentcounterror/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 days, 13 hours ago](https://wordpress.org/support/topic/message-derreur-uncaught-argumentcounterror/#post-18914481) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Post Views Counter] WordPress postmeta table](https://wordpress.org/support/topic/wordpress-postmeta-table/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [1 week, 2 days ago](https://wordpress.org/support/topic/wordpress-postmeta-table/#post-18908445) * There is no such option currently in PVC but we have done some research already and could incorporate that in PVC Pro. Just drops us a line via contact form at [https://postviewscounter.com/support/](https://postviewscounter.com/support/) and we’ll give you some details. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Responsive Lightbox & Gallery] Title appears with hexa HTML codes when hovering thumbnail](https://wordpress.org/support/topic/title-appears-with-hexa-html-codes-when-hovering-thumbnail/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 weeks ago](https://wordpress.org/support/topic/title-appears-with-hexa-html-codes-when-hovering-thumbnail/#post-18903488) * 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 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Post Views Counter] WordPress postmeta table](https://wordpress.org/support/topic/wordpress-postmeta-table/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 weeks, 2 days ago](https://wordpress.org/support/topic/wordpress-postmeta-table/#post-18901661) * No. Post Views Counter does not store view counts as custom fields in the default WordPress postmeta table. It stores them in its own custom database table instead. * The reason it uses a custom table is that view counts are a high-write, high- read data type. Keeping them separate from postmeta makes the data model cleaner and better suited for counting, reporting, and updates. For users, that usually means more reliable tracking, better performance on larger sites, and less clutter in the standard WordPress metadata table. * Yes, it still supports custom post types, so you can track views for any post type you choose. The counts are just saved in PVC’s own tables rather than as postmeta fields. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Post Views Counter] Getting Post Views Counter to work with Autoptimize properly](https://wordpress.org/support/topic/getting-post-views-counter-to-work-with-autoptimize-properly/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [1 month, 1 week ago](https://wordpress.org/support/topic/getting-post-views-counter-to-work-with-autoptimize-properly/#post-18879413) * Hi, * In PVC, both **J**avaScript 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: * ```wp-block-code 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Post Views Counter] Post views difference](https://wordpress.org/support/topic/post-views-difference/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [1 month, 2 weeks ago](https://wordpress.org/support/topic/post-views-difference/#post-18875549) * The difference you’re seeing is expected because Post Views Counter and Google Analytics measure views differently. PVC is flexible — it supports PHP, JavaScript, and REST API counting modes, and it includes options to exclude bots, logged‑ in users, specific roles, and IPs, and to set a custom count interval. Google Analytics relies on client‑side JavaScript, applies its own bot/traffic filters, and reports pageviews and sessions rather than raw server hits. * If you want PVC numbers to look closer to GA, try these steps in PVC settings: enable crawler and AI bot exclusion, exclude logged‑in users or specific roles, switch to the JavaScript counting mode (so it only counts JS‑enabled visitors), and set a reasonable count interval to avoid counting rapid refreshes. Also remember to compare the same date ranges and traffic segments when checking both tools. * Finally, keep in mind that exact parity is unlikely because the two systems use different detection and sampling methods;. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Responsive Lightbox & Gallery] Turn off drag&drop in media folder](https://wordpress.org/support/topic/turn-off-dragdrop-in-media-folder/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [1 month, 2 weeks ago](https://wordpress.org/support/topic/turn-off-dragdrop-in-media-folder/#post-18875494) * 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: * ```wp-block-code 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Responsive Lightbox & Gallery] Patch to fix issue where lightbox doesn’t work with cache-buster suffix in URL](https://wordpress.org/support/topic/patch-to-fix-issue-where-lightbox-doesnt-work-with-cache-buster-suffix-in-url/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [1 month, 2 weeks ago](https://wordpress.org/support/topic/patch-to-fix-issue-where-lightbox-doesnt-work-with-cache-buster-suffix-in-url/#post-18875475) * Thanks for reporting this and for sharing the patch. * We’ll review the proposed fix in detail, verify the scenario on our side, and– if confirmed – include the adjustment in the next plugin release. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Image Watermark] Hey, you’ve been using Image Watermark for more than](https://wordpress.org/support/topic/hey-youve-been-using-image-watermark-for-more-than/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 months ago](https://wordpress.org/support/topic/hey-youve-been-using-image-watermark-for-more-than/#post-18860406) * [@davidpeake](https://wordpress.org/support/users/davidpeake/) can you check your browser console? there should be some error message related to the Javascript or failed request * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Post Views Counter] Has stopped working in Version: 1.7.1](https://wordpress.org/support/topic/has-stopped-working-in-version-1-7-1/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 months ago](https://wordpress.org/support/topic/has-stopped-working-in-version-1-7-1/page/2/#post-18860404) * [@revixi5](https://wordpress.org/support/users/revixi5/) there must be a reason for it. Can you share a screenshot of your Counting page? Most probably something in your settings prevents that. * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Responsive Lightbox & Gallery] Wieder hier gelandet](https://wordpress.org/support/topic/wieder-hier-gelandet/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 months, 1 week ago](https://wordpress.org/support/topic/wieder-hier-gelandet/#post-18851761) * 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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Image Watermark] Watermarks have disappeared, cannot apply manually](https://wordpress.org/support/topic/watermarks-have-disappeared-cannot-apply-manually/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 months, 1 week ago](https://wordpress.org/support/topic/watermarks-have-disappeared-cannot-apply-manually/#post-18850730) * Hi, Updating to version 2.0.9 has no impact on images that were already watermarked in the past. Once a watermark is embedded into an image, it becomes part of the file itself, so the plugin version cannot remove or alter it by just updating the plugin. * What can happen, especially when updating from a much older release, is that the watermark settings need to be refreshed. In those cases we’d recommend to open the plugin settings, selecting the watermark image again, and saving the configuration. This ensures that all new features and settings introduced in recent versions are properly initialized. * After re‑selecting and saving the watermark image, applying the watermark again should work normally. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Responsive Lightbox & Gallery] [Bug] Grid layout broken after latest update – ignores all settings](https://wordpress.org/support/topic/bug-grid-layout-broken-after-latest-update-ignores-all-settings/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 months, 1 week ago](https://wordpress.org/support/topic/bug-grid-layout-broken-after-latest-update-ignores-all-settings/#post-18848698) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Responsive Lightbox & Gallery] Social icons in theme menu turn into colored dots after update (2.7.2+)](https://wordpress.org/support/topic/social-icons-in-theme-menu-turn-into-colored-dots-after-update-2-7-2/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 months, 2 weeks ago](https://wordpress.org/support/topic/social-icons-in-theme-menu-turn-into-colored-dots-after-update-2-7-2/#post-18845759) * Hi, * Thank you for the report. * We were able to verify this as a real regression. The issue is not with the standard WordPress Social Icons block in post/page content, but with widgetized/theme- rendered output. In affected versions, Responsive Lightbox & Gallery can interfere with that widget output and strip the icon markup, which leaves only the colored circular backgrounds visible. * As a temporary workaround, please try disabling the Widgets option in Responsive Lightbox & Gallery -> General settings. If that menu area is rendered through a widget/sidebar context, this should stop the plugin from modifying that output and the icons should display correctly again. * Please note that this is only a workaround, because disabling that option also disables Responsive Lightbox & Gallery processing for widget content site-wide. * We are working on this issue and plan to propose a fix in the next plugin release. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Responsive Lightbox & Gallery] Grid function no longer working properly](https://wordpress.org/support/topic/grid-function-no-longer-working-properly/) * Plugin Support [weiser](https://wordpress.org/support/users/weiser/) * (@weiser) * [2 months, 2 weeks ago](https://wordpress.org/support/topic/grid-function-no-longer-working-properly/#post-18845630) * 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/](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. Viewing 15 replies - 1 through 15 (of 50 total) 1 [2](https://wordpress.org/support/users/weiser/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/weiser/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/weiser/replies/page/4/?output_format=md) [→](https://wordpress.org/support/users/weiser/replies/page/2/?output_format=md)