Bliss7

@247wd

Nothing happens when the X is clicked. Absolutely nothing. A few other plugins also have such an annoying issue. The issue is further complicated when some sites can dismiss this nag banner, and other sites are unable to dismiss such banners (nothing happens when the X is clicked).

I hate it whenever this thing happens. But it is not for WordPress to explain, it is the developer that should explain.

@bisratlearn

I’m just reporting on a bug to you guys, so maybe you can fix this in another update soon. I don’t think sharing my particular System’s Status would be helpful, as you yourself indicated that this is indeed a widespread issue with Firefox at least. The Dismiss button on the Notice is simply not working, and that’s all for this problem. I hope the Woocommerce team can take note of this problem and issue an update that resolves this problem.

@cookieyesteam

When you say obtaining full certification, what do you mean? To my mind, it makes sense if your plugin is a plug and play solution, as in people just install your plugin and it comes complete with all the privacy notices/wording being fully enabled upon plugin activation.

It does not make sense to me, to get “certified” when upon downloading and activating your plugin, we still have a lot of work to do to customize it in order for it to “comply” with the GDPR laws.

What am I missing?

I have a problem with this plugin, like others I gotten that Technical Error email. This was a site that I only now updated the plugins and something went wrong.

What to do? There is an old code stuck and tattooed to my site now. It is some breadcrumbs from earlier Yoast SEO plugin settings.

@mostafas1990

The issue of leftover residue URLs is still an issue. In Google Search Console, it looks like this (My domain is redacted).

https://www.my-site.com/wp-json/wpstatistics/v1/hit?_=1546603729

And such issues cannot be fixed because these URLs don’t exist anymore, and will remain as 404s in the Google Search Console for a long time.

@mostafas1990

1. The WP Statistics plugin has long been deactivated and even deleted. It does not exist on my site any more.

2. Litespeed Cache is enabled, and everytime I update any plugins, the cache is flushed, so it should not be an issue, unless there is a more complete flush that I do not know about. I have flushed everything just now just to be sure, and Revalidated the issue in Google Search Console.

I will report back if the issue remains. Thanks.

There may a reason to keep using this plugin even though it seems iffy now.

If you have a website ranking well, would removing the plugin and replacing with another affect the rankings, even if albeit temporarily?

Would you risk this?

I am struggling with this dilemma. But the author or owner of this plugin has not even updated us (the users) about how it’s going.

Iffy….. sigh/

So is there any update to this? @sharethis

@alanfuller

Thanks a lot for your effort, Alan.

I must be one of the most ardent users of this plugin, as I could not and still cannot find a plugin that is as simple to use as this one. So that is why I installed it on most of my sites.

I will await the return of this plugin with bated breath. Next week or two, you think?

@wpmudevsupport12

Well, all the links that were previously reported in error as 403 are now gone already from the plugin.

The issue seems to have gone away. on its own.

@alanfuller

Hi Alan,
Thanks, this plugin has been installed in many of my sites. So when something like this happens, it’s a PITA.

Can you suggest any similar plugins that resemble this plugin? All the current contact form plugins are just way too bloated and complicated.

Or when will it be back? Any rough date?

So, what should I do?

Should I create a redirection for them to redirect them to the homepage? Is it safe to do so or will I interfere in the functioning of Yop Poll on my site?

Or are these just auto generated from normal visitors coming to my site and can be ignored?

@yourownprogrammer
The latest version for sure. All updated.

@asaldel

Thanks, yes the latest update fixed the issue.