gravatard

Thanks again!

Thank you for the update.

Are you aware of any other pricing rules plugins that do not use the same hooks/filters? I see other plugins on the market.

Or do you suspect they all tap into the same hooks/filters as Wholesale Prices?

Thank you for the reply, I will try this.

As a quick aside, are you aware of any conflicts with Wholesale Prices Premium plugin? I saw there was a conflict 2 years ago between your plugin and theirs.

Hi, I shared a staging site with your website support team and they discovered the issue. Thanks. This issue has been resolved by following the requested steps to remove this code from wp-config: https://postmansmtp.com/post-smtp-1-9-0-better-support-for-secure-delivery/

However, despite being able to enter new username/password, I was still getting authentication error. I was able to resolve that by choose SSL over TLS and following this article to add DMARC record for domain: https://wpmailsmtp.com/how-to-create-dmarc-record/

Not to derail this thread but OP is dealing with the exact same issue as me: https://www.ads-software.com/support/topic/authentication-error-21/

Hopefully that clarifies.

Hi @haseeb0001,

Unfortunately that thread is not relevant to my issue. My email host is PrivateEmail.com, but the issue seems to stem from Post SMTP plugin not allowing me to update the username/password fields.

I reset the plugin using the reset option within your settings page, which deleted the email logs, but didn’t solve the issue. Running the wizard again I ended up in the exact spot as before with the wrong email account grayed out.

Deleting and reinstalling your plugin didn’t solve the issue either. The same old (wrong) username/password was there and unable to be changed.

There is clearly a bug within your plugin that needs review. From uneditable username/password fields in wizard/manual setup, through settings that don’t get wiped from the database upon uninstall.

Regardless, I enjoy your plugin when it works and hope to not have to switch. Thanks!

I think I figured it out. Here are my troubleshooting steps:

1. Download and review the .htaccess file. No obvious age gate blocks detected.
2. Reset file permissions at server level, in case it’s a server block. No change.
3. Allow “age-gate” REST API namespace in WP Cerber Hardening section. Fixed issue!

Step 3 seems to have worked. After clearing cache I can access the website using the Age Gate form again without 403 Access Forbidden console error.

Issue resolved! Thanks!

Hi @philsbury

Did you figure it out and push an update?

Hi @philsbury

It’s WprdPress sending these reports. Here’s a breakdown of the entire email:

Subject Line: Your Site is Experiencing a Technical Issue

Howdy!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Age Gate.

First, visit your website (https://www.domain.com/) and check for any visible issues. Next, visit the page where the error was caught (https://www.domain.com/wp-login.php) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

https://www.domain.com/wp-admin/?action=enter_recovery_mode&rm_token=U34WYcCd.............

To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.6.2
Current theme: Custom (version 1.0.0)
Current plugin: Age Gate (version 2.13.6)
PHP version 7.3.27-1+0~20210211.76+debian9~1.gbp8355b8

Error Details
=============
An error of type E_ERROR was caused in line 114 of the file /home/public_html/wp-content/plugins/age-gate/public/class-age-gate-public.php. Error message: Uncaught Error: Call to a member function is_edit_mode() on null in /home/public_html/wp-content/plugins/age-gate/public/class-age-gate-public.php:114
Stack trace:
#0 /home/public_html/wp-content/plugins/age-gate/public/class-age-gate-public-presentation.php(201): Age_Gate_Public->is_restricted()
#1 /home/public_html/wp-includes/class-wp-hook.php(287): Age_Gate_Presentation->change_page_title(Array)
#2 /home/public_html/wp-includes/plugin.php(212): WP_Hook->apply_filters(Array, Array)
#3 /home/public_html/wp-includes/general-template.php(1233): apply_filters('document_title_...', Array)
#4 /home/public_html/wp-includes/general-template.php(1257): wp_get_document_title()
#5 /home/public_html/wp-includes/class-wp-hook.php(287): _wp_render_title_tag('')
#6 /home/25

Is it from a possible plugin conflict?

Hi Phil,

Any chance you’re looking into this issue?

Hi Phil,

Yes I am using Elementor on this site.

The issue was SG Optimizer plugin by SiteGround. I was deferring JS. Disabling this option cleared the console error. Thanks!

That resolved the issue, thanks!

Hi, I have activated the plugin, and you’ll see in topbar menu, the Facebook text is vertical (which is the error).

URL: https://www.newhopebelleville.com/

I have not implemented the shortcode or widget on any page currently, just activated the plugin to display the error.

I figured it out. I use ATUM Inventory to manage stock levels. I set WooCommerce Low Stock threshold at 2, Out of Stock at 0.

In ATUM Inventory, for all Variable Products I set the parent stock to 1 (variations have their own stock levels of course).

This helped products not show “Out of Stock” on the store, but didn’t allow for quantity field/selector.

To fix this, I updated all Variable Products parent stock to 3 instead of 1. This is above WooCommerce Low Stock threshold of 2, so now quantity field selector works for each variation.