sparky672

My review is only my opinion of a plugin, which includes settings, GUI, UX, usability, convenience, etc. This plugin only has one purpose, which is to make my admin tasks easier and more convenient and it has failed at this one simple thing.

IF in order to use the plugin properly, I have to sort the main posts page by date published, then it’s not convenient or a good user experience.

In every WordPress installation I have ever used, no matter what theme, the default sorting column of PAGES is title (alphabetical), not date published. Also keep in mind that post sorting on any main posts page regardless of post type can be re-sorted by various columns by the user at any time, thereby completely disconnecting how one expects this plugin to navigate through posts.

If the plugin is also not “connected” or in sync with PAGES, or other post types using any other column besides “date published”, then this whole thing needs to be reconsidered, in my opinion.

If this is fixed in a future version, let me know and I will happily retract or modify my review.

Asking the user to choose a selection that doesn’t even exist because some obscure hidden setting is disabled by default, is a VERY poor GUI experience. The note should be dynamic and accurate. Please fix this.

• This reply was modified 7 months, 2 weeks ago by sparky672.

I have the AVADA theme on my woocommerce store.

After debugging this with the theme provider, they found that one of their theme files needed to be fixed according to the latest woocommerce updates, which they have sent me as a temporary fix until they implement this fix in their next theme update.

The file that needed to be changed is in the theme > Includes folder and for the avada theme this was the file class-avada-woocommerce.php.

You can contact your theme provider to provide you with a temporary fix if you want.

Can you kindly share the contents of this file here? I also have Avada and would rather not wait until the next update to get my error logs to stop exploding. I would also rather not start from scratch with trying to convince Avada tech support that this issue is theirs. Thanks.

• This reply was modified 8 months, 1 week ago by sparky672.

Absolutely ridiculous.

I think something like six updates have been pushed out since this bug was reported and none contain the fix. Imagine the millions of missed opportunities to use ApplePay caused by this – Apple should be thrilled. Ding dong!

Wow… three months without this very simple bug fixed!

All afternoon on the phone with my host checking the server’s SSL and TLS settings… then on chat with WooCommerce going through various troubleshooting steps. Finally, he asks me to trigger the error log and we see an error message that the domain name erroneously contains a subdirectory.

Even after finding the issue via chat, WooCommerce tech support is completely unaware of this bug. Not only that, their suggested solution was to toggle Express Payments option on/off to force a manual refresh of the domain. Of course this would never work because the code is written to fetch the subdirectory.

I finally had to modify this line of the plugin identified above. I changed get_site_url() into get_bloginfo('url'), which correctly returns only the site’s domain name without a subdirectory.

This worked and Apply Pay was activated, but it’s not an acceptable long-term solution as it will break as soon as the next plugin update is applied.

How this was never fixed months ago is absolutely absurd. Lots of people give WordPress its own directory; so many that there’s even this support article at WordPress about it.

I wonder how many of the 455 million WordPress installations are in a subdirectory, AND also use this plugin? Surely it must translate into many many tens of thousands missed opportunities to activate Apple Pay.

This theme appears to be dead based on the lack of activity in this forum.

Regardless, I had only tested this yesterday in Safari 13.1.2 and Chrome 97.0.4692.99 on a Mac, and just assumed it was widespread based on the failure in Chrome.

However, today it’s working in Firefox just fine; and when testing in Chrome, it’s working there now too. Just an issue with Safari, which is technically an out of date version.

I had only tested this yesterday in Safari 13.1.2 and Chrome 97.0.4692.99 on a Mac, and just assumed it was widespread based on the failure in Chrome.

However, today it’s working in Firefox just fine; and when testing in Chrome, it’s working there now too. Just an issue with Safari, which is technically an out of date version.

• This reply was modified 3 years, 1 month ago by sparky672.

It’s just a PHP notice, not an actual error.

Correct. But since the form is on the home page, the log was just endlessly filling up.

Thank you for the prompt response!

It’s in the right sidebar on the edit form page.

I found it. It was already set to “Yes”.

So I think I found the actual problem. The form did not have a name. The box for “Form Name” (The title of this signup form.) was completely empty. I don’t know how that’s possible… maybe my client got in there and accidentally deleted?

I entered a name and the errors went away. Not sure how that’s related to the Ajax though or if you can make it fail more gracefully if name is missing.

Do you have AJAX disabled for that form?

I don’t even see a setting for disabling Ajax for the form. EDIT: I found the setting for Ajax. It was already set to “Yes”.

The errors are triggered by nothing more than loading the page that contains the form.

• This reply was modified 3 years, 2 months ago by sparky672.

Of all the convoluted nonsense!

I too have the same issue with the same symptoms. I could not get the setup widget to go away until I faked certain steps- “skipping” them did nothing. Then the setup widget still stayed there but it was just an empty box.

I had to repeat the setup wizard again in order to get the dashboard widgets to sort themselves out. I’ve had my store installed and working for over a year so why does something like this keep happening? Is the development team not beta testing each release?

Add this issue to the constantly having to edit the database to dismiss the “thank you” notice after updating.

Besides release notifications (removed as explained above), Yoast SEO shows other types of notifications that are important for your site.

JUST MAKE IT ALL STOP! PLEASE! I cannot tell you how many times I’ve had to hide the notification about integrating Yoast with WooCommerce. Why can’t I permanently delete this, one time, forever?

I. DO. NOT. WANT. TO. INTEGRATE Yoast with WooCoomerce. Yet there it is again… and again… I’m about ready to delete the plugin.

EDIT:

This plugin kills the Yoast nonsense: https://www.ads-software.com/plugins/so-clean-up-wp-seo/

• This reply was modified 3 years, 7 months ago by sparky672.

I have WooCommerce 5.0.0 and also see this bug! I had to manually edit the database as described by SSVapes as it was the only way to clear out this persistent message.

I should not have to edit db tables to get the nag to go away. Seriously… this was reported many versions ago and should be fixed.

It’s explained in the plugin documentation: https://wpcerber.com/wordpress/malware-scanner/

Your blog is all jacked up. Click on “continue reading” button for each of the articles and they send you elsewhere.

“continue reading” button on the “What Cerber Security Scanner scans and detects” goes to the “Manage multiple WP Cerber instances from one dashboard” article.

“continue reading” button on the “Troubleshooting malware scanner issues” goes to the “WP Cerber Security 8.6” article.

“continue reading” button on the “Automatic cleanup of malware and suspicious files” goes to the “WP Cerber Security 8.6” article.

Please be more specific; what is “my ACP”?

Seriously?

ACP =>
Admin Control Panel =>
the screens where you administer and control your site =>
the place where the Dashboard screen is located =>

https://www.ads-software.com/support/article/administration-screens/

To update a theme or plugins automatically:

ACP > Dashboard > Updates > click on each update

• This reply was modified 4 years, 12 months ago by sparky672.