Plugin Author
wpsoul
(@wpsoul)
I will appreciate if you provide me link to page
Sure: https://bobdewebbouwer.com/test/blog/2022/08/03/test/. The breakpoints are:
Mobile
460
Tablet
768
Desktop
1024
Default Row Content Width
1200
The default row should show 4 columns, 1024 and below should have 3 columns, 768 should have 2 columns and 460 just 1 column.
Plugin Author
wpsoul
(@wpsoul)
Thank you. Issue is found and will be fixed in next update
Hi!
Is this problem corrected?
I have modified the default breakpoints, but it keeps applying the original ones at all times. I have cleared cache, reset the block where I want to see the changes applied and created a new block from scratch to see if this way it would take the new breakpoints, but there is no way.
Another question, if I have a Global Reusable CSS created and then I change the default breakpoints I guess that the Global Reusable CSS is not updated, is it so?
Thanks for your help!
-
This reply was modified 3 years, 3 months ago by
Xaifu.
Plugin Author
wpsoul
(@wpsoul)
Reusable css must be also updated before render. Please, send link on your page and provide screenshot of your breakpoint settings
Thank you for your quick response!
I am now checking it again, and I see that it is indeed applying the new breakpoints correctly. We consider it solved.
Regarding: Reusable css must be also updated before render.
Does that mean that yes, the breakpoints of a global reusable css are automatically updated every time I change the general breakpoints?
I have modified the code that was generated inside Global Reusable CSS to clean it up so that it only contains the values I need to keep. I understand that if I have modified it, it will not be automatically updated, right?
In any case, is it correct to modify Global Reusable CSS to “clean the code” or is it better not to touch that code?
Plugin Author
wpsoul
(@wpsoul)
Breakpoints are not updated in reusable styles, but latest update will modify breakpoints before they are rendered on frontend, so, they will be auto changed on fly (you don’t need to update them manually in code)
Although it is logical to define breakpoints at the beginning of the project and not to touch them later, it is good to know that Greenshift will offer this possibility in the next updates.
Please when will the breakpoints be fixed? (Same issues as previous posts).