kit21
Forum Replies Created
-
Yes, I guess that could be the solution after I noticed images using relative path aren’t loading in the FSE editor and did a bit of googling.
- This reply was modified 7 months, 2 weeks ago by kit21.
Plugin version: 11.0.32. I tested again with the latest version and it’s still broken in FSE
PHP version: 8.2. This shouldn’t matter as it’s not a php issue.No related error message.
The block looks broken without any style applied
https://ibb.co/ypB27W1FSE render blocks inside an iframe with a src that is “blob:…”. I believe the root directory for relative path within an iframe is calculated based on the iframe src and this breaks some style related import of your plugin’s js
- This reply was modified 7 months, 3 weeks ago by kit21.
Thank you for your reply!
I was testing it locally and on a stage server with all other plugins disabled and tested the social login buttons in incognito mode simply by comparing the behaviour when Cocart is off or on.The social login plugin(https://woocommerce.com/products/woocommerce-social-login/) is configured to support Facebook and Google login but neither of them work and I guess all other social methods will also fail for the same issue.
When Cocart is on, clicking any social login button redirects to same page and show “Provider Authentication Error” above the login panel.
When Cocart is off, it will simply redirect me to the login panel of the respective provider(Google/ Facebook).
The screenshots I shared was me trying to understand what’s the different in state before the plugin throw an error inEndpoint.php
that prevent the plugin from working. What I found is that to avoid the error$session["config"]["config"]
has to be assigned values, but that value is missing when Cocart is enabled.
The site I originally tested was a old Themosis site. I thought it might be a conflicting with previous code, so I set up a new site using Root Sage with only WC, WC social login and Cocart, but the social login still fail with the same behaviour. I will try to setup a new WP site and try again.
Thank you for your help ??