This topic has 6 replies, 2 voices, and was last updated 4 years, 2 months ago ago by Olga Barlow
Hi
I’ve noticed a strange conflict when I use the WPBakery backend editor. I have inserted the Product slider widget using Custom Grid without Lazy Lazy loading.
With the Custom Grid and no lazy loading the problem is: Single Image and Custom Heading widgets have their anchor tags / links stripped. Also the WPBakery Button shortcode text is printed to the page instead of being rendered as a button.
However, if I use the Product widget using Product Content Effect set to ‘Inherit’ OR with lazy loading, then the abovementioned widgets are rendered correctly.
I have cleared my cache. I have ensured the Smush plugin doesn’t have the lazy load feature enabled. I’m relying on XStore’s lazy load feature.
I have set up the staging home page so you can easily enable/disable the row with the product slider using the Custom Grid. Notice how when the row is disabled, all widgets behave as expected.
As you can see on the staging home page, I have been able to create the content using Text boxes – so this isn’t urgent.
Thanks.
Hello,
Yes, you are right. A strange bug but it really exists. I have passed your request to our developers. I’ll inform you once they fix the issue.
Regards
Ok – I’ll leave this open until you get back to me then. Strange that it only happens when lazy load is unticked and only the custom grid content.
Do you need the the staging site page with those widgets to look at the problem any more? I need to change the staging home page back to a ‘normal’ page without those message boxes and duplicate content. Just let me know when you’re done with it please 😉
I take my hat off to you and your developers. It such a good theme – mind blowing how many moving parts there are!
Hello,
We were able to replicate the mentioned issue on our test installations. Our developers will continue their work there. In this case, wait for the next theme updates when we fix the bug.
Till this happened use our button element instead of the default one.
Regards
Hi again
I’ve recently updated to XStore 6.3.7. Doesn’t look like this fix was included in the update. Do you happen to know when this might be fixed please?
Thanks!
Hello,
Unfortunately, we have not found a solution yet. Still working on it. Take our apologies for this inconvenience.
Regards
You must be logged in to reply to this topic.Log in/Sign up