problematichild
Forum Replies Created
-
Hi @inpsydekrystian
Thanks for the update and for escalating this internally. Please keep us posted on the progress and let us know once the filter becomes available.Hi @inpsydekrystian
We understand that Pay Later and vaulting cannot typically be enabled together by default. However, to utilise both features, the merchant was manually added by PayPal Support to an allowlist, which grants access to certain functionalities that are otherwise restricted.PayPal Support has also provided an option to enable the “Pay Later 2nd Button,” which serves as a dedicated entry point for Pay in 4.
With this configuration, the Pay in 4 button appears for one-time orders, while vaulting for recurring payments remains available and is not fully disabled.
We have reached out to confirm whether the recent updates on the plugin side may have affected our previous setup.
We have also contacted PayPal directly to verify this, as we want to determine whether this behaviour falls outside the scope of the plugin’s capabilities.
We’ve already reviewed the relevant Stripe and WooCommerce logs around the affected orders, and we were not able to identify any Stripe-side errors or failed payment events during the time these issues occurred.
From our investigation so far, we can also confirm that the duplicate WooCommerce orders are linked to separate Payment Intents in Stripe, and both Payment Intents show as successfully completed and charged.
What we are seeing suggests that in some cases customers may be experiencing a disruption during the checkout flow, which may prevent the checkout from cleanly redirecting to the “order received” page. In those scenarios, the customer may assume the transaction did not go through and attempt to place the order again, resulting in a second successful payment and duplicate order creation.
Based on this behavior, could you please advise on the possible cause of a checkout flow not completing the final redirect or confirmation step and any recommended fixes to prevent this from occurring?
https://prnt.sc/hfq_kWbbNSit
https://prnt.sc/EcbuNk8w8q-x
https://pastebin.com/Z8DMPuJ0Hi @lastsplash , thanks for looking into this. It seems to be working now after applying the filter you provided.
Everything looks good on our end. Thank you.
Hi @tamirat22 ,
Thanks for the update and for escalating this to the development team, really appreciate you looking into it.
We’ll wait for your next update.
Best regards
Forum: Plugins
In reply to: [Autoship Cloud for WooCommerce Subscription Products] Disable DiscountWe have updated the discount percentage and cleared the cache. The updates now seem to be reflecting correctly. Thank you for your assistance!
Just one thing to confirm: in the Product Page Autoship Info Link content, does it only accept plain HTML? Is there another option to add shortcodes?
We would like to create the content using Elementor and then add the shortcode, but it seems to be reading the shortcode as plain text instead. Here’s a screenshot for reference: https://prnt.sc/AweRgUUyzRRG
Forum: Plugins
In reply to: [hCaptcha for WP] hCaptcha Issue with Gravity Forms IntegrationHi @kaggdesign ,
We have disabled caching on the page, and the captcha now appears to work as expected on the first submission. While it is not invisible, this setup should be okay for now.
Thank you for your assistance—I really appreciate it!
Forum: Plugins
In reply to: [Relevanssi - A Better Search] Device-Specific Search ResultsHi @msaari , we tried the code you provided, and it seems to be working. Thank you so much for your help—I really appreciate it.
Hi @ckadenge ,
We reached out to Autoship QPilot regarding this issue, and they confirmed that Autoship Cloud enforces logic during WooCommerce checkout that requires any customer purchasing Autoship products to save their payment method at checkout.
They were able to replicate the issue where payment methods were not saved at checkout for new subscribers.
Since payment methods were previously saving as expected during checkout and account creation, their developers are reviewing the situation to determine if the change is due to something on Autoship’s side or Stripe’s.
That being said, this issue is not isolated to our case—it has been occurring since the last Stripe plugin update. We are still uncertain whether it can be resolved by Autoship or Stripe. If you could also take a look, we would greatly appreciate it.
Hi @ckadenge ,
In response to your previous question about account creation, we have checked the WooCommerce account settings and can confirm that account creation has been enabled: https://prnt.sc/52AvAaqMKJtc
When a new customer placed an order, the account was automatically created, and the order is visible under the customer’s account rather than as a guest checkout.
However, we are still seeing the “Missing Payment Information” notice on the order: https://prnt.sc/1zpLTVSqzc2I
The only update we can think of is the Stripe update from mid-September, which we followed, including the re-authentication process outlined here: https://woocommerce.com/document/stripe/admin-experience/updated-requirements-for-stripe-plugin-mid-2024/. There have been no issues with other orders, but this seems to affect subscriptions specifically.
We have enabled Stripe logging and haven’t found any errors in the logs. While we do have records of payment intents, when we checked the webhook delivery logs, we found that although the initial order was processed, the recurring order (which should be created in autoship) had no payment method saved: https://prnt.sc/3wU6gWoKmQ_P
Hi @ckadenge ,
We haven’t had any issues with subscriptions for new customers that we are aware of until recently, so we are unsure if this is a recurring problem. However, recent orders from new customers have triggered an error indicating invalid payment since no payment method was saved.We’ve been using Autoship Cloud powered by QPilot for subscription orders, and we are uncertain about how both Stripe and Autoship handle the saving of payment methods, especially for new customers.
Forum: Plugins
In reply to: [WooCommerce] Missing Order in WooCommerce DashboardHi @ckadenge
Upon further investigation, we discovered that the shop_quote post type was likely generated by the Zip plugin. However, it didn’t properly update orders when payments via zipmoney were cancelled. We confirmed that the payment went through Stripe instead. To temporarily resolve this, we manually adjusted the post_type in the database for the affected order, ensuring it displays correctly on the WooCommerce dashboard until zipmoney support addresses the issue.
Forum: Fixing WordPress
In reply to: Untitled posts automatically createdHi @ewamchoden
Gravity Forms does have functionality that allows form submissions to be automatically turned into posts. However, it’s important to note that the specific issue of untitled auto posts cannot be conclusively attributed to Gravity Forms without further investigation.
To determine if Gravity Forms is the cause of untitled auto posts, you can review the form settings and check if there is a post meta field. If such a field exists, there’s a significant chance that it could be the cause.
Another suggestion is to use the gform_disable_post_creation filter. By using this filter, you can disable the automatic creation of posts from form submissions. You can refer to the official documentation for Gravity Forms for more information: https://docs.gravityforms.com/gform_disable_post_creation/.
I hope that helps!Hi @sabeelmansoof , have you been able to resolve the issue with the select2 on Elementor popup? I am experiencing a similar problem and I am curious to know if you were able to find a solution. I have also tried overriding the z-index, but still have issue with select2 search/input field that comes with the dropdown. Can you share any actions you took to resolve this?
For additional info, each variation sku is unique.