Cambabutonono

Hi, The below snipped works fine for main menu so far but I haven’t finished the project so not sure what still awats… ??

// SCSS
// adjust the mobile menu breakpoint

$breakpoint--global-header: 1300px;

@media (max-width: $breakpoint--global-header) {
	.wp-block-navigation__responsive-container-open:not(.always-shown) {
		display: flex !important;
	}
	.wp-block-navigation__responsive-container:not(.hidden-by-default):not(.is-menu-open) {
		display: none !important;
	}
}


@media (min-width: $breakpoint--global-header) {
	.wp-block-navigation__responsive-container-open:not(.always-shown) {
		display: none !important;
	}
	.wp-block-navigation__responsive-container:not(.hidden-by-default):not(.is-menu-open) {
		display: block !important;
		width: 100%;
		position: relative;
		z-index: auto;
		background-color: inherit;
	}
}

Thanks for sorting that out @eedee !

The link to the workaround posted by @doctorrockter worked in my case! Many thanks!
(delete?_transient_wp_core_block_css_files?in the?wp_options?table.)

Ok, I just create a new post in there and copy-paste Ig ?? not sure how to delete it from here tho.

Thanks for your response @macmanx Would you be able to provide an advice on how do I report it there? The topic appears to be closed for replies… cheers!

That workaround works! Removes both default inline css and the filters from the footer.

Not sure why all that garbage is included by default anyway, should be added by a theme imho.

I had a similar problem. Hummingbird adds a HTML comment at the beginning of document which I think causes the problems in e. g. Google Console.

For Yoast SEO plugin’s sitemaps I’ve added 2 entries
In Caching > Exclusions > Url strings

\/sitemap_index.xml
\/*sitemap.xml

note the escaped slash at the beginning of each string

Seems to resolve the problem.

After posting that I’ve downloaded the plugins and realised that this is more complex, so probably the classic editor plugin is the best bet.

• This reply was modified 5 years, 11 months ago by Cambabutonono. Reason: corrected grammar, expanded the post
• This reply was modified 5 years, 11 months ago by Cambabutonono.
• This reply was modified 5 years, 11 months ago by Cambabutonono. Reason: reconsidered the options

Hi there.

I’m very happy that the WordPress page & post edit screens are getting a new look however the website I am working on utilises a heavily modified classic editor that have been developed over many years. I simply don’t have enough dev power to change all the additional functionality to support a new editor therefore are forced to stick to the WordPress 4.x I guess.

I’ve noticed that the ‘classic’ editor is still used on all custom post types anyway, so I was wondering if there is a trick to bring it back to the post & page editing screens with a simple switch, without any additional plugins.

Many thanks