The site on WordPress 6.1 does not look the same as before

You have the following defined on line 336 of the file 6luor.css:

figure {
   margin: 0;
}

If you remove that it should solve the problem.

@mburridge, I didn’t find the 6luor.css file and removed it from the style.css file.
This solved the first problem, but not the second.

• This reply was modified 2 years, 4 months ago by Ярмолик Андрей.

In addition, the “+” now does not appear automatically in the editor and to insert a new block you have to constantly press “/”.

Are you able to access the Block Inserter via the blue + button in top left of the editor?

@mburridge, yes, I can, but when the “+” button appeared automatically, it was much more convenient.

Does the problem happen on another computer or in another browser?

@mburridge, I have one computer and one browser (Google Chrome). Before the update, this problem did not exist, and now it is on two of my sites.

If you’re on a Mac you should also have Safari, and if you’re on Windows you should also have Edge. Failing that try installing Firefox so you can see if the problem occurs in another browser.

The fact that it’s on two of your sites leads me to think it might be your browser. Other things to try might be to clear your browser cache and reboot your computer just to make sure it’s not a JavaScript runtime problem.

@mburridg, I have Windows. Checked in EDGE. There is a problem there too. I was cleaning the cache. It didn’t help. So the problem is definitely not in the browser, but in the WordPress update.

Hi, could you deactivate all the plugins on your site and see if the issue persists please.

@mburridge, Deactivated it. The problem persists.
P.S. This morning I posted a new post on one of the sites and everything worked, and then I updated WordPress and now it doesn’t work.

OK thanks, I created this issue. Please feel free to add further detail to it as you see fit.

BTW someone else has reported on the issue that if you click a little further to the right then the + button does appear. I can confirm this behaviour.

Hopefully this will work for you as a workaround until the bug is fixed.

@mburridge, yes, I’ve already read it. Thanks. I hope that the error will be corrected soon.