Wide line separator not working
-
Hi, I’m having a strange issue. When I try to add a solid wide line separator block it just shows as a tiny dot in the editor, then not at all on the published page.
The dots and the default line styles work fine, but not the wide line. I already have wide lines on my site from before this bug started. I’ve tried duplicating those but it still produces the tiny dot.
Also, since this issue has begun my page has been laggier than usual. Not sure if that’s related.
Any ideas?
The blog I need help with is: (visible only to logged in users)
-
Update:
Looks like there’s some major issue with my site.As soon as I get on the editor I’m promted to save even though I haven’t changed anything. When I go to save it says I’ve made changes to post-meta-icons. And the select option is flashing on and off. At this point the editor is lagging a lot.
I’ve now deleted the post-meta-icons from my query loop which seemed to slightly improve the lagging. But now I can’t get them back because the option to add post-meta-icons is completely gone from the insert block options.
The line separator bug is still happening too.
Also, the editor lags and crashes a lot with this error:
o@https://s0.wp.com/_static/??-eJylkkGOwjAMRS9EakAdWCHO0iZW65LEJXYK3H7CFrFBXlq2nr6ePzxW5zkrZoU11omywFTbOGKZ2qYgbIe+23dHGCvFACRO5iFGfji81yEC5YDPLlHuFtnBr7gbvjwHFCNmLcSF9OXuFSsaYZ7TymKlFAz16QpXpWxlhUEHI2LWFF27JiWzbZm56PttRs4Y2d++hKHsY32XYhEIJAob5sAFEqfGtli0Jm49S83g9qHwmi6H0+m47/u/83n5B9KlM8Y=:23:3151
V/a<@https://s0.wp.com/_static/??-eJylkkGOwjAMRS9EakAdWCHO0iZW65LEJXYK3H7CFrFBXlq2nr6ePzxW5zkrZoU11omywFTbOGKZ2qYgbIe+23dHGCvFACRO5iFGfji81yEC5YDPLlHuFtnBr7gbvjwHFCNmLcSF9OXuFSsaYZ7TymKlFAz16QpXpWxlhUEHI2LWFF27JiWzbZm56PttRs4Y2d++hKHsY32XYhEIJAob5sAFEqfGtli0Jm49S83g9qHwmi6H0+m47/u/83n5B9KlM8Y=:23:84318
we/yr</<@https://s0.wp.com/wp-includes/js/dist/vendor/lodash.min.js?m=1653325678h&ver=4.17.19:9:25590
we/yr</<@https://s0.wp.com/wp-includes/js/dist/vendor/lodash.min.js?m=1653325678h&ver=4.17.19:9:25590
V@https://s0.wp.com/_static/??-eJylkkGOwjAMRS9EakAdWCHO0iZW65LEJXYK3H7CFrFBXlq2nr6ePzxW5zkrZoU11omywFTbOGKZ2qYgbIe+23dHGCvFACRO5iFGfji81yEC5YDPLlHuFtnBr7gbvjwHFCNmLcSF9OXuFSsaYZ7TymKlFAz16QpXpWxlhUEHI2LWFF27JiWzbZm56PttRs4Y2d++hKHsY32XYhEIJAob5sAFEqfGtli0Jm49S83g9qHwmi6H0+m47/u/83n5B9KlM8Y=:23:84474
ne/instantiate/p</<@https://s0.wp.com/_static/??-eJylkkGOwjAMRS9EakAdWCHO0iZW65LEJXYK3H7CFrFBXlq2nr6ePzxW5zkrZoU11omywFTbOGKZ2qYgbIe+23dHGCvFACRO5iFGfji81yEC5YDPLlHuFtnBr7gbvjwHFCNmLcSF9OXuFSsaYZ7TymKlFAz16QpXpWxlhUEHI2LWFF27JiWzbZm56PttRs4Y2d++hKHsY32XYhEIJAob5sAFEqfGtli0Jm49S83g9qHwmi6H0+m47/u/83n5B9KlM8Y=:17:14341
r@https://s0.wp.com/_static/??-eJylkkGOwjAMRS9EakAdWCHO0iZW65LEJXYK3H7CFrFBXlq2nr6ePzxW5zkrZoU11omywFTbOGKZ2qYgbIe+23dHGCvFACRO5iFGfji81yEC5YDPLlHuFtnBr7gbvjwHFCNmLcSF9OXuFSsaYZ7TymKlFAz16QpXpWxlhUEHI2LWFF27JiWzbZm56PttRs4Y2d++hKHsY32XYhEIJAob5sAFEqfGtli0Jm49S83g9qHwmi6H0+m47/u/83n5B9KlM8Y=:17:13979
la/r</<@https://s0.wp.com/_static/??-eJydUstywjAM/KE6AobHqdNzP8OxRRDYVirLIfx9HR4zdEp66FHa1Xq1Mpx74zgpJoVjBo8DOezH5pjfoEKUXCge84QdeED5vFKbSOlBsb4WE+44Rk7P0EO4D6WjlKErtWxRuooIwrBcN4tmBW2h4AE9qcmkCJQ8jv/W2bNEqyZQK1Yuv8WeV8oHFnXscY4QqytrJmssf3Ns8cQDeeRZnkMzEJ7ncIqdFbQZA7p6jK+Ccml+NF/GTtF2eLX4KrJYzCO1Kavaj73Vm+e5eO9Lj32oEwIZZfoUGS5ctLRYH52bnFxQ6owyh1M9560PvbCHNrA71YWrnKKYyJ725KwS10FPWeGqNmqxwSj1+b7OR3xfbrerxXq92e2O3yws/nM=:699:679
la/r<@https://s0.wp.com/_static/??-eJydUstywjAM/KE6AobHqdNzP8OxRRDYVirLIfx9HR4zdEp66FHa1Xq1Mpx74zgpJoVjBo8DOezH5pjfoEKUXCge84QdeED5vFKbSOlBsb4WE+44Rk7P0EO4D6WjlKErtWxRuooIwrBcN4tmBW2h4AE9qcmkCJQ8jv/W2bNEqyZQK1Yuv8WeV8oHFnXscY4QqytrJmssf3Ns8cQDeeRZnkMzEJ7ncIqdFbQZA7p6jK+Ccml+NF/GTtF2eLX4KrJYzCO1Kavaj73Vm+e5eO9Lj32oEwIZZfoUGS5ctLRYH52bnFxQ6owyh1M9560PvbCHNrA71YWrnKKYyJ725KwS10FPWeGqNmqxwSj1+b7OR3xfbrerxXq92e2O3yws/nM=:699:667
Ot@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:48159
t/e.useMemo@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react.min.js?m=1662044577h&ver=6.0.2:1:10748
la@https://s0.wp.com/_static/??-eJydUstywjAM/KE6AobHqdNzP8OxRRDYVirLIfx9HR4zdEp66FHa1Xq1Mpx74zgpJoVjBo8DOezH5pjfoEKUXCge84QdeED5vFKbSOlBsb4WE+44Rk7P0EO4D6WjlKErtWxRuooIwrBcN4tmBW2h4AE9qcmkCJQ8jv/W2bNEqyZQK1Yuv8WeV8oHFnXscY4QqytrJmssf3Ns8cQDeeRZnkMzEJ7ncIqdFbQZA7p6jK+Ccml+NF/GTtF2eLX4KrJYzCO1Kavaj73Vm+e5eO9Lj32oEwIZZfoUGS5ctLRYH52bnFxQ6owyh1M9560PvbCHNrA71YWrnKKYyJ725KwS10FPWeGqNmqxwSj1+b7OR3xfbrerxXq92e2O3yws/nM=:699:657
ft@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:43451
Wt@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:50270
ts@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:112276
Fr@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:77760
Dr@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:77688
Rr@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:77549
Nr@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:74544
n/Pn/<@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:30170
unstable_runWithPriority@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react.min.js?m=1662044577h&ver=6.0.2:1:7430
xn@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:29947
Pn@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:30117
Nn@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:30050
n/ua/<@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:116031
ua@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:116036
V@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:9145
n/Xe/<@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:22465
Xe@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:22470
ge@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:16379
me@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:15616
unstable_runWithPriority@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react.min.js?m=1662044577h&ver=6.0.2:1:7430
xn@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:29947
oa@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:115829
pe@https://s0.wp.com/wp-content/plugins/gutenberg-core/v14.0.2/build/vendors/react-dom.min.js?m=1662044577h&ver=6.0.2:1:15411Please help! My site was nearly ready for launch before this all happened.
-
Hi, just adding this relevant info from the other thread:
However, I have a new issue. When I try to add a solid wide line separator block it just shows as a tiny dot in the editor, then not at all on the published page.
The dots and the default line styles work fine, but not the wide line. I already have wide lines on my site from before this bug started. I’ve tried duplicating those but it still produces the tiny dot.
Also since this issue has begun my page has been laggier than usual. Not sure if that’s related.
You are welcome to edit the homepage. It’s not resolved on my end. Here’s a picture of what I’m seeing with the initial error (sorry for the photo of screen):
We’re taking a look. The error message you’ve shared seems to be catching the related files, but not showing the actual errors related with them, so can you get a screenshot of that as well?
-
I’m not getting the slowdowns you’re seeing. I was able to add a full width dynamic HR. Can you confirm you see that?
-
Hi I don’t see any change you’ve made. But I was able to add the full width dynamic HR myself. That worked fine.
I’ve found that the full width separator only works when in a group block with setting allow to use full width.Could you try this to see if you get the crash I’m getting: go to styles > blocks > search separator.
Mine crashes at this point.
Could you also try adding post-meta-icons to the index page outside of the query loop block? That doesn’t seem to be working on any page still.Thanks
-
Ooh, thanks. Yes I do see an error there. We’ll do some testing to see where best to report it.
In the meantime, can you scroll down to the separator and use its settings?
-
Great, thanks.
I can use the separator settings but wide line doesn’t work, as shown in that photo linked above.
Any update on post-meta-icons?
They’re still not appearing on the list of blocks when trying to add them to my posts.
And when I am able to insert them on other pages (works on index home page) they’re bugged, not showing any icons. -
Hello there!
Any update on post-meta-icons?
They’re still not appearing on the list of blocks when trying to add them to my posts.To check are you trying to add these to the individual posts? If yes, you would need to add these to the single post template instead which can be found here: https://godorhorseflies.wordpress.com/wp-admin/site-editor.php?postType=wp_template&postId=pub%2Fgeologist-yellow%2F%2Fsingle
I hope this helps.
-
-
-
Oh yes I forgot about that, sorry! That is a workaround that works.
Thanks both you for all your help -
Update:
Hello guys, sorry to add more problems but there is definitely still something buggy going on with post meta icons.
Here is a screen recording: https://www.veed.io/view/c24aff44-e62d-4cd5-8794-8c5f0750a439?sharingWidget=trueNotice extremely long load times, then prompt to save after not changing anything, then flashing select toggle. The editor is very laggy to the point of unusable at this point. I get a browser warning saying this page is slowing firefox down.
-
Oh wow, yeah that’s taking a minute! Same results in another browser? If not, does clearing the cache help?
https://wordpress.com/support/browser-issues/#clearing-your-browser-cacheFWIW, I copied your code for my test to see if I could duplicate what you’re seeing. No luck just yet, aside from the search issue you mentioned earlier.
-
Yeah exact same in Chrome. And clearing the cache hasn’t seemed to help either.
Oh right, interesting. I’ve figured out that the weird save prompt for the post meta icon template “change” only happens in my archive template page.
Also this now appears on my search page

Index page post meta icons are unchanged, however they now seem to be classed as a Row block. I didn’t make this change

-
Hello there,
The load times sure is curious. Can you tell me if you have any adblocking software (browser extensions…etc), or are using a VPN?
Also this now appears on my search page
https://i.ibb.co/kqSrxzb/Screenshot-2022-09-06-at-22-55-24.pngI’ve had a rummage around and it looks like this may be a bug when a group block is nested inside of another group block.
The blocks in the template part post-meta-icons: https://godorhorseflies.wordpress.com/wp-admin/site-editor.php?postType=wp_template_part&postId=pub%2Fgeologist-yellow%2F%2Fpost-meta-icons were grouped together and then they were added into another group by the time they were added into the Archive and search templates.
Ungrouping them solves this message.
I placed the elements in post-meta-icons into a row to keep everything together horizontally.
Index page post meta icons are unchanged, however they now seem to be classed as a Row block. I didn’t make this change
https://i.ibb.co/kH61r2d/Screenshot-2022-09-06-at-23-01-25.pngI noticed this when I had a look previously. This was something that we did not add.
I hope this all helps.
-
Hello there,
The load times sure is curious. Can you tell me if you have any adblocking software (browser extensions…etc), or are using a VPN?
Also this now appears on my search page
https://i.ibb.co/kqSrxzb/Screenshot-2022-09-06-at-22-55-24.pngI’ve had a rummage around and it looks like this may be a bug when a group block is nested inside of another group block.
The blocks in the template part post-meta-icons: https://godorhorseflies.wordpress.com/wp-admin/site-editor.php?postType=wp_template_part&postId=pub%2Fgeologist-yellow%2F%2Fpost-meta-icons were grouped together and then they were added into another group by the time they were added into the Archive and search templates.
Ungrouping them solves this message.
I placed the elements in post-meta-icons into a row to keep everything together horizontally.
Index page post meta icons are unchanged, however they now seem to be classed as a Row block. I didn’t make this change
https://i.ibb.co/kH61r2d/Screenshot-2022-09-06-at-23-01-25.pngI noticed this when I had a look previously. This was something that we did not add.
I hope this all helps.
-
Hey Aleone,
Thanks for rummaging.
No VPN, and the only extension I’m using is uBlock Origin. Disabling this hasn’t seemed to have done much.
I’m also still getting the error message even with your changes to the template part. But I’ve deleted the p-m-i block and copy/pasted the Row block from the index page (the one that has the p-m-i content but isn’t classed as a p-m-i block) to the Archive and Search pages. That seems to have solved this issue.
I found this related forum topic. It’s wordpress.org so I’m not sure how applicable it is but @MichaelApproved’s comment might be useful.
https://wordpress.org/support/topic/template-part-has-been-deleted-or-is-unavailable-error/
-
Hmm, that fix wouldn’t work, as you are using a block theme, so fooling WordPress into thinking it’s not would cause more problems.
We’ll keep digging into this though, sorry for the trouble!
-
Just noting we’ve got the style-search crash bug pinned down, and I think we’ve found a culprit and filed a report for that one.
What are your thoughts about splitting the other issues into different topics, just to keep this thread from getting too tangled? Plus if the topic titles match each of the issues you’re facing, maybe we’ll be able to find others who are facing the same things and be a bit closer to figuring out why this is happening.
-
Just noting we’ve got the style-search crash bug pinned down, and I think we’ve found a culprit and filed a report for that one.
Excellent!
What are your thoughts about splitting the other issues into different topics
That’s fine with me. Are you looking to create the topics or would you like me to?
- The topic ‘Wide line separator not working’ is closed to new replies.
