Title: evanltd's Replies | WordPress.org --- # evanltd [ ](https://wordpress.org/support/users/evanltd/) * [Profile](https://wordpress.org/support/users/evanltd/) * [Topics Started](https://wordpress.org/support/users/evanltd/topics/) * [Replies Created](https://wordpress.org/support/users/evanltd/replies/) * [Reviews Written](https://wordpress.org/support/users/evanltd/reviews/) * [Topics Replied To](https://wordpress.org/support/users/evanltd/replied-to/) * [Engagements](https://wordpress.org/support/users/evanltd/engagements/) * [Favorites](https://wordpress.org/support/users/evanltd/favorites/) Search replies: ## Forum Replies Created Viewing 8 replies - 1 through 8 (of 8 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Email Templates Customizer and Designer for WordPress and WooCommerce] 1.5.9 Broke functionality with emails generated from other plugins](https://wordpress.org/support/topic/1-5-9-broke-functionality-with-emails-generated-from-other-plugins/) * Thread Starter [evanltd](https://wordpress.org/support/users/evanltd/) * (@evanltd) * [6 months, 1 week ago](https://wordpress.org/support/topic/1-5-9-broke-functionality-with-emails-generated-from-other-plugins/#post-18806558) * Yes, new update works thank you! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GenerateBlocks] Query Loop Block — Orderby Slug bug still not fixed](https://wordpress.org/support/topic/query-loop-block-orderby-slug-bug-still-not-fixed/) * Thread Starter [evanltd](https://wordpress.org/support/users/evanltd/) * (@evanltd) * [1 year, 5 months ago](https://wordpress.org/support/topic/query-loop-block-orderby-slug-bug-still-not-fixed/#post-18342386) * Thank you, I had no idea there even was a v2. Looking in the settings I see that I had “use only v1 blocks” enabled. I don’t recall ever turning that on, or even seeing that option before. Now that I turned it off, the toggle has disappeared entirely from the Settings. Weird. But thank you for pointing me in the right direction. I’m too far in to rebuild this site with v2, but will try it on the next one! * Also wanted to mention, at [https://generatepress.com/blocks/](https://generatepress.com/blocks/) it still refers to the block as “Query Loop” which added to my confusion here. * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Extended Post Status] Lots of trouble with it in latest WP/Gutenberg](https://wordpress.org/support/topic/lots-of-trouble-with-it-in-latest-wp-gutenberg/) * Thread Starter [evanltd](https://wordpress.org/support/users/evanltd/) * (@evanltd) * [1 year, 10 months ago](https://wordpress.org/support/topic/lots-of-trouble-with-it-in-latest-wp-gutenberg/#post-18049914) * Thanks for the reply! Indeed the plugin you suggested is working out for me and I appreciate your help! * Forum: [Developing with WordPress](https://wordpress.org/support/forum/wp-advanced/) In reply to: [What’s this new frontend CSS ouptut in 6.5?](https://wordpress.org/support/topic/whats-this-new-frontend-css-ouptut-in-6-5/) * Thread Starter [evanltd](https://wordpress.org/support/users/evanltd/) * (@evanltd) * [2 years, 4 months ago](https://wordpress.org/support/topic/whats-this-new-frontend-css-ouptut-in-6-5/#post-17563561) * Ok, with more research I’ve concluded that even though I actually love the Gutenberg editor itself, clearly this push toward “block themes” and “full site editing” is not for me. After nearly 20yrs of using WP as a CMS rather than a pagebuilder, writing custom PHP and CSS and enjoying the separation of content and design, it’s hard to wrap my head around how visually click-designing an entire website in the block editor would ever be faster, easier, less aggravating—or even possible given the amount of customization we put into our sites. * Guess I’m stuck being a dinosaur for now, which means not creating a theme.json, and disabling new features as they arrive. Here are two ways to disable the global inline css output. Both seem to work for me. I’m not sure which approach is more proper. * ```wp-block-code function remove_global_styles_and_svg_filters() { remove_action( 'wp_enqueue_scripts', 'wp_enqueue_global_styles' ); remove_action( 'wp_body_open', 'wp_global_styles_render_svg_filters' ); } add_action('init', 'remove_global_styles_and_svg_filters'); ``` * OR: * ```wp-block-code function remove_global_styles(){ wp_dequeue_style( 'global-styles' ); } add_action( 'wp_enqueue_scripts', 'remove_global_styles' ); ``` * Forum: [Developing with WordPress](https://wordpress.org/support/forum/wp-advanced/) In reply to: [What’s this new frontend CSS ouptut in 6.5?](https://wordpress.org/support/topic/whats-this-new-frontend-css-ouptut-in-6-5/) * Thread Starter [evanltd](https://wordpress.org/support/users/evanltd/) * (@evanltd) * [2 years, 4 months ago](https://wordpress.org/support/topic/whats-this-new-frontend-css-ouptut-in-6-5/#post-17563050) * Ok what a rabbit hole this is sending me down! Apparently I missed the boat when WP decided to remove the whole **__inner-container** div from block output…sorta…. sometimes. * I also missed the boat on **theme.json**. It appears if your theme does NOT include a **theme.json** file, WP will continue to output an inner container div inside blocks such as **group**. A legacy accommodation I guess? * If your theme DOES include a theme.json file, even if it’s totally blank inside, WP completely changes the html output/structure of blocks, to just a single div with no inner container. Wow. * Furthermore, if your theme.json includes the appropriate “**layout**” settings inside it, you then get a new pane in the block editor with a toggle switch **[ Inner blocks use content width**] that looks like it’s meant to replace the functionality of the removed inner container div. * Whatever legacy fallbacks they had in place prior to 6.5 were obviously working great for me, as I was blissfully unaware of these major block-related changes. * These fallbacks appear broken in 6.5. Currently I continue to have these “legacy” inner container divs output, but the CSS is now applied to them as if they were the newer simplified “solo” divs. * This is not easy to fix. All my custom theme CSS—across 20+ sites—is built to target the inner containers. * Forum: [Developing with WordPress](https://wordpress.org/support/forum/wp-advanced/) In reply to: [What’s this new frontend CSS ouptut in 6.5?](https://wordpress.org/support/topic/whats-this-new-frontend-css-ouptut-in-6-5/) * Thread Starter [evanltd](https://wordpress.org/support/users/evanltd/) * (@evanltd) * [2 years, 4 months ago](https://wordpress.org/support/topic/whats-this-new-frontend-css-ouptut-in-6-5/#post-17562480) * I dug around looking at some of my other sites, and apparently the global inline css output has had the !important flags for awhile now, at least going back to 6.2. I still maintain that this is really dumb to include !important in default core css, but it’s not the root cause of my problem. * The problem I’m seeing in 6.5 is that they changed where the “is-layout-constrained” class is applied. * Previously, it was on the main outer group div. So the CSS in question would then only apply to its immediate child, the inner container. No prob. * ```wp-block-code
``` * In 6.5 it has moved “is-layout-constrained” to the INNER container. * ```wp-block-code
``` * This means that this sloppy CSS rule **now applies to _every_ immediate child element inside a group’s inner container**: * ```wp-block-code body .is-layout-constrained > :where(:not(.alignleft):not(.alignright):not(.alignfull)) { ``` * So if I have a heading, an image, whatever, inside a group, it now is forced to have auto left/right margins !important. That’s really gross. - This reply was modified 2 years, 4 months ago by [evanltd](https://wordpress.org/support/users/evanltd/). - This reply was modified 2 years, 4 months ago by [evanltd](https://wordpress.org/support/users/evanltd/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simple Share Buttons Adder] Latest version 8.4.9 strips all “p” tags from classic editor post content](https://wordpress.org/support/topic/latest-version-8-4-9-strips-all-tags-from-classic-editor-post-content/) * Thread Starter [evanltd](https://wordpress.org/support/users/evanltd/) * (@evanltd) * [2 years, 8 months ago](https://wordpress.org/support/topic/latest-version-8-4-9-strips-all-tags-from-classic-editor-post-content/#post-17269312) * Yes, all looks good now! Thank you for the fix. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Media Credit] Disable frontend HTML output when fields are left empty](https://wordpress.org/support/topic/disable-frontend-html-output-when-fields-are-left-empty/) * Thread Starter [evanltd](https://wordpress.org/support/users/evanltd/) * (@evanltd) * [6 years, 7 months ago](https://wordpress.org/support/topic/disable-frontend-html-output-when-fields-are-left-empty/#post-12317955) * Awesome, thanks so much! And yes, I did have default credits disabled, using the block editor. Viewing 8 replies - 1 through 8 (of 8 total)