Paragraphs and newlines are no longer possible

[phx]

Since some time the text formatting is completely broken! I can no longer start a new line, or even a new paragraph. The preview will automatically attach the new line directly to the previous one, without any space.

P

Even worse: this also affects Code sections! So you can no longer paste formatted code!

P

The only possibility to enforce a paragraph seems to be a code-section with at least one character in it (still doesn't help with real code).

P

This was already mentioned in some threads, but I'm not sure if the responsible people are aware of it. I'm also unsure if Windows is affected, but Unix definitely is, as I'm currently typing on an iBook running NetBSD. I remember in the past Windows had a formatting problem, which added additional newlines. Could this have been an attempt to fix it, but breaking formatting for all other systems as a result?

EDIT: Just confirmed: Windows is not affected! But now all other systems suffer...

[derSammler]

Could be that the forum software only accepts \r\n as a new line. Linux uses only \n.

Funny that this is still an issue in web software these days, as this is something every web developer should know for 20+ years.

[DisasterIncarna]

yeah firefox linux user here, lots of problems of late, hasnt always done these weird things and i havent changed browser/os so not sure what initiated the issue(s).

[TCD]

RCK posted the change to newline characters in this post: https://eab.abime.net/showpost.php?p...6&postcount=76
Hopefully the change can be refined so it works properly.

[DisasterIncarna]

Any idea what caused it in the first place? an update/change to vbulletin, something different on the new server or something?

[giantclam]

+1 here, debian12/firefox-esr ...just tried to create a long post (with images), and it went all horrorshow as described =/

[phx]

Originally Posted by DisasterIncarna

Any idea what caused it in the first place?

As TCD indicated, it is likely caused by the patch which RCK applied a few days ago.

Now things are much worse. Even Windows it affected, if you use "Preview Post". I had no problem to remove some newlines after preview, when using Windows, before. But this is plain horror!

[TCD]

I've asked RCK to have a look again.

[phx]

[phx]

I just found that a workaround is to edit the text after submitting it. Then add the missing newlines and save. Still quite annoying. The preview is completely broken.

[meynaf]

The workaround for me is to not use the wysywig editor at all.

Click on Switch editor mode button (the "A" on the top right) to disable it. You will see the formatting tags but everything will be as you want.

[phx]

This is test.

With a new paragraph.

        moveq   #42,d0
        rts

Works! Ok. This is indeed another workaround.

[jman]

I hope this will be fixed soon, it's quite annoying.

Thanks for suggesting a workaround.

Testing the workaround:

the quick brown fox
jumped over the lazy dog

[RCK]

Originally Posted by RCK

So I applied the fix for firefox
Firefox user should try to refresh EAB with CTRL+F5 and see if it's better now.

	// deal with newline characters
	if (is_browser('mozilla'))
	{
		$text = preg_replace('#(?<!<br>|<br />|\r)(\r\n|\n|\r)#', ' ', $text);
		$text = preg_replace('#<br>#', '', $text);
	}

So the fix seems worst than the original, so I'm rolling back to:

        // deal with newline characters
        if (is_browser('mozilla'))
        {
                $text = preg_replace('#(?<!<br>|<br />|\r)(\r\n|\n|\r)#', ' ', $text);
        }

I don't know how to fix that for every firefox of every OS
If someone have one idea of the correct preg_replace, tell me and I will try.

[phx]

Originally Posted by RCK

So the fix seems worst than the original, so I'm rolling back

Thanks!
Confirmed.

I don't know how to fix that for every firefox of every OS
If someone have one idea of the correct preg_replace, tell me and I will try.

I would just leave it as it is and wait for a Firefox fix.

[TCD]

While the 'fix' seemed to work fine for new posts, for quoting and editing it was pretty bad. So thank you for rolling it back