Archived topic
Full-width container
21 replies · Started by Vera on March 9, 2023
Hi Fernando,
paddin yes, but now full width isn’t.
The same is happening to my end this morning. I have paddings back but now there is no spacing between container and the elements above and below, and the second container is missing full width although the same CSS is applied to both containers. At least now we all see the same, so hopefully you can help me.
Thanks so much!
I can't see margins set for the Containers.
The second Container isn't set to align wide or align full.
Can you double-check these settings? If they are and they are not working, can you provide admin login credentials so we can take a closer look?
Please use the Private Information field for this: https://docs.generatepress.com/article/using-the-premium-support-forum/#private-information
Hi Fernando,
under Customize -> Additional CSS I have the following CSS code:
.gb-container.gb-container-a6c488ca, .gb-container.gb-container-28fed5b7, {
margin: 32px calc(50% - 50vw);
max-width: 100vw;
width: 100vw;
}
This should apply to both containers, as both IDs are listed.
Under Container Block in Block Editor, under spacing, I have padding set at 40 px all. I also have Use legacy enabled. What I don't understand why this has started happening without any intervention in the site. No updates, or any change that preceded the mess up.
I am waiting to see if cache plugin author maybe have a solution, and if not, I will grant you an access to the site.
Thank you!
You have an extra , at the end of your selector - .gb-container.gb-container-a6c488ca, .gb-container.gb-container-28fed5b7,.
It's causing a syntax error. Remove that first and see how it goes.
Thanks, Fernando! That's fixed now. That was my mistake. Now if we can find out how to the padding, it would be great!
Do you think that it makes sense to add padding within Additional CSS and to remove it from the block's spacing section?
Is it the one shared here by Ying?: https://generatepress.com/forums/topic/full-width-container/#post-2562171
Since I'm seeing that too from my end, it must be a caching issue. The best way to approach this is to address the caching.
If you're referring to something else, let us know.