TodorChristov

@garrettzucker – what a great plan, indeed!

@nwwoman – thanks! Right now I am open to every sound alternative, so I’ll have ClassicPress on my radar. I expect Woo to make certain changes to their code and if so, probably it will be difficilt for CP to maintain compatibility with Woo. But who knows, we’ll see.

@designsimply – thanks for your sugestions. I hope Gutenberg team will take into consideration issues which I and others have raised.

@nwwoman – but what about WooCommerce? As far as I know, ClassicPress has no plans to support Woo.

• This reply was modified 6 years, 3 months ago by TodorChristov.

@designsimply, let me explain why I think paragraphs should not be separate blocks by quoting another user’s comment in WPTavern:

“We should be free to type our content and if and when we want to break that content we can press a key like currently happens with the Enter key. Which will start a new content block, thus giving us a spot to insert any fancy Gutenberg Blocks.

Having separate Paragraph blocks is overkill.”

Please, read this comment – https://wptavern.com/wordpress-5-0-targeted-for-december-6-prompting-widespread-outcry-ahead-of-wordcamp-us#comment-271977

The comment explains the problem and offers a logical solution. I just cannot say it better.

@designsimply, I think I found the Toolbar. But what is the link between the Toolbar and the Paragraph blocks?

I really do not need separate paragraph blocks for each paragraph. Probably I would be fine with a Text block in which various paragraphs could exist. This is how a service like MailChimp is proceeding with blocks, for example.

I can see there is also a Classic block in which I can put a lot of paragraphs, but as far as I know, Classic block must be used as a last resort and in the future it could be deprecated. After all, what is the reason to terminate the “old” Classic Editor and to use a Classic block instead? I see no logic.

When you type a text and hit Enter, a new paragraph block is created. This happens every time you hit Enter.

Hi, @susannelson!

The code you suggested did the job. Thank you!

Regards,

Todor

Sure, I will leave a review soon.

Thank you once again!

Todor

Hi Thomas,

No, everything is OK.

Thank you a lot for your quick support!!

Todor

Hi Thomas!

Our discussion forced me to check what exactly version of my child theme is in use. I found out that I use a bit older version. When I switched to the latest version of Metro theme the blue bar is not there. Instead there is a small circle with a pen. When clicking it I am directed to the banner settings in my admin panel. Probably this is how your latest feature works?

Probably it is a good idea to update to the latest version of my child theme. This way I will see the correct things on my front-end when logged-in.

Regards,

Todor

Hi Thomas!

My theme is a child theme based on Genesis Framework. In order to work, you’ll need a copy of Genesis framework as well. Do you have one?

Regards,

Todor

Thanks for your support, Thomas!

I use Metro theme from Genesis. And I am almost sure that in the past I somehow have deactivated the editing features because I have never used them. To me they cause distraction on my front-end, but thats just me, of course.

Due to my settings, probably the blue bar should be hidden in my installation as well but I see it. It is a thin short non-clicable vertical blue line. Nothing big, just saying.

Hi Thomas!

I didn’t realize it is a feature.

When I am a logged-in user, I do not see any Edit link, just a small blue bar which is NOT clickable because if I want to click it I must stop hovering on the banner and the bar disappears.

In my instalation of WordPress I don’t use (nor see, probably I have forbidden them) any editing features from the front-end. May be this explains why I don’t see your editing link either?

When logged-out I don’t see the bar.

Regards,

Todor

3 months later, the issue is resolved somehow. I don’t know how. ??

It may have something to do with Smooth Scrolling feature of Chrome. I deactivated it in my browser from here —> chrome://flags/ and the fixed widget is working pretty well now.

But… this is just a quick local fix, I suppose. If it is a Chrome bug then quite a lot of people could be affected by it.

• This reply was modified 6 years, 11 months ago by TodorChristov.