Spectra 2.12.9 and 2.13.0 break full width container layout
-
Fixed by rolling back to 2.12.8. THe latest versions cause full width containers to break. See screenshot:
Spectra bugs
- This topic was modified 5 months, 4 weeks ago by delanthear.
-
It looks like that if you make change in the customiser it DOESN’T affect the preview, I.e. you still get the huge amount of white space which makes it look broken. If you save it, then clear caches it DOES work.
HOWEVER this is a TERRIBLE piece of dev by Brainstorm Force. I’ve LOADS of websites which are built with Astra Pro and Spectra which are using NEW container blocks, which are all broken by default, requiring me to log into each of them and change a setting. They aren’t using legacy blocks.
You really need to think more about the impact on your users when you make changes like this and give us a way to avoid touching all our previous work again after a plugin update.
ALSO
These settings are breaking margins on group blocks as well. See this image: https://imgur.com/a/9VDkGXX When left on legacy the margin on the group block is correct, when I change this to COMFORTABLE, all the top and bottom margin disappears on the block causing this issue. It seems a 4em top and bottom margin which is set in astra-theme-css-inline-css disappears.
Not only to I need to go and change this setting on all our sites, i also need to check the values on almost every group block used.
- This reply was modified 5 months, 2 weeks ago by delanthear.
This has also completely ruined one of our sites. H2s seem to be picking up incorrect margin sites now which were fine before.
View post on imgur.com
See this. Changing from the “legacy” option is applying a left margin to the h2s, via
.entry-content[ast-blocks-layout] > * {
max-width: var(--wp--custom--ast-content-width-size);
margin-left: auto;
margin-right: auto;
}and –wp–custom–ast-content-width-size: 910px;.
The container layout is set to normal.
The whole site is messed up following this change. Rolling back to 2.12.8 fixes it.
Same on this site. Again, the h2 is having an automargin applied on the wrong content width value: https://imgur.com/a/RCVF2Cc
EDIT: Checked on the third site and initially I didn’t se the same problem, but then I realised that that is because the H2 is inside a Container. If it’s just on its own and outside any container, it is affected by the wrong page width.
- This reply was modified 5 months, 2 weeks ago by delanthear.
Hi @delanthear,
I completely understand your frustration, and I want to assure you that resolving this issue is our top priority.
I apologize for any inconvenience this has caused you, and I want to thank you for your patience and understanding as we work on a solution. We are currently preparing a hotfix, and we plan to roll it out at the start of the week to ensure this issue is addressed promptly.
If you have any further concerns or questions, please don’t hesitate to reach out.
Have a nice day!
Hi All,
We have released the updated version of Spectra with the fix today, please check and let us know if you are still facing the issue.
Have a nice day!
Hi. The new version has resolved the issue with the left hand margin when in legacy block editor mode.
However, if I change to “comfortable” it it is still applying incorrect left and right padding to headings that aren’t in containers, as per https://www.ads-software.com/support/topic/spectra-2-19-9-and-2-13-0-break-full-width-container-layout/page/2/#post-17743763
Hi @delanthear,
Sorry for the inconvenience caused to you.
Please ensure that you have cleared all the caches including the server-side cache. If you are still facing the issue, can you please share the issue URL so that I can investigate the issue further and assist you?
Looking forward to hearing from you.
Have a nice day!
Exactly the same as logged on the ticket and on the previous message. The H2s have spurious margins on, as if they are being worked ou tfrom a smaller page size then they should do. when you aren’t on legacy block spacing. Caches have been cleared any caching plugins disabed. See screenshot.
more broken spectra
Check your ticket 200752 for the site and access.
Hi @delanthear,
Sorry for the inconvenience caused to you.
We have replicated the issue and added the task with the high priority to the tasks list. We will release an updated version of the plugin with the fix as soon as it is done.
Have a nice day!
Good morning,
We can’t really say that a version regression deserves to give the status “Resolved” to this malfunction.
Has anyone found a workaround as the repair takes a while to come.
At worst, tell us the code and the css file to modify.
Thanks in advance,
BPH30Hi @bph30,
Sorry for the inconvenience caused to you.
We have fixed the reported issues. If you are still facing the issue, please open a support ticket from here:https://wpspectra.com/support/ so that the support dev can check further and assist you.
Have a nice day!
- You must be logged in to reply to this topic.