Last modified: 2012-11-19 15:59:08 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 25019 - Enable LiquidThreads extension on tr.wikinews
Enable LiquidThreads extension on tr.wikinews
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
Extension setup (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://tr.wikinews.org
:
Depends on:
Blocks: 19699
  Show dependency treegraph
 
Reported: 2010-09-01 21:25 UTC by Serhat Erdoğan
Modified: 2012-11-19 15:59 UTC (History)
8 users (show)

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


Attachments

Description Serhat Erdoğan 2010-09-01 21:25:13 UTC
Hi,

We would like to have the following namespace for comments on news articles: Yorum. Also we would like to enable LiquidThreads extension for Yorum namespace. Discussion: http://tr.wikinews.org/wiki/Vikihaber:K%C3%B6y_%C3%A7e%C5%9Fmesi#Comments_.28yorum.29_alan_ad.C4.B1n.C4.B1n_a.C3.A7.C4.B1lmas.C4.B1 and http://tr.wikinews.org/wiki/Vikihaber:K%C3%B6y_%C3%A7e%C5%9Fmesi#LiquidThreads
Comment 1 JeLuF 2010-09-02 05:27:08 UTC
What's the name of the discussion namespace for "Yorum"? (Even if it might not make much sense to have a discussion namespace in this case, the software needs one).
Comment 2 sekseniki145 2010-09-02 10:20:30 UTC
(In reply to comment #1)
> What's the name of the discussion namespace for "Yorum"? (Even if it might not
> make much sense to have a discussion namespace in this case, the software needs
> one).

It is "Options" in English.
Comment 3 JeLuF 2010-09-02 11:05:24 UTC
Namespaces come in pairs. Like "Image" and "Image talk". So if you want to have a new namespace "Yorum", we also have to set up a talk namespace for it. And this namespace needs a name.
Comment 4 Serhat Erdoğan 2010-09-02 11:58:37 UTC
Hi, 
If there has to be a talk namespace, it can be "Yorum tarışma". But it would be better without any talkspace if it was possible.
Comment 5 Leinad 2010-09-02 12:06:24 UTC
(In reply to comment #4)
> Hi, 
> If there has to be a talk namespace, it can be "Yorum tarışma". But it would be
> better without any talkspace if it was possible.

It is not possible.

En.wikinews and de.wikinews which have "Comment" namespace, also have "Comment_talk" namespace but this namespace is hidden by css hack. For example look at http://en.wikinews.org/wiki/MediaWiki:Common.css, there is: body.ns-102 #ca-talk {display:none;}
Comment 6 Serhat Erdoğan 2010-09-02 19:02:23 UTC
It seems I misspelled the talkspace. It should be "Yorum tartışma".
Comment 7 Aykut 2010-10-06 17:10:24 UTC
Domain name is not opened yet been made. Is there a problem?
Comment 8 Antoine "hashar" Musso (WMF) 2011-01-16 16:19:18 UTC
Created namespaces:

     'trwikinews' => array(
         100 => 'Portal',
         101 => 'Portal_tartışma',
+		106 => 'Yorum',
+		107 => 'Yorum_tartışma',
     ),
Comment 9 Vito Genovese 2011-01-25 23:40:13 UTC
Sorry to reopen it. But the extension "Liquid Threads" is yet to be enabled.
Comment 10 Andrew Garrett 2011-01-26 18:45:41 UTC
Further LiquidThreads deployments are on hold. See bug 19699.
Comment 11 Vito Genovese 2011-01-26 18:55:09 UTC
(In reply to comment #10)
> Further LiquidThreads deployments are on hold. See bug 19699.

Thank you Andrew. I'll notify the community (and would be delighted if you could take a look at bug 26943) :)
Comment 12 Sam Reed (reedy) 2011-05-23 19:26:00 UTC
Closing as later, as LQT isn't going to be deployed anywhere new atm
Comment 13 Andre Klapper 2012-11-19 15:59:08 UTC
I'm closing this request as WONTFIX as the current resolution RESOLVED LATER is deprecated (see http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65116 ), plus WONTFIX better reflects the situation.

This request will not get fixed, as deploying and developing LQT is on hold (see e.g. bug 19699 comment 10) and discouraged.
Its functionality will be superseded by Flow/Messaging in late 2013 or 2014, after Echo/Notifications has been successfully deployed.

For more information on Flow/Messaging see https://www.mediawiki.org/wiki/Flow .
For more information on Echo/Notifications see https://www.mediawiki.org/wiki/Echo_(Notifications) .

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


Navigation
Links