Jeff McNeill

Still no idea why, and apparently no one has any ideas on this?

Yes, that’s it, React is not loading. No idea why.

Wow, ok. Thanks for pointing that out. I didn’t look closely at that widget. Will be using the one included in your plugin. Thanks again!

@drlightman if you aren’t here to support this issue, or have useful advice, kindly stay off the comms. Read more about pagespeed https://developers.google.com/speed/docs/insights/v5/about and CLS https://web.dev/cls/

For me, I’ve switched to luckywptoc, and suppressed the js and css files, and now have no degradation of pagespeed.

Nope

Well, other caches certainly could, for example W3C which I believe is mentioned, not to mention web server caching/opcache and the like. If the update did not clear out the cron job, much less have a way of dealing with these missing files/directories being called, then any persistence due to third party/web server caching could explain what is happening. Did you see my reference above to the cron job error, which took place after upgrading the plugin? I’m sure “lots of testing of the new beta” happened, but something was missed.

P.S., I did see an error related to this from a cron job as well:

PHP Warning: include_once(): Failed opening ‘classlesses/autoptimizeExtra.php’ for inclusion … in /var/www/html/wp-content/plugins/autoptimize/autoptimize.php on line 330, referer: …/wp-cron.php?doing_wp_cron=1538040526.7750680446624755859375

I’ve had a similar issue, but more of random 500 errors (but not all requests). My guess is that parts of the old version of the plugin were cached by other caches, browser caches, intermediate Internet caches, and the like. It seems that re-architecting the plugin was the cause of these problems, and there was not any regression testing regarding the plugin upgrade. Anyway, that is my best guess by looking in the logs.

If you respected your users, then you will delete this last comment which is insulting and wrong. You are misleading. There was nothing in the FAQ.

Obviously the “feature” you had added without any good reason was complained about enough so that you later added an “opt out” option in the control panel. Why not take responsiblity for this “functionality” that was unwanted and unneeded and has nothing to do with the plugin? Because you are not the developer but some talking head who can’t admit the mistakes made to add unwanted spam. The plugin still has this unwanted spam functionality that people must disable.

This is not respecting the user. This is misleading the user. And once again the problem that was created by your developers, adding this unneeded and unwanted feature is somehow the users fault? Yeah, right.

You are completely tone deaf here. Take responsiblity. Apologize. Stop blaming the user. That would be being responsible, that would be respecting the user.

You deliver a mediocre produce which requires disabling a non-essential and unwanted feature. Until that is removed, any claim to delivering “one of the highest quality plugins out there” is a sham and a lie.

Wasting my time responding to the inane rebuttles is the best thing I can do, showing both respect and courtesy that some day you may understand what it is you are doing wrong, so that you can do better. You can do better. Time to grow up.

Wrong, wrong, wrong. It is good to talk to developers, whether about free or paid apps. Feedback is necessary to make products better. A plugin FAQ doesn’t help if it is for a different version, and if you found an answer for my question in the FAQ, remember that my feedback was two months ago, when it was not present. I do respect the time of others, and provide very useful and effective feedback. Regardless if something is premium or not, SAAS or not, quality is important and expected. I contribute to free products both in terms of code and in terms of issues. You should respect the user.

Same problem here. However, I am unclear about what I am supposed to do about the /woocommerce/templates/emails folder/files.

I’ve commented out line 71 in includes/classes/rp-decorator-customizer.class.php but that did nothing.

This was working fine with the same theme and an older version of woocommerce, so likely they broke the customizer, but I do not know what steps to take next.

Please advise.

– Wrong, there is no “Disable Security Alerts” setting.
– Wrong, what the plugin does is make the mistake confusing “Insecure WordPress version detected” with “WordPress … which has x known security vulnerabilities”. Just because a version has known security vulnerabilities does NOT mean that the version detected is in fact the actual version running (duh), or even that it is insecure in its particular configuration. False means false, not a particular kind of false. Here is the quote:

Insecure WordPress version detected. Your site is running WordPress version %1$s, which has %2$s known security vulnerabilities. You should upgrade WordPress as soon as an update is available. If no update is available yet, then it may be necessary to apply other threat mitigation solutions. More Information

– Wrong, SPAM is unsolicited commercial messages. By intrusively populating messages in the admin console, with your company/product name, and with links to company/product information, that is unsolicited, comercial messages. Advertising doesn’t even need to imply that you make money, but that the intent and the meaning is advertising (the fact I really cannot turn this off is a huge clue here, and the fact that I was not asked to turn this on, and it is not a part of the functionality of the plugin).
– Wrong, just because security is a big umbrella term doesn’t mean that you can provide security alerts about the operating system (true or false). This is unneeded and unwanted behavior, and I cannot disable it!
– Wrong, open source software doesn’t mean you get a pass with ongoing spammy behavior.
– Wrong, I don’t have to submit a support request. Reviews are a valid place to post positive and negative experiences.
– Since every single point you have made is wrong, and you mislead again and again on these points, it seems obvious that you don’t take the users/customers side in this matter.
– I would ask that you take a step back and honestly reconsider this “functionality” that you have spent time defending, when it is in fact indefensible.
– My review is fair, my friend.

Take care.

– Jeff

Moved this release over to Gitlab, with a little renaming:

A forked version of the pre-spam 0.57 version (not updated since then, but renamed to comply with any trademark issues) is available on Gitlab:

https://gitlab.com/jeffmcneill/wpx-widget-logic/tags

A forked version of the pre-spam 0.57 version (not updated since then, but renamed to comply with any trademark issues) is available on Gitlab:

https://gitlab.com/jeffmcneill/wpx-widget-logic/tags

Hi Leland,

I’ve added this as an Issue in the Github repository. CF7 is a contact form pluing, not a registration plugin, so the idea is to stop contact form spam. Shouldn’t be too difficult. I’ve added it to my June task list, if someone else does not address by then.

Sincerely,
Jeff