CGS Web Designs

Jumping in here just to help out – @ciarando I had similar behavior using the Square payment gateway. I was able to experience the issue on your site – simply couldn’t type into the credit card form. In my case, it was caused by the Autoptimize plugin performing code minification on the cart page. If you have a plugin doing .js or .css minification disable it, clear your caches, and then check again. If that resolves it, then you may have to look into your plugin settings to exclude the checkout page from optimization.

I have the same issue.

I’m not sure this is a false alarm. According to WP Vulnerability Database (here is the link) and the associated documentation within, ManageWP confirmed they were not activating the plugin or providing support in response to the vulnerability.

Timeline
2019-09-05 Identified the vulnerability
2019-09-06 Contacted ManageWP
2019-09-09 Contacted plugins@www.remarpro.com
2019-09-10 Response by ManageWP requesting more details
2019-09-11 Response by ManageWP that they are not actively maintaining the plugin and don’t provide support
2019-09-20 CVE assigned
2019-10-16 Public disclosure

Honestly – even if the vulnerability is a false alarm, ManageWP’s response to the inquiry is enough to remove it from every site you have because it’s only a matter of time before there is a real problem that they aren’t going to resolve. Why wait until it’s too late?

• This reply was modified 5 years, 4 months ago by CGS Web Designs. Reason: Ticking for email replies
• This reply was modified 5 years, 4 months ago by Jan Dembowski.
• This reply was modified 5 years, 4 months ago by Jan Dembowski.

I guess you can forget about it, I switched to a different plugin.

I’ve done all of that, multiple times, with no luck.

Marking as resolved.

As I said before, I tried this on 2 separate computers using Chrome and experienced the same issue. My primary computer does have some add-ons, but the second computer I tried it on was my work computer which has no add-ons in Chrome (they’re not allowed). Identical results until I happened to try it with Firefox and it just worked. I guess we’ll never know! But something to keep in mind in case anyone else reports a similar issue.

Also I gave you a 5-star review.

I have resolved the issue – but please read what I found as it may be useful.

Performing the steps you’ve requested the console shows one warning when the page loads, but clicking the close button literally does nothing – no additional activity in the console. The warning on page load is as follows:

DevTools failed to parse SourceMap: https://[redacted-domain]/wp-content/plugins/activity-log-mainwp/assets/js/dist/index.js.map

This warning doesn’t appear in the console during any other navigation around my MainWP dashboard. I’m using the default WordPress theme Twenty Nineteen. The only plugins I have installed are MainWP extensions and UpdraftPlus Pro.

HOWEVER: I was using Chrome. In order to provide as much information as possible, I also decided to run the same process using Firefox. However, when I used Firefox, there were no warnings and the nag did close successfully. Of course, now that the flag has been set, the nag is also now gone from my Chrome instance. I’m satisfied with that.

To be clear, I observed this behavior using the latest version of Chrome on 2 separate Windows 10 computers – so I know it’s not MY specific computer that has an issue. It’s definitely something in Chrome.

And, yes – you call it an advertisement, I call it a nag ?? Great product by the way – It’s on my list of plugins to buy once I have a few more clients on the books.

@davidanderson Sorry I have been busy today with some other projects, I installed this update you published on one of my sites and that alone seems to have resolved the issue. I’ll have to go back and update all the others & test, but so far it looks promising. Thank you for sticking with this.

Here’s the screen grab you asked for – it takes about 5 – 10 seconds before the alert pops up. The section of text in the console that begins with ReferenceError is the output at that time.

https://snag.gy/VZOqMv.jpg

I’ve never enabled the new caching options on the plugin. Also, I’ve tried disabling my existing caching plugin & clearing the cache to no affect. Also disabled all my plugins etc… no dice.

Setup:

I’m using 2 different shared hosting accounts – so I don’t have much control over the servers. I use one for all of my production sites and one for their development twins. I have many sites so I haven’t had time to test them all, but in general it seems only the sites on the production account are throwing this error. So, I agree that the response has something to do with the specific setup & probably has nothing to do with themes/plugins.

Both shared hosting servers have similar set ups – there is a difference in the OS version but that’s about it. As far as modules & PHP versions, everything between the two is identical.

There’s one twist though – when I first discovered this issue, I looked at one of my development sites and it was throwing the error as well. But 8 hours later, the error is not throwing any longer – and I’ve made no changes. Caveat: I was wildly flipping back and forth between production/dev quite a bit trying to figure out what was going on so I suppose there’s a chance I looked at the production site by accident, but I’m pretty sure that’s not the case. At this time however it seems only the sites on my production setup are throwing the error, I can’t find any instance on my development setup where this is occurring.

As far as site health info, that is a lot of information disclosure to post in a public forum – is there a way you can accept the information privately?

I agree with the OP, I really liked this plugin for specific DB optimization. Now it’s got all this other stuff I don’t want junking up my sites. And some of them after this update are now getting a pop up error stating “an unexpected response was received” whenever I load any of the WP-Optimize setting pages on the back end. Messy.

I have the same problem immediately after updating.

(edited to flag for follow-up replies via email).

• This reply was modified 5 years, 8 months ago by CGS Web Designs.

Did you try the CSS edit I posted?

I’m not an authority on CSS, but the WooCommerce stylesheet for your site appears to have this section regarding the price:

.woocommerce ul.products li.product .price, .woocommerce div.product p.price, .woocommerce div.product span.price {
    color: #f66f66;
}

Add that to your custom CSS and then change the value after color: perhaps to #000000 just to check it – that should make the text black.

What’s the url of the one of your product listings?

• This reply was modified 5 years, 8 months ago by CGS Web Designs. Reason: Ticking for email replies