Jeffrey2915

Thanks for that!

Yes, it seems one must wait 24+ hours for the API credentials to become active, as I am one step closer; now, the only message is:
“Auto Amazon Links: No products found.”

I have tried adding different product URLs, etc. but nothing works.

I have created new API credentials and will wait 24+ hours before trying again, and will report back here.

Thanks!

Thanks for that; will look into it!

However, there is a workaround to achieve what you’re looking for. One possible solution could be to use two different payment gateways. You can set one payment gateway for one product category and another gateway for the other categories. Each payment gateway can be linked to a different bank account.

Thanks for this suggestion!

Can you please briefly explain how to assign a Product Category to a second payment gateway?

Thanks!

Thanks for your response!

I inherited this website project from a previous designer, so I don’t know its history. Following your instructions for restricting API Keys, I indeed found a key of the same name in the Google Analytics account, though I’m unsure of its origins or purpose. Can you speculate?

I also found that the first version of your filters (.example.com/), specifically the dot prefix, was missing, so have now added it. I also regenerated the Key, as suggested by Google.

Do I need to do anything else?

If you’re still interested in the alert I received from Google, is there a contact from or email address to which I can send it?

Thanks!

Fantastic!

Those appear to be precisely what I’m looking for. Will dig into them now.

Thank you so much!

Thank you!

Great plugin!

• This reply was modified 1 year, 11 months ago by Jeffrey2915.

Has this issue been addressed?

It appears this plugin is not yet ready for WordPress v6.1.1, as upgrading throws a critical error, and debugging reports the following:

[23-Nov-2022 00:52:21 UTC] PHP Notice Trying to get property ‘term_id’ of non-object in /…/httpdocs/wp-content/plugins/hide-categories-products-woocommerce/hide-categories-products-wc.php on line 85

Thank you!

Great, wasn’t aware of that option.

Thanks!

Thank you for the speedy response!

Following up here for the benefit of others, as there is VERY little info to be found elsewhere.

In fact, we discovered that the problem was caused by a setting in the WooCommerce Anti-Fraud plugin.

The setting for “Check if customer attempts to make a purchase too many times within the time period configured below” was inadvertently set to 24 hours. This compounded the underlying problem, which was a misconfigured PayPal gateway; combined, they prevented both our troubleshooting efforts, and Customers attempting to re-submit their Orders.

Resolved!

Hello, @campkins

Were you able to resolve this issue? We recently began experiencing the same problem, and are unable to discern the cause.

Appreciate any insights!

Thanks for the answer, and for the speedy response!

This would certainly be a great feature to have, even if as part of the Premium version of the plugin. In the meantime, we’ll export to Excel or CSV, then import that to an email list manager such as Constact Contact or similar …

Thank you!

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

Thanks for the support!

Unfortunately, when I click on “Download most recently modified log file,” the dialog window states: “Loading log file … 502 (UpdraftPlus: could not parse the JSON)”.

But I was able to access the logs via cPanel; here’s a link to the latest successful full backup log.

Keep in mind that any references in the logs to “example.com” are in fact preview URLs being ‘proxied’ by Hosts.cx; the development site in question is not public and can be accessed only by this preview link provided by Hosts.cx. The DNS records still point to the previous host and site, which is live and slated to be replaced by this new site.

I should also mention that until 4 days ago, this development site was in fact able to make complete backups stored locally; backups began stalling/failing yesterday.

Thanks again!

Thanks for the response; great plugin!

RESOLVED

In fact, the new SSL Cert was NOT configured correctly on the hosting server.

All is well now!

RESOLVED

In fact, the new SSL Cert was NOT configured correctly on the hosting server.

All is well now!