4 posts by 2 authors in: Forums > CMS Builder
Last Post: April 18   (RSS)

Hi rez,

You're correct - by default in the WYSIWYG editor <enter> creates a paragraph break, whereas <shift+enter> creates a line break. From what I can see, the CSS you're using there should remove the spacing from around the paragraph elements; it's possible that the stylesheet is cached, so the first thing I'd check is if clearing your cache makes a difference.

Another option is to alter the behaviour, which is possible through TinyMCE configuration: https://www.tiny.cloud/docs-3x/reference/configuration/Configuration3x@force_br_newlines/

The configuration options you'd want to add to your wysiwyg_custom.php file are:

    force_br_newlines : true,
    force_p_newlines : false,
    forced_root_block : '',

This will reverse the default, so that <enter> creates a line break and <shift+enter> creates a paragraph break. 

Let me know if this helps with the issue, or if you have any questions!


PHP Programmer

By rez - April 17 - edited: April 17

Thanks Daniel. I used your configuration and removed my css since Paragraphs are now Shit-Enter. I explained this to the client but I think she will just use Enter / line breaks every time.

I see that TinyMCE  suggests not to make this change and that Microsoft Word and others use Paragraph tags when you press enter. I'll have to check that out, I don't use Word much except when opening a customers file but it seems weird to me as well. I would expect one line when pressing enter and have always thought the default was strange.

Anyway, I think I'm good and my customer will probably get to this tomorrow and hopefully be happy. Thanks!

By daniel - April 18 - edited: April 18

Hey rez,

Glad that worked for you! The <enter> behaviour is definitely platform-specific, and while I think it used to be more uniform, there's now some variation: Word adds paragraphs, whereas Open Office and Google Docs use line breaks. One small thing I'll add about the implication of switching from paragraphs to line breaks specifically in a web context is that line breaks can't be styled. Using two line breaks to show paragraphs means that that space will always be an exact double space. Whereas <p> tags allow you to alter the spacing with CSS, which can be useful if a site is re-designed or changes typography in the future, as "double space" isn't always proportional between different fonts. I personally like to preserve this flexibility, though I can certainly understand that there are cases where it's easier to simply use the line breaks.


PHP Programmer