Container width differs between blog/news/category pages and I don’t know why.

Hello @rodario,

Thank you for using Neve and apologies for the delayed reply!

I have verified all three pages mentioned by you in the above comment but the container is set correctly on all of them. All of them have 100% width with the –container variable set to 1600px. Visually all I can see is that indeed the News and Blog pages have the content width set to 70% instead of 100% thus resulting in a difference when switching from “Hikes” page to one of these two.

You can set them all to the same width easier by adding the below code to the Additional CSS tab in the Customizer:

@media only screen and (min-width: 960px) {
 .nv-index-posts.blog.col {
    max-width: 100% !important;
}
}

After applying this code, you should see no difference when switching from one page to another.

Thank you and please let us know if this worked for you!

Hey @mateithemeisle thanks for the reply and don’t worry about the delay. You’re providing a much appreciated free (for me) service here.

I can confirm that this solution works as a workaround but it leaves open the question of why:

Why do category/hike and category/blog – both category pages the settings of which I have no control over – behave differently; one filling the container, one not?

Have a great day ??

Hello @rodario ,

Thank you for confirming that the solution worked!

Can you please make sure that you don’t have the content set up to 70% from the page options? Usually, we do this when we want to include a sidebar on that page.

To check this you can go to Edit page > Page Options and make sure Full Width is setup. (screenshot)

Also, please check Customizer > Layout > Content/Sideabar and make sure the same setting applies to all the pages. (Full Width 100%). (screenshot)

Thank you and please let us know how it went!

Hi @mateithemeisle

I can’t set the width for category pages. There is no “Edit Page” option for category pages.

Hello @rodario,

The category pages are dynamically generated and they inherit the width setup in Customizer from the Blog/Archive Sidebar width. (screenshot)

Please make sure that this setting is correctly in place and let us know if you are still facing the issue!

Thank you and we’ll await your response!

Hey @mateithemeisle

Yeah the width is set correctly.

But more importantly: They’re both category pages, so they both inherit the same settings, so they should both display the same – but they don’t.

I mean, that’s the whole point of the question. Why don’t they behave the same?

PS:

1. Please disregard the news page. I’ve only been talking about the blog and hike pages now.

2. You will not see the issue if you look at the pages now because I’ve implemented your CSS workaround. But if I remove that snippet, the pages go back to being different widths. And the question remains: Why?

Hello @rodario ,

Thank you for mentioning that you implemented the CSS and the issue is not observable anymore, otherwise it would have taken longer to see the correct situation!

As for what you mentioned earlier, you are right, since they are both category pages they should inherit the same settings, however, I couldn’t reproduce the error on my end so it is something tied to your specific environment (a plugin conflict, caching, etc).

Can you also check for the plugin conflicts and make sure to purge all cache (server,browser, plugins) and see if the error persists?

Thank you and have an amazing day!

Hi @mateithemeisle

Excuse the delay.

I’ve deactivated all plugins, cleared both server and browser cache, and the issue persists, unfortunately.

Have a great day ??

Hello @rodario ,

Thank you for your reply!

Since you have performed the above to no avail, there must be some setting in your environment that we are not able to catch and without looking inside the website to see exactly what is going on I couldn’t really respond to the previous question of “why are they behaving differently”. If it would have been an issue with the theme I should be able to replicate it too, but since this is not possible, I would advise you to update to the new theme version as it might help in solving the issue, or use the CSS provided above as it will have no significant impact on your website performance.

Thank you and have an amazing day!