·
Added a discussion

Hi, not sure if I am posting this in the right place, whether its public or personal? However, here goes.

I am trying my best not to be insultive here by just asking:

Who's bright idea was it to not allow spaces between paragraphs.

Every time I press Enter, (and the same is happening here.) There's enough space to add another line. Resulting in no space between paragraphs. I am intentionally going to make this sentence long to see how big the space it. And now click the enter button.

And the massive space appears again. But what if I just want to start a new line after a short statement? It has a massive gap. So if I reduce the cpace between the lines so the text looks okay. There is then no spacing between paragraphs. So its currently impossible to make my lines correctly spaced?

The only top margin space is (apart from paragraphs) if I use headings.

Any ideas how to get myself out of this dillema?

I mean, if I start a new line like I just did, there's a massive space again. Space as if I had started a new paragraph.

Which is just too big.

And the script , although shows <br><br> in the code, does'nt honor them on the front end.

And when I eventually get users... I don't want to ask them, and they would do a runner if I did... to add line breaks between paragraphs. even if that was possible.

I mean, look at my post here. Its ridiculously spaced. Simply because I don't have the choice to add a line space?

Any ideas how to fix it. Thanks. I'm using the 14.0.1 version of Posts plugin.

Much appreciated. And apologies for the abrupt start to this post. Thanks

  • 192
  • 😆 1
Comments
    • Hello @Stephen Hawkins !

      The problem which you described meets to count the common way of the posting in the Web, where prefer to remove the empty space by any way. As the custom "hack" you may insert the line

      with the --- symbols between the paragraphs with the white font color and correct the margins in the CSS classes like .bx-def-vanilla-html p in cases when the space is too big.

      • It really is a frustration for some of my users. Some are poets and struggle to get the format right.

        I do not know whether it originates from the Quill plugin or UNA development, but it is these little things that cause some users to leave.

        At this stage, selecting all the text and changing the format to "Heading 5",
        kinda normalize the layout. (Like here).

        So, "Normal" is actually paragraph format, inserting the extra line.

        • Poets and song writers are definitely affected.

          How did you figure out the clever "Select All, Heading 5" trick? Amazing.

          I have an advanced text editor called BBEdit. Wonder if it can show the invisible characters and returns (line feeds) - then copy and paste to UNA. But this plan does the average site visitor/user no favors at all.

          Please keep us informed as to a solution.

          • I would suggest we rename the available formats in the meantime:

            "Normal" > "Paragraph"

            "Heading 6" > "Subtitle". This works nicely underneath photos as a description or for credits.

            "Heading 5" > "Normal"

            However, the problem remains — a large membership will not be able to figure this out for themselves.

            Playing around in the Quill "Playground" you will see that there is no issue there. 

            image_transcoder.php?o=sys_images_editor&h=3064&dpx=2&t=1776417551

            We really need the feature to be updated.

              • There is a similar formatting issue which also needs to find resolution.

                I notice it in my Files app (regarding PDF files). It is in the Description that the summary is jammed up without spaces. The Description shows up on the Files Index page. That is where is problem is - not on the page for the original File.

                Besides affecting readability - it gives the site an amateurish appearance.

                • This issue has been brought up several times, you may even find my comment on the matter, linking to an ISSUE logged in their (Quill's) GIT repo. Stating they are not ever going to fix this issue.

                  At this point, UNA devs just need to replace the editor.

                  • It is unfortunate that a few lines of code could be implemented to fix this issue across all apps. But it is not so simple as that.

                    Hopefully, our clever devs will rise to this challenge and address things in the days ahead.

                    Thank you again for your analysis and summary.

                    Login or Join to comment.