-
I’m experiencing an issue with the Site Footer element. I created a Site Footer, applied it to the entire site, but the display is inconsistent between the homepage and the other pages.
Specifically, the Grid section in the Site Footer has different CSS applied. On the homepage, the Grid is styled with CSS from a separate CSS file, while on the other pages the exact same element (same class) is styled with inline CSS. I’ve attached two screenshots below for reference.
Please note: I did not make any custom CSS changes to this Grid. Everything is within the same Site Footer element, and this behavior occurs consistently across different viewports; and No caching plugin on my site.
-
Hi there,
Could you please share the link to your site so we can check the footer directly?
That will help us understand why the Grid CSS is being applied differently on the homepage compared to other pages.
-
Updated links
-
Hi there,
I just checked the 2 links, the site footer look the same.
Have you fixed it already?
-
Hi Ying!
Not fixed. I just update 2 screenshot links. Please check again, thanks!
(on Desktop, please!) -
Hi there
The difference is that on the homepage your Grid containers are sitting side-by-side, while on the inner pages they are stacking. The element itself is the same, but the CSS for the Grid isn’t being applied consistently.
Please try:
- Go to Dashboard → GenerateBlocks → Settings → Regenerate CSS files.
- Clear any server/CDN cache.
- Recheck the homepage vs. other pages in a private window.
-
Hi there,
the issue is a CSS Class conflict.
Each GenerateBlocks is given a unique class for the local block CSS to be written to.
However when you copy a block from one post to another , such as from the home page to a GP element. Then the classes do not get updated and you have a conflict.This is whats happening on your home page, as you have the same grid layout below the hero and in the footer.
To break this conflict.
Edit the footer element and duplicate the blocks and delete the original.
This will generate new classes.
You may need to adjust the the grid layout column.
Then save the element. -
This is exactly the cause. I’ve actually come across it several times before on other projects, but since it didn’t seem to affect the design much, I didn’t dig deeper. I hope GB can fully address this issue in future releases.
Fixed!
Thanks so much, David! and Chaz & Ying, too! -
Glad to be of help!
- You must be logged in to reply to this topic.