Action summary is artificially truncated on history, contribs and RC
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	• bzimport
	Feb 29 2008, 7:30 PM

Description

Author: alexsm333

Description:
On history, contribs and RC pages, when action is move/block/protect,
MediaWiki displays this inside <span class=comment>:
"<action description>: <user summary>", e.g. "moved A to B: some explanation..."

For some reason this whole comment gets truncated to 255 bytes. If user summary itself was close to 255 bytes, then user summary gets truncated. As a result, one has to open the Logs to see the full summary.

The problem happens much more often on non-Latin alphabet projects, with 2 or more bytes per most used characters.

Solution: please do not truncate this comment field.

P.S. While adding this bug I could only select "1.12-svn", while Wikimedia projects already say "1.13alpha".

Version: 1.12.x
Severity: normal

Details

Reference: bz13200

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:04 PM

• bzimport added a project: MediaWiki-Special-pages.

• bzimport set Reference to bz13200.

• bzimport added a subscriber: Unknown Object (MLST).

• bzimport created this task.Feb 29 2008, 7:30 PM

The field is 255 bytes long.

Duping this to bug 4715 for increasing the lenght.

This bug has been marked as a duplicate of bug 4715 ***

alexsm333 wrote:

This bug is NOT about increasing the length of rev_comment database field.

It's about DISPLAYING rev_comment (already stored in Revision table): it is not displayed properly on certain pages.

You're thoroughly mistaken.

You mention that the "comment" as you call it is truncated on move/block/protect and that you need to go to [[Special:Log]] to see the full summary.

That is the flaw. The message in the log is NOT the same as what is in rev_comment.
rev_comment is the comment for the REVISION, the full message you are talking about is NOT rev_comment, it's log_comment and the reason that one has more info than the other is because they are two different messages.
log_comment is shorter because it's also paired with log_user and log_action. So rev_comment needs to include more text as part of the comment and therefore becomes longer and ends up truncated.

Therefore, your bug is directly caused by rev_comment's byte length, there is no truncating of comments other than what the database does.

Action summary is artificially truncated on history, contribs and RCClosed, ResolvedPublicActions

Description

Details

Event Timeline

Action summary is artificially truncated on history, contribs and RC
Closed, ResolvedPublic
Actions