Last modified: 2012-07-24 13:50:23 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 25159 - $1 not filled into message MediaWiki:Lqt-marked-as-read-placeholder
$1 not filled into message MediaWiki:Lqt-marked-as-read-placeholder
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://translatewiki.net/w/i.php?titl...
:
Depends on:
Blocks: messages
  Show dependency treegraph
 
Reported: 2010-09-13 07:22 UTC by Purodha Blissenbach
Modified: 2012-07-24 13:50 UTC (History)
5 users (show)

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


Attachments
Screenshot showing 3 times "The thread was marked as read. Undo" insted of "The thread $1 was marked as read. Undo" (22.92 KB, image/png)
2010-09-13 07:22 UTC, Purodha Blissenbach
Details

Description Purodha Blissenbach 2010-09-13 07:22:37 UTC
Created attachment 7684 [details]
Screenshot showing 3 times "The thread  was marked as read. Undo" insted of "The thread $1 was marked as read. Undo"

The message MediaWiki:Lqt-marked-as-read-placeholder
has a placeholder $1 inside,
which is supposed to be replaced by a thread title.
It is not, but replaced by an empty string instead,
as the attached screen shot shows.
Comment 1 Alex Monk 2012-07-24 13:50:23 UTC
It looks like this was fixed at some point.

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


Navigation
Links