-
Wordpress 7.0 updated automatically overnight and now this issue has appeared when I am trying to add a new container block for “Chicken” into —a pre-existing published post — the container blocks inside of the container blocks that are the columns inside of Grid block each inserted container block is adding 100s of pixels of space at the bottom of each Container block and there’s nothing in settings that “show this” so I’m calling it an artifact / byproduct of the WordPress 7.0 upgrade because this wasn’t happening yesterday in the prior version of WordPress.
And here is where things get even weirder — I created a brand new test post and stayed in draft mode and re-created my exact work flow and in this brand new post environment it didn’t happen so it appears to “infect” content created in the prior version of WordPress. This issue is specifically tied to the Container block. The Container block is a GenerateBlocks block and there is no scenario where I believe this is intentional. For my content I use container blocks and inside of what I call my “Master Container Block” I insert a “Grid Block” often the 3-column grid and within those three containers I add multiple container blocks stacked atop one another and I add generous top padding to each of these container blocks that contain one item I’m promoting for sale to create a well-spaced, staggered layout design. Here’s a URL to the live post where this problem surfaced so you can see the layout design/style I’m referring to.
I can record a full screen video to show you exactly what I’m describing here. Here’s the thing this post is published but it’s not finished and this problem/issue has surfaced immediately following the WordPress 7.0 overnight update/upgrade. I really need to get back to work on this post GET YOUR GRILL ON… and due to the issue I can’t. HELP, ASAP.
I am running GenerateBlock Pro Version 2.5.0
Michael
-
Here’s is the URL to the published post I am still working on where this issue surfaced in WP Editor and these GIANT spaces are appearing out front — not right now because I deleted this new garbage content because this is a business website not some random hobby blog, not a blog at all just built on WP.
https://www.luxe-edit.com/get-your-grill-on-bbq-grills-more/
-
Hi Michael,
We haven’t received any similar reports about this issue, so this appears to be a new case. We’ll need to rule out a few common possibilities first.
Could you try temporarily deactivating all plugins except GP Premium and GenerateBlocks to check whether this might be caused by a plugin conflict?
Let us know if the issue still exists when only GP Premium and GenerateBlocks are active, and we can troubleshoot further from there.
-
Your comment about me being the first to report this should surprise no one, WordPress 7.0 was just pushed out the same day (May 21) this issue surfaced — there’s always a first report and it’s from me.
This isn’t a plugin conflict — if it were caused by a plugin conflict, the issue would be widespread and affect all content. It doesn’t. It’s only affecting content created in the pre-7.0 version of WordPress. This is likely coming from WP Core 7.0, and for some reason it’s causing this very problematic issue. So, I reject the easy-way-out plugin conflict theory, and I’m not blowing up my website for that.
To isolate the issue further (as I stated in my support ticket), I created a brand-new WP 7.0 test post and reproduced my exact workflow there using the same GenerateBlocks structure and active plugin environment. The issue did not surface in the new post environment. The spacing issue only occurs when inserting brand-new Container blocks into content originally created in the pre-7.0 version of WordPress. That behavior strongly points to some kind of WP 7.0 compatibility/state issue tied to pre-7.0 post environments rather than a traditional plugin conflict.
Michael
luxe-edit.com -
. The spacing issue only occurs when inserting brand-new Container blocks into content originally created in the pre-7.0 version of WordPress.
I can not replicate the issue with my site (WP 7.0), where and how can I see the issue on your site?
And can you describe the spacing issue in more detail? Or a video record would help too.
-
The original affected post still exists in my WordPress editor and is set to redirect to a newly rebuilt version of the post so I could continue adding fresh content to it as the new WP 7.0 post environment doesn’t create the garbage spacing at the bottom of each container block. So, I can open the prior post that is set to re-direct to the new 7.0 version and while recording a full screen video replicate my workflow to see and share what happens. Me describing it to you has already been done and that’s not working so going that route again just wastes everyone’s time and frankly I lost an entire day yesterday to this throwing away more time on dead ends isn’t on the menu.
Let me know if you want to take the time to create the full screen video. Also, how will I share that video file with you?
Michael
-
You can upload your video to the media library and share the link with us.
But to investigate the issue, I need to see the issue first. So, where and how do I see the issue if you don’t want to describe the issue in detail?
-
Uploading this video to my WordPress media library is not an option — I’m running a public business website and anything uploaded there is immediately indexed by search engine crawlers. This would not be a one-day exposure especially since today is Saturday and the beginning of the Memorial Day long weekend — the file would sit publicly accessible in my media library for however long your team needs to review it, which could be days or longer. As I stated previously, the moment I confirmed the issue was appearing in my front-facing public content I deleted it. I will not publish anything to my live public business website under any circumstances for a support scenario.
Sharing via email is the appropriate path. Please provide an email address where I can send the video file directly.
To your second point — this issue was documented in detail in my opening support ticket so if you need to re-read it I refer you to my initial support ticket. A video is the next logical step forward, not a request to repeat what I’ve already written. If you need the video to investigate further, please provide a way to receive it that doesn’t involve my public business website.
Michael
-
You can send it to [email protected]. Please make sure to reference this forum topic so we can identify it easily.
While you’re at it, please also provide a temporary admin login to your site so we can directly debug the issue further.
Thanks.
-
Update: I conducted a controlled test this morning using the post Have a Seat, my most recent post created in the pre-7.0 WordPress environment. I replicated my exact workflow — inserting a new Container block at the bottom of the post, adding a Grid block, populating all three columns with additional Container blocks, and adding content. The issue with hundreds of pixels of unwanted, extra empty space at the bottom of the container blocks within the grid column container blocks did not surface.
As I noted in my opening ticket, this appears to be a WP Core 7.0 compatibility issue tied to specific conditions. The fact that it didn’t reproduce today doesn’t change what happened when it first surfaced — the timing was directly tied to the WP 7.0 update and the behavior was consistent and occurred repeatedly within the work session, which is why I was able to document it in detail. WordPress core updates are known to introduce inconsistent behavior across different site environments, which may explain why the issue did not surface in today’s controlled test.
I’m retaining the screen recording I made today. If the issue resurfaces I will record another full screen video and share with you immediately to [email protected]. If it would be useful for your investigation even though it shows normal behavior, I’m happy to send the full screen video I just recorded.
Michael
luxe-edit.com -
In WordPress 7.0, one of the changes introduced is that CSS added through the Customizer > Additional CSS section is now automatically enqueued inside the Block Editor as well.
This means that if you have frontend-only CSS added in the Customizer, those styles are now also being applied inside the editor. That could explain the spacing issues you’re seeing.
You may want to check the CSS in the Customizer and temporarily remove all custom CSS to test whether the spacing behavior still persists after that.
- You must be logged in to reply to this topic.