[admin]

Quick summary update to this issue:

Looks like a value of 0 was entered for the following expiry email option.

Number of days before the account expiry when the reminder notification is sent

A value of 0 disables that email as explained in the help text below the field. The minimum accepted value is 1 which will send an email 1 day before the expiry.

[admin]

For the Stripe SCA checkout, the checkout page and the fields (within the checkout form) is handled by Stripe.

The phone number field is not a required field in our plugin’s standard checkout process. Can you please give me a bit more information in terms of how you had this phone number field there? Was it added via a customization?

[admin]

It will be good for me to check your log and the setup. I have sent you an email for this.

[admin]

We replied to your email but I will post it here also just to make sure you get this info:

It Looks to be a UTF-8 character encoding issue. The character set is not set to UTF-8. Check the following settings of the PayPal account:

Some Characters and Text Not Recognizable in the Notification Email

[admin]

There is some kind of conflict on this site or a database corruption that has happened. I am going to send you an email so I can get some private details so I can provide help.

[admin]

Glad to hear you got it sorted out.

[admin]

WP eStore is PHP8 compatible. Some of the addons may not be fully compatible yet. I just need to see which addon and which function of the addon is causing an issue with PHP8 and I will sort it out.

Can you please load a fresh copy of the eStore plugin:

Re-install or Load a Fresh Copy of the Plugin(s)

Also, load a fresh copy of the Order Management addon by downloading it from here:

Addon Downloads

[admin]

Which version of the order management addon are you currently using?

Which version of PHP is your server using?

Are you using the variation configuration addon? If you are then can you please temporarily deactivate that addon then do a test and let me know if the result is the same or different?

Also, please share the content of the log file so I can take a look at it see if the processing is getting stuck somewhere. You can also use the contact option on the site to get in touch (if you want to share the log file privately).

[admin]

If the debug log file is empty after a transaction, it means our plugin is not receiving the payment notification from the payment gateway (in this case Stripe). So we have to look at what setup configuration is missing for Stripe. It is likely that you haven’t setup the Stripe webhooks according our following documentation. Can you please double check this and let me know if you have setup the webhooks (step 9 in the following setup document)?

WP Payment Gateway Bundle – Stripe Checkout SCA Setup

If you have setup the webhooks, then it could be that there is a firewall or security setup on the server that is blocking the webhook information that Stripe is sending to our plugin. Some firewall or security plugins will accidentally block Stripe notifications. So it is a good idea to do the following and do a test:

Test to (How to) Identify a Conflicting Theme or Plugin

Also, post a URL to the page that contains the payment button so I can inspect a few things using my browser.

[admin]

In your email, you mentioned that you amended an existing subscription payment button temporarily and changed the pricing on it. That can cause this issue since for some of those users/members, the payment verification can fail. I will reply to you via email but I will also post an explanation of the issue here just in case you don’t receive the email:

Changing an existing subscription button on the fly is not recommended since a subscription agreement has ongoing payments that can affect future incoming payment verifications if the existing product prices are altered. Let me give you a simple example to illustrate the issue. Let’s say you have a subscription payment button that charges $10 per month. A few users subscribe to that payment. Now, you alter that payment button/product and set the price to $20 per month. When a payment notification for a recurring payment (from a user who subscribed at the $10 price tag) comes in, the plugin will fail that verification since it expects that product/payment button’s amount to be $20. It will assume that somebody is trying to pay less than what the real price is (some people out there will try to do this so the plugin has a guard against it).

So when you want to offer a new/different subscription pricing option, do the following:

– Create a NEW payment button/product at the new price or offer.
– Edit the page containing the payment button.
– Replace the old button with the new button so the new users interact with the new button.
– You can replace the button again if you want at a later time.

The payment from old users will continue to be processed correctly since you didn’t alter that payment pricing.

[admin]

At the moment it looks like the “open checkout in a new window” option is enabled. That option could be having an issue in Safari browser with the ajax request. The Ajax request is needed for the collect customer input addon.

Uncheck the following checkbox from the Advanced settings menu of the plugin:

Open Checkout in a New Window

Let me know how it goes in safari browser after that.

[admin]

There could be another plugin on this site with a JavaScript error that is breaking the functionality of the customer input addon. Can you please post a link to the page where I can go and add an item to the cart and view the cart? I can then inspect it from my browser and see if there are any JavaScript errors on the site.

[admin]

You can look at the second shopping cart template option which doesn’t use any icons:

WP eStore – Shopping Cart Templates (Full Cart Display Options)

[admin]

All our plugins remain compatible with WP 6.0.2

[admin]

We will send you the addon via email.

[Author]

Posts