Post title missing in recent posts list (specific user/browser?)

[Aleksi "Lex" Kilpinen]

Just tested, If I quote a post by Dude111 the topic of my post is just Re:
as it should be, since SMF takes the topic from the post you quote, and adds a Re: in front of it.

[Adish - (F.L.A.M.E.R)]

I'll move this to Bug Reports. Was it replicated by any chance?

[Dharshan]

I'll move this to Bug Reports. Was it replicated by any chance?

yes. chk my first post (the screen shot there)

it was replicated again (the second screen shot 13th post)

[Aleksi "Lex" Kilpinen]

I'll move this to Bug Reports. Was it replicated by any chance?

Haven't had luck replicating this, so so far it seems Dude111 is the only one that got this to happen.

[Adish - (F.L.A.M.E.R)]

I'll move this to Bug Reports. Was it replicated by any chance?

yes. chk my first post (the screen shot there)

it was replicated again (the second screen shot 13th post)

Having "Re:" is a different thing than what Dude111 did. Compare both the screen shots.

I'll move this to Bug Reports. Was it replicated by any chance?

Haven't had luck replicating this, so so far it seems Dude111 is the only one that got this to happen.

He broke SMF if we were able to replicate this, I would consider this as a major bug.

[Aleksi "Lex" Kilpinen]

I still haven't had a chance to try the actual setup of 98SE + IE6 + whatever the addon mentioned was, but somehow I doubt it would make a difference - isn't the check for content done on server level though? Not on the client side?

[Kindred]

BTW: I changed the title of this thread to be something descriptive.

[Arantor]

What has happened is that the subject has at some point been replaced with a space encoded as a numeric entity ( )

IIRC this would not be caught by the check made in Post.php against the subject being empty since the trim() operation would not be done on entities. I can't remember what processing is done prior to that trim(), though, as there is a htmlspecialchars() or $smcFunc['htmlspecialchars'] call. I don't have access to the source right now to view, but the order of operations, and the details of them, may be important.

[emanuele]

I cannot post any more without a subject and if entities are used they are not converted to the respective character, but are posted as a code...but I found another thing: an inconsistency between the post page and the quick reply.

If an entity (e.g. "& #160;" without the space) is posted from the quick reply it is converted to the corresponding char (a space in this case), while if the entity is posted from the post page the entity is converted to & #38;#160; (i.e. &+#160;).

The result is: posting & #160; from the quick reply in display you will see an "empty" post (it contains only a space), while posting & #160; from the post page in display you will see & #160;

I'm not sure if it makes sense...

[Illori]

is this still an issue?

[Joker™]

If an entity (e.g. "& #160;" without the space) is posted from the quick reply it is converted to the corresponding char (a space in this case), while if the entity is posted from the post page the entity is converted to & #38;#160; (i.e. &+#160;).

The result is: posting & #160; from the quick reply in display you will see an "empty" post (it contains only a space), while posting & #160; from the post page in display you will see & #160;

Umm not able to reproduce this anymore. The data sent in the database "& #160;".

[emanuele]

Is this still true?

As you can see from this post: more or less.

Okay, this is related to this: http://www.simplemachines.org/community/index.php?topic=484030.0

And of course, since it depends on javascript, if js is disabled it's still possible to post entities that are converted to the relative char and so post a virtually empty subject.

* emanuele feels that move the replacement to php is the way to go, but will wait for objections.