Last modified: 2008-03-02 09:42:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13200 - Action summary is artificially truncated on history, contribs and RC
Action summary is artificially truncated on history, contribs and RC
Status: RESOLVED DUPLICATE of bug 4715
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-02-29 19:30 UTC by AlexSm
Modified: 2008-03-02 09:42 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description AlexSm 2008-02-29 19:30:25 UTC
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".
Comment 1 Brion Vibber 2008-02-29 19:33:32 UTC
The field is 255 bytes long.
Comment 2 Brion Vibber 2008-02-29 19:37:31 UTC
Duping this to bug 4715 for increasing the lenght.

*** This bug has been marked as a duplicate of bug 4715 ***
Comment 3 AlexSm 2008-02-29 20:25:56 UTC
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.
Comment 4 Daniel Friesen 2008-03-02 09:42:16 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.