[admin]

Please share a link to the page where the “Add to Cart” or “Buy Now” button is located. I need to inspect the page to check if any caching issue might be affecting it.

Also, please send a screenshot of the “Developers” menu from your Stripe account. I need to verify the API version currently set. You can reply to the email we sent and share the screenshot privately.

Next, reset the debug log files for both the WP eStore plugin and the Payment Gateway Bundle addon. After that, perform a test transaction and share the updated debug log files from both plugins. This will give me a complete overview of what’s happening. Feel free to send the logs via email as well.

[admin]

Hi, I’ve replied to your email but just in case it ended up in your spam folder, I’m copying the message here as well.

——–
Looks like your server’s firewall or security rule is blocking the post payment redirection after Stripe checkout via our plugin.

Please contact your hosting provider and ask them to temporarily disable ModSecurity for your domain, or whitelist the specific rule that is being triggered during the Stripe checkout.

You can send them this message:

“We are encountering a Not Acceptable! error from ModSecurity when attempting to complete a Stripe checkout using the WP Payment Gateway Bundle addon. Can you please review your ModSecurity logs and either disable ModSecurity for this domain or whitelist the rule being triggered? The request is being blocked incorrectly by ModSecurity.”

[admin]

Hi, Use the support contact form on our site to get in touch.

Customer Support

[admin]

The log data you shared looks good—there was no issue with that transaction. The PayPal Standard checkout you’re using doesn’t redirect to any error URL by default.

Could you please share a screenshot of the error URL you’re referring to? That would help me understand the issue better with a visual reference.

This is most likely a site-specific issue related to your server environment or a potential conflict.

The first thing to check is whether you have any caching enabled on your site. If caching is active, it’s possible that users are being shown a cached page containing an error message from a previous failed transaction.

The e-commerce functionality needs a dynamic page being shown to the visitors (so they are seeing the latest values/data of a product). A cached page simply shows a static cached page (our plugin doesn’t get a chance to apply the latest calculation and price to that page). When a cached page is being shown, the user is not actually being shown the updated price values of a product. That’s what causes the issue with e-commerce type setup because an e-commerce type site is not the same as a blog type site. Caching is normally fine with a Blog type site where there is no need to show updated content.

If your caching solution has an option to disable caching when a cookie is present, then I can tell you which cookie to set in the configuration of your caching solution or plugin. Otherwise, you can ask them if you can exclude the page containing the products to be excluded from caching.

Exclude the pages (containing the payment buttons and the thank you page) from caching.

[admin]

No, the update should be done by using database query. We don’t advertise any feature like that so there is no method for it out of the box.

[admin]

Here is an example code showing how you can access the custom fields of Form builder addon.

$member_id = "123";
$field_key = 'kursleiter';
$custom_value = wp_emember_get_user_details_by_id($field_key, $member_id);
echo "Value of Kursleiter: " . $custom_value ;

[admin]

Unfortunately, the label cannot be sent to PayPal due to a character limit imposed by PayPal. As our plugin does not meet the specific requirements of your project, we kindly recommend reaching out to us via the contact form on our website. We will be happy to process a refund for our plugin so you can explore alternative solutions for your site.

[admin]

Hi, The label can’t go there since PayPal has character limits for that field. We keep that field for value only so that the character limit is not exceeded.

You can view the details of custom fields, including the label, within the Customers menu of the plugin. The “Viewing the Customer Input Data” section on the addon’s page includes a screenshot illustrating how it should appear:

WP eStore Addon – Collect Customer Input in the Shopping Cart

[admin]

Can you post a URL of the page containing the button so I can inspect the behavior from my browser?

[admin]

PayPal deprecated the smart payments button a long time ago.

[admin]

There might be a conflict with the theme or another plugin on this site. I need more visual details to identify the potential issue. I will send you an email so you can reply with the necessary visual details.

[admin]

Hi, Something would have to have changed in your site/server for it to start behaving differently.

We don’t have any way to control your site/server environment. So it is about finding out which aspect of the environment is causing the unexpected behavior.

Can you please tick/check the following checkbox from the settings menu of the plugin so the inline login option is not used (that one might be conflicting on the site):

Disable Inline Login Widget

Have you done the following test already?

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

[admin]

Hi, Our plugin cannot handle that particular scenario that you described. The plugin updates the inventory after the payment has been made. So if there are a lot of users trying to purchase the same item at the same time and you have a limited quantity, it can face the issue that you explained. When they add the item to the cart and keep it in the cart while someone else is paying for it at the same time, someone can miss out.

I have sent you an email for it.

[admin]

Simple Download Monitor (SDM)

SDM Debug Logging Feature – https://simple-download-monitor.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/

[admin]

Hi, You may have specified a membership level ID for this one time eStore product which is then treating it as a membership payment. The last membership payment is used as the reference in the member’s profile.

If this one time eStore product is not for a membership payment, then don’t specify a membership level reference for it. Edit the WP eStore product in question, and then remove the reference that makes the product a membership payment product:

WP eMember and WP eStore Integration for Membership Payment

Only use the integration for the product that is for a membership payment.

Let me know if that explanation helps.

[Author]

Posts