Ingo Steinke (openmindculture)
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] Flamingo Spam ReportsHi @gondia123, the plugin is not ready for production yet!
DO NOT USE IT IN PRODUCTION!
But if you want to test, I uploaded a zip file at the (possibily broken) pre-release 1.1.2: https://github.com/openmindculture/wp-contact-form-inbox-report-mailer-plugin/releases/tag/1.1.2
Please see the open issues!
I did not manage to make WP_Cron send mails regularly yet on different testing sites, although some mails have been sent irregularly. If you want to contribute to the plugin, feel free to do so!
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Does not work for Block Checkout page?After the latest updates to WooCommerce, Germanized, and WooCommerce PayPal payments, are all PayPal payments now supposed to work with WooCommerce block checkout when using the latest plugin versions, including WooCommerce PayPal payments 2.5.4 ?
What’s the current status and planned updates for PayPal vaulting? If I understand the plugin’s changelog correctly, there has been some critical changes that have been rolled back concerning Vaulting? Fix – Can not refund order purchased with Vault v3 Card payment #1997. Does this mean the current plugin version uses PayPal Vault version 3 or not? Is the problem expected to be solved in the current release, WooCommerce PayPal Payments 2.5.4 ? Is there any additional action necessary or recommended to repair existing customers’ database entries or PayPal data?
Thanks!
Thanks so far!
Can the problem be caused by customers who do a single purchase with PayPal payment as guests without a shop customer account and who only create their shop customer account when using the same PayPal account to place a subscription order in the same shop later?
The above scenario is currently possible, as customers can buy as guests as long as they do not place subscription orders. This works well for users who use credit cards instead of PayPal.Does this plugin store a token or a corresponding reference or key in the shop’s database? Where can we verify if the shop part is working correctly?
Some further details from log files and order history:
Typically, the absence of a payment token is not caused by the plugin.
It looks like the customers do have a token on the PayPal server. Verified from both sides: the user can also see the active recurring payment in their PayPal account.
Log excerpt for problematic payments:
https://api-m.paypal.com/v2/checkout/orders
Request Body: {“intent”:”CAPTURE”,
…
{“user_action”:”CONTINUE”,”shipping_preference”:”GET_FROM_FILE”
…
“return_url”:”[…]?wc-ajax=ppc-return-url”
“payment_method”:{“payee_preferred”:”IMMEDIATE_PAYMENT_REQUIRED”}
Response: Array
(
[code] => 201
[message] => Created
)
…
POST https://api-m.paypal.com/v1/identity/generate-token
Response: Array
(
[code] => 200
[message] => OK
)vs. log excerpt when generating token for new customer:
POST https://api-m.paypal.com/v1/identity/generate-token
Response: Array
(
[code] => 200
[message] => OK
)
…
POST https://api-m.paypal.com/v1/notifications/verify-webhook-signature
Request Body: …
"event_type":"VAULT.PAYMENT-TOKEN.CREATED","summary":"A payment token has been created."The explicit token created event seems to be missing when existing customers place their orders and allow subscriptions, while it works when new customers place their order in a seemingly identical way.
When recurring payments fail, I can't find any explicit error in any log file, but WooCommerce order history shows:
"Payment failed. No payment tokens found for customer 8. Status der Bestellung von Zahlung ausstehend auf Fehlgeschlagen geändert."
(German text part translates to: order status changed from pending payment to failed.)
So what is the proper way to deal with "typically" and seemingly situation of the existing customers? Can we find additional logs or meta information somewhere else? Any other helpful ideas?
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedThis is still not working. I will follow-up researching more details when I find time. Helpful suggestions are appreciated, if anyone has been able to solve a similar problem.
- This reply was modified 4 months, 1 week ago by Ingo Steinke (openmindculture).
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedAs nobody seems to be able to help, I will test alternative solutions:
- switch caching plugins to verify if it is W3TC related or if the same problems occurs with WP Rocket or other alternatives,
- use an alternative to WP_Cron which seems like an unrealiable hack anyway.
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedI added a schedule on the second page, emptied the cache, and did the same after updating my plugin on the first site (open-mind-culture.org).yesterday. I haven’t received any scheduled mail from both sites since then.
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedI have installed the same plugin on another site which also uses W3 TC page cache now.
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedThe situation is getting even more erratic.
I didn’t touch any settings and didn’t explicitly clear the cache; WP core and W3TC is still the same since my last comment. But since tonight 3:05 a.m. I receive scheduled report mails again. Despite the expected hourly schedule, probably due to low traffic page visitors, these are the successful callback times so far:
02:53
03:05
04:12
04:16
05:04
05:19
05:53
06:06
06:55
07:05
07:50
08:07
08:56
09:06
09:55
09:56
10:02
10:04Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedNo more cron since I activated page cache.
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedI will reenable page cache now and see if it occurs again.
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedCan’t reproduce the issue anymore. About 1 day after WordPress core update to 6.3.2 cron suddenly worked as expected without any settings changed.
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedCaching changed: 20231012-1944 Page cache disabled, frontend minify disabled, object cache stays enabled, browser cache stays enabled
- This reply was modified 6 months, 2 weeks ago by Ingo Steinke (openmindculture).
Forum: Plugins
In reply to: [W3 Total Cache] WP Cron Callbacks not executedyou mean enable object cache but disable page cache?
I will try and tell you.
- This reply was modified 6 months, 2 weeks ago by Ingo Steinke (openmindculture).