Archived topic
Posts/Blog Page in one row when should be in two?
11 replies · Started by William on June 30, 2022
Hi there,
I was checking this page, which is my default posts page, and notice that there are two things that are going wrong with it.
- The excerpt is showing
- The posts should be in two columns, not one
I have made in the customizer options of GP to remove the excerpt to 0 words/characters and have made sure to choose to have the posts show in two columns, so I am a little unclear why this is happening?
Kind regards,
Will
Hi William,
Can you try clearing all caching mechanisms set in your website?
If that doesn’t work, as a second course of debugging, can you try #1 here?: https://docs.generatepress.com/article/debugging-tips/
It would be good to take a backup of your site before doing so. Start with caching/optimization plugins.
Kindly let us know how it goes.
I've checked caches and it is not a cache issue and have also disabled plugins to check as well. It's weird as if I make it a mansonry, it goes to two columns as intended. How can this be fixed?
Without the issue persists:
Hi there,
can you disable ALL optimization plugins you're using? So i can take a closer look.
Hi David/Fernando,
I feel a plonker...it was CSS that was causing the issue. All fixed, thank you very much for your help.
With that, I guess the best thing for location specific CSS is to include it in a GP element?
Many thanks,
With that, I guess the best thing for location specific CSS is to include it in a GP element?
I wouldn't recommend that. CSS should be added in Additional CSS field in the customizer.
You can make your CSS to target specific pages only.
Gotcha - but the way above does mean the CSS would be loaded on pages/posts where the CSS is not applied though?
My thoughts to have it in a GP element is to only load the code that is applicable for that page's styling, not anywhere else (to save on load speed etc.)?
How much CSS was it ?
About 30-50 lines usually - I do have around 4-6 elements that have CSS code on each for them as a <style>
If you're happy adding the <style> tag in the element then continue to do so.
Its not a problem.
If you're using a Caching plugin that optimizes CSS they will generally scrape them inline styles and move them to the head anyway.
That makes sense. I guess if using the likes of WP Rocket with Remove Unused CSS functionality too, it might make more sense to stick it in the Additional CSS area - thanks as always.
You're welcome
