- This topic has 7 replies, 2 voices, and was last updated 2 years, 1 month ago by David.
April 16, 2019 at 12:21 am #870159FunkyCss
There seems to be a problem as i mention in facebook Elementor Comunity ,
When i updated in my two websites the beta of gpp is breaking the elementor woocomerce widget in the responsive .
In the mobile the products dont apear right .
You can find the issue in the front page , in a mobile view where are three products , ps this happend to a clone site when i updated Generatepress .GeneratePress 2.2.2GP Premium 1.7.8April 16, 2019 at 1:13 am #870183DavidStaffCustomer Support
can you check in Customizer > Layout > Woocommerce – what do you have the columns set to for Mobile?
If thats not the issue then can you flush and disable your cache so i can see where the CSS effecting it is coming from.April 16, 2019 at 1:27 am #870191FunkyCss
Hi David , i have set one column in the woocomerce layout in mobile , and i have disabled cache for now ,
And there seems to be an issue with Fastest Cache ….
Probably the new update of Elementor , or GP is not fully compatible with it . as i said before this site is live for 6 months and never had an issue and i have not changed anything . for sure is not issue of GP .April 16, 2019 at 1:59 am #870212DavidStaffCustomer SupportApril 16, 2019 at 2:08 am #870218FunkyCss
Hey David , i just re enabled caching and it looks to work fine , before i open the ticket and the facebook ticket i did that like a milion times . now it looks to work fine , i am not sure what was really wrong ,
GP With Elementor + Fastest Cache and autoptimize never had issues to mine sites , and this was not something crazy but i am just saying that is a good combo . Till now with the Beta versions of GP i have not found any bug .April 16, 2019 at 2:20 am #870224DavidStaffCustomer Support
Always best to flush the cache after an update. Sometimes as you have experienced it doesn’t always work and the cache needs disabling. Considering the amount of CSS elementor and Woo adds to a site i generally disable caches before updating.
Woo is exceptionally prone to issues when Caches combine/aggregate CSS. I would suggest only using one plugin to do this. Using Fastest Cache and Autoptimize may create issues of there own if they are both doing the same function.April 20, 2019 at 1:17 am #874037FunkyCss
David thank you so much for your wonderful suggestions and great lessons , i really apreciate that .
I am going to follow your advice , and i try day with day to be away from Builders and plugin caches and come closer to GP philosophy.
Thank you once again !
AndreasApril 20, 2019 at 7:48 am #874317
- You must be logged in to reply to this topic.