dev
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] complianz broken with JS configOh the error is:
“ReferenceError: complianz is not defined”.
This is the other similar post I can find, which is about CSS inline minification in W3TC rather than litespeed. https://ww.wp.xz.cn/support/topic/w3-cache-minify-issue/
We’ve excluded the plugin path from both CS/JS /wp-content/plugins/plugins/complianz-gdpr/
Forum: Plugins
In reply to: [LiteSpeed Cache] complianz broken with JS configHello,
Exclusion doesn’t resolve the issue as it causes the plugin to error, despite being excluded.
We’ve tested excluding the whole plugin path from all features yet it will breaks. Any ideas on how to get it working?
Kind Regards
Hello,
It seems both cloudflare browser check + WF captcha has resolved the issue for the moment.
We suspected a async JS loading of the captcha library was allowing it to be bypassed. Either way, its been resolved which is good news.
Appreciate the follow up.
Kind Regards
Forum: Plugins
In reply to: [WP Frontend Delete Account] Accounts not deletedHello,
Any update on this issue with multisite?
Kind Regards
Hello,
— About the migration patch fixed instance
The _customer_user is correctly matched with the right customer and POST ID in those tables.
I’ve checked 2 orders from the same customer and they’re both ok. However they’re still not able to see any of their order history.
Creating new orders is ok, just pre-migration ones.
Does WC require any other metadata or info for order history ? I’m not sure what is a miss.
The issue is customers pre-migration cannot see any of their order history. They seem ok from the WC admin and also DB side.
- This reply was modified 4 years, 3 months ago by dev.
Hello,
Theses sites are already live so cannot be re-migrated over. The source site did not have this issue at all.
There 2 woocommerce sites that we were migrating. Both of which are now completed and we need to fix these issues.
What needs to be updating code wise/cause of the issue ?
I’m unable to replicate it with a manually made new order however.
Update
We’ve had it confirmed with the multisite-patch run store as well. The order in WC order details shows the correct customer being assigned yet its not in their order history.
This order has come in after the patch was run. It seems like order history has just broken and not working.
This migration was done with the free one then patched.
So we’ve migrated another store with the latest pro version of the plugin. Customers cannot see the orders within their order history however they are assigned within the order details.
Has something been missed with the pro version or is there something else that needs aligning for it to appear in their account?
Just managed to run this on the site and it has worked, thanks again 🙂
Will be doing the future migrations soon with the latest version (inc fix) so should be resolved now.
Anymore issues and I’ll report back here.
Awesome ! Thank you again.
Hello,
Thanks for sending that over, however we’re not able to remigrate the stand-alone to subside.
We weren’t unaware that this bug was a two-way issue before migrating from stand-alone to multisite.
Could we get a multisite version of the patch plugin please? We can use the beta version for the upcoming migrations which is great but one store has already been migrated back.
Hello,
We’ve ended up migrating the standalone back to a multisite installation due to too many issues with the site.
Using prime mover export from standalone to subsite, we have the same issue.
Can we get a plugin to fix this for the reverse (E.G standalone > Multisite) instead of the Multisite > Subsite thats temp fixed via the plugin.
Awesome, thanks for all of your help.
I’ll feedback any other core issues when we do our next migration, otherwise will fix adhoc
Works perfectly !
[10-Feb-2022 11:33:58 UTC] NO MORE ORDERS TO PROCESSED.
[10-Feb-2022 11:33:58 UTC] DONE PROCESSING ALL WOOCOMMERCE ORDERS.
[10-Feb-2022 11:33:58 UTC] THERE ARE AROUND 1621 ORDERS PROCESSED.
[10-Feb-2022 11:33:58 UTC] DEACTIVATING HOTFIX PLUGIN SCRIPT…We’ve got more woocommerce stores to migrate. Are we ok to use this script as part of the restoration checks (original issue list? We can wait until fixed in the prime version depending on time frames etc.
Also, are there any recommends for the other issues we had? We’re going to trial these steps next:
1. Reactivating/deactivating all plugins
2. Remove/reinstall the core problematic issues
3. Reimport existing plugin configs for any missing configs or known issue ones
4. Clean re setup for the core problematic plugins