Page layout container width has narrowed since upgrading to WP 6.2

If you want to override the max-width of the page layout container, you can add custom CSS to your WordPress site. Here’s how to do it:

1. Go to your WordPress dashboard and navigate to Appearance > Customize.
2. In the Customizer, click on Additional CSS.
3. Add the following code to the Additional CSS box:

.is-layout-constrained > :where(:not(.alignleft):not(.alignright):not(.alignfull)) {
   max-width: none !important;
}

4. Click Publish to save the changes.

This CSS code sets the max-width of the page layout container to none, which effectively removes the constraint on the container width. You can adjust the max-width value as needed to achieve the desired width for your page layout container.

There is no Customize under Appearance since upgrading to WordPress 6.2.

try a link like this to get to customize area / additional css area:

examplesite.com/wp-admin/customize.php

Thanks

That worked, but unsure why Customize is hidden by default.

In Customize there is now, but most of the theme’s customize options have disappeared, including the option to set the header logo, header type etcc..

@farhansrambiyan,

My editor is also using only ContentWidth size after upgrading. I tried to follow your instructions but I don’t have “Customize” under “Appearance.” I just have Themes and Editor. Adding that code to styles.css did nothing, but I don’t think that file affects the editor (unfortunately).

Before WP 6.2, the site was able to run without an index.php file in the parent and child theme.

Not so after upgrading to WP 6.2.

Copying index-classic.php to index.php in the parent theme resolved all issues.

I was able to finally copy the css proposed by @farhansrambiyan but it just blows everything apart. My client side is fine, but the editor does not recognize the wideSize in my theme.json and makes everything the contentSzie:

"layout": {
    "contentSize": "680px",
    "wideSize": "1100px"

@srd75,

Where do you find index-classic.php? And does it fix the issue without the CSS proposed by @farhansrambiyan?

@highgatecreative index-classic.php is specific to the theme the site was using and probably doesn’t exist in your theme.

The CSS issue proposed by @farhansrambiyan was no longer relevant, as the proper the action I took allowed the proper theme to become active again (Twenty Twenty Three) had taken over before the rename took place.