Bug overview description.
Thread in forum #166664 is FUBAR. Compare last post on https://e621.net/forum/show/166664?page=2
with forum #166947

What part(s) of the site page(s) are affected?
Last post(s) in forum #166664

What is the expected behavior?
Forum posts not lumped together

What actual behavior is given instead?
Lumped together posts (at least 11 of them)

Time of incident (if applicable).
N/A

Can you reproduce the bug every time?
Yes (as in it isn't temporary)

What steps did you take to replicate this bug?
N/A

Errors or other messages returned (if any).
N/A

It looks like it's something to do with forum #166947, perhaps with the section tag not ending properly or something. It won't let me use the respond button and it also eats up the report page

EDIT: Just verified myself, this is what happens if you don't include an end section tag.

EDIT2: removed section tag to restore the thread back to its proper layout

Whoa, now that looks really odd. It reminds me of the table DText glitch (ask parasprite), but that can't be because table DText entered e621 on a later date.

Hudson said:
Whoa, now that looks really odd. It reminds me of the table DText glitch (ask parasprite), but that can't be because table DText entered e621 on a later date.

What the heck it happened here o_o

This is really weird and ugly so I think I have to be a part of it.

Furrin_Gok said:
What the heck it happened here o_o

I guess we're being assimilated.

Thanks a lot, Tuvalu.

Will this be fixed if I add a /section? [/section]

let's see...

nope

Tuvalu said:
let's see...

nope

There is no escape

I'll, uh, stop shitposting now, guys. Been fun

Note to the devs: I fixed it for the time being by closing the section at the end of the post.

NotMeNotYou said:
Note to the devs: I fixed it for the time being by adding [/section] at the end of the post.

I'd better edit an unclosed section into all my past two-thousand forum posts before you fix it

Does this only affect the forum?

No idea, too lazy to investigate.

Fenrick said:
Does this only affect the forum?

It also affects blips and user info, and presumably anywhere else that uses dtext

NotMeNotYou said:
Note to the devs: I fixed it for the time being by adding [/section] at the end of the post.

If so, you only fixed half of it :P

It's now 6 posts messed up instead of 11, not that it matters, since it still needs a bug fix.

Chessax said:
If so, you only fixed half of it :P

It's now 6 posts messed up instead of 11, not that it matters, since it still needs a bug fix.

That's because Foxwhisper also didn't close their section.

Damn lazy people and their unclosed tags.

NotMeNotYou said:
That's because Foxwhisper also didn't close their section.

Damn lazy people and their unclosed tags.

My suggestion in forum #201812 might come in handy here if it will get implemented.

Bug confirmed, assigned internal bug ID #631.

It also happens with tables. At least it looks slightly better.

It can even happen with pools apparently: https://e621.net/pool/show/8574

For the devs, the method I use for parsing bbcode is hacky but it works:
openElements = []
For each opened element, push "elementname" into openElements
On close of a element, remove any one entry where "elementname" in openElement, if not there ignore it and don't put the actual html element.
At end of text, for each in openElements append openElement as html to processed text.

Proper method would be to yell at the user about unfinished bbcode and tell them to fix it. DText is close enough to bbcode that this method should work.

Another example located in the now closed forum #203410.

Chaser said:
For the devs, the method I use for parsing bbcode is hacky but it works:
openElements = []
For each opened element, push "elementname" into openElements
On close of a element, remove any one entry where "elementname" in openElement, if not there ignore it and don't put the actual html element.
At end of text, for each in openElements append openElement as html to processed text.

Proper method would be to yell at the user about unfinished bbcode and tell them to fix it. DText is close enough to bbcode that this method should work.

This is already in there, but it appears to have become broken with the latest DText changes. \o/

Fix submitted. Pending deploy.

There was also a regression with nested code/table/section/quote tags that should be fixed as part of the submitted fix.

I supposed this will be fixed once deployed but comments in post #749689 suffer same(?) issues.

Chessax said:
I supposed this will be fixed once deployed but comments in post #749689 suffer same(?) issues.

Correct, it's universal to anything involving DText. I'm aiming for tomorrow or Friday for deploy. Need to get testing in.

I typically like to get regression fixes out faster than this, but I've been really busy and my internet connection has been awful the past week.

I've pushed a canary out to e926. If anyone notices anything about this issue that is still broken over there, please post in this thread so it can be addressed.

KiraNoot said:
I've pushed a canary out to e926. If anyone notices anything about this issue that is still broken over there, please post in this thread so it can be addressed.

I can't manage to replicate any of the previous behaviour with either \

Tuvalu said:
I can't manage to replicate any of the previous behaviour with either \

or \

.
However, I did notice that \

[/tr]

Fixed on 2016-08-13 as part of release 1.1.1.