Dave Loodts
Forum Replies Created
-
Yes, Version 2.23.6
Hi Michel, good insight looking at the raw xml strange. Mmm strange.
It only happens indeed with the auto mode. Not on the manual regenerate.
But then again: it happens not always. I have 4 feeds of 3 products. This morning only one was “corrupt”.I use your plugin on a lot of shops, also the premium plugin. I have not seen this issue before. But this shop is also hosted on another server (not mine or in my control) and with other caching plugins then i’m used too. I’m thinking it should have something to do with caching. There are 2 plugins: Litespeed and Super Page Cache (for Cloudflare).
So, i’m going to do some more tests. I keep you informed.I can confirm the mails are not being sent anymore. Thanks!
It seems the mail continues after the update. I have planned a re-check this thursday; i’ll keep you informed.
Forum: Plugins
In reply to: [Jotform - AI Chatbot] (E425). r.find is not a functionHuh, trying to test it again today and it seems like the AI chat is working now…. strange.
Forum: Plugins
In reply to: [Jotform - AI Chatbot] (E425). r.find is not a functionI don’t want to share the link to the staging site here publically.
Can i sent it via an e-mailadres or your own ticket center?Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] Ideal / Wero logo results in a 404Okay, so you agree it’s a performance issue and a valid concern.
Great! We agree.But your defence is: branding updates.
Tell me: how many times does this happens? Monthly, quarterly, yearly?
It’s not happening that often, right. It’s easy to follow it via updates, right.This get-the-logo-via-api thing also breaks the images in the backend, in the Mollie settings page the ideal logo is not loading…. that is what you get with this approach.
Hi Michel,
Auto feed fix is switched off.
All these options are switched off: Disable background processing, Feed process logger, Show product identifiers, Omit price filters,Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] Ideal / Wero logo results in a 404From a performance point of view, i doesn’t make no sense to download external images.
This should be out of the box an image from the website server in the first place.The rule of ww.wp.xz.cn is not the mix multiple questions in 1 ticket. My fault. So, i created a new ticket here: https://ww.wp.xz.cn/support/topic/custom-segmentation/
Hi, i can confirm it is now solved.
I got a question and a remark.
The remark: Omnisends adds the newsletter-signup on the woocommerce checkout hook: woocommerce_after_checkout_billing_form. Not really the best place for sign-up conversion, and out of the box there’s no option to change it. Would be better to use this hook: woocommerce_review_order_before_submit
Visual sheet: https://www.businessbloomer.com/woocommerce-visual-hook-guide-checkout-page/
The question: what path can we take to detect B2B vs B2C users; and different languages (in this case: NL and FR).This is the brand ID: 69bc2bb79b31272ae542023e
Hi, we have the same problem.
Start page inside WordPress admins stays the same, just like the “fix it now” button in Omnisend.During initial activation, these things are done:
- rest api user is created
- contacts seems to be synched to omnisend
- also some sales numbers are synched
In the troubleshooting guide there’s mention of getting to yourdomain.com/wp-json/wc/v3/products.
But that should not be public, right. It should be connected via the created rest api user.
Hope this is fix soon. I build shops and it’s the first time i advices omnisend to this shop: http://www.maisonmoie.com, but it’s rather bizar to see that it’s connection is not so fluently.
By the way: no wordfence, https okay, cron job okay;I’m going to test it on staging next week. I’ll keep you informed.
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] 3 months of PHP errors: ‘inpsyde-blocks’Waw, that is still on month to go…. so +4 months with these errors… I’m 20 years in WordPress business, i never saw plugin builders delaying these kinds of issues and just launch a fix release… which is the obvious thing to do, as it took already 3 months.