Last modified: 2013-04-22 16:17:02 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T31127, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29127 - LiquidThreads warning about signing your post is broken
LiquidThreads warning about signing your post is broken
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Alex Monk
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-05-24 21:57 UTC by Thor Malmjursson
Modified: 2013-04-22 16:17 UTC (History)
3 users (show)

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


Attachments

Description Thor Malmjursson 2011-05-24 21:57:52 UTC
On a fair few Wikis I've seen, one of the biggest bugbears for me certainly is the lack of new users who remember to sign their posts.  I'd like to ask that the autosign feature of LiquidThreads is removed, since one of its supporting functions is to make commenting easier for new users, and having it automatically sign posts / comments is not going to help new users to learn that elsewhere, they have to do that for themselves with the ~~~~ thing.  

The other issue is that quite often, certainly at Wikinews, where LQT is operational for our comments namespace, we get double signatures on threads where people automatically use the ~~~~ without remembering that it autosigns everything.

Can someone please fix this? Probably a checkbox saying "Don't sign my post, I'll use my own signature" or something?
Comment 1 Brandon Harris 2011-05-24 22:05:33 UTC
Actually, in the redesign, LQT will autodetect whether or not the user has signed the post and will remove any signatures.

I do not believe removing auto-signing is going to happen, nor do I anticipate a preference being added.  Adding more complexity to an already complex process is never the answer.

Accordingly, I am closing this bug WONTFIX.
Comment 2 Thor Malmjursson 2011-05-24 22:08:10 UTC
So basically, you won't fix this because it's being done in the "redesign"?  Is there any timeframe on when this "redesign" is going to materialise, or is it a "sit, wait and hope it turns up" kinda thing?
Comment 3 Brandon Harris 2011-05-24 22:11:45 UTC
I hate to say "pretty much" but yeah, pretty much.  

The LQT rebuild is ongoing but it is not currently a high-priority project for the Foundation so we don't have the resources to apply to it.  Even if we did have the resources to address local issues like this, I doubt this would happen because, frankly, it's the wrong thing to do from a design perspective.
Comment 4 Andrew Garrett 2011-05-26 23:48:51 UTC
Actually, you already get a warning when you sign a post with four tildes.

It's just that it gets lost between the edit toolbar and the textbox.

Reopening this bug to fix that.
Comment 5 Alex Monk 2013-02-20 19:10:56 UTC
(In reply to comment #4)
> It's just that it gets lost between the edit toolbar and the textbox.
> 
> Reopening this bug to fix that.

Gerrit change #50035
Comment 6 Alex Monk 2013-02-24 14:27:44 UTC
Merged by Siebrand.

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


Navigation
Links