All old posts as new

I have all old messages of Extension talk:ParserFunctions as new! This extremely annoying! Subfader 17:43, 14 January 2012 (UTC)

This happened because the old talk not using LQT was transformed into talk using LQT. I also think that it would be better to archive old talk an start newly with LQT. However, this has nothing to do with LQT as such. Cheers [[kgh]] 20:33, 14 January 2012 (UTC)

kk. Subfader 18:43, 15 January 2012 (UTC)

LiquidThreads and link rot

In traditional talk page technology, there is such problem with heavily used talk pages as invalidation of inbound links due to archiving. If I give a link (such as [[namespace:page#section]] to an active discussion in, say, a wikiproject in English Wikipedia, then in several weeks this link will become nearly useless. Do LiquidThreads offer permanent links to discussions, which are preserved even if a thread moves to a talk page named differently? Incnis Mrsi 12:17, 30 January 2012 (UTC)

Yes. Nemo 19:03, 28 September 2012 (UTC)

There are new posts - your own replies

I hate it showing up my own posts as new messages after leaving comments. Sometimes it even updates onpage with an alert. Then you click and they're even hidden behind a "show X replies"-link... This and the slowness keep me from using this extension. Subfader (talk) 19:08, 21 February 2012 (UTC)

Disable LQT in custom namespace

Hi, is there a way to disable LQT in a custom namespace? I ask because LQT conflicts with wikilog extension comments. Thanks in advance! Singlespeedfahrer 08:56, 24 February 2012 (UTC)

see documentation https://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/LiquidThreads/README?revision=78554&view=markup Wikinaut (talk) 09:50, 24 February 2012 (UTC)

Thank you for your answer. As far as I see LQT uses other namespace as wikilog (100) as default (I use namespace 106 for wikilog), so this shouldn't affect the issue(?). Could you please give me a hint? Seems to be that I miss the forest for the trees ;). Singlespeedfahrer (talk) 10:10, 24 February 2012 (UTC)

Adding toolbar section and group to WikiEditor

Hi, I would like to add a group and a section to the WikiEditor used by LiquidThreads as described in Extension:WikiEditor/Toolbar_customization#Adding_things (works for me on pages without LiquidThreads). Unfortunately my JavaScript experiences are very bad. Has anyone accomplished this yet or can give me a hint to do this? Best wishes. Singlespeedfahrer (talk) 09:48, 26 February 2012 (UTC)

lost hope for version 3.0

other extensions are heavily developed, but this one is lost in space. perhaps admins got better jobs. 213.134.163.130 20:10, 30 March 2012 (UTC)

You mean, "lost in communication". 3.0 is under development but we know nothing of it. Jasper Deng (talk) 21:47, 30 March 2012 (UTC)

No, at least Wikimedia Foundation has given up on this. G.Hagedorn (talk) 01:58, 25 July 2012 (UTC)

The progress can be seen at gerrit

last commit ist 10 month ago.

And there is a clear statment on Werdnas discussionpage to this topic. DaSch (talk) 06:53, 25 July 2012 (UTC)

mw 1.17 upgrade

I'm on mw 1.17.3 and just installed lqt 1.17.x version; my spinner still spins when starting a new discussion. The error console reports 4 "jquery is undefined" msgs in lqt.js.

Installed the development trunk version, but it references mw.util.wikiScript which is part of mw 1.18.

any help is appreciated to upgrade lqt for 1.17. thanks Hypergrove (talk) 15:08, 24 April 2012 (UTC)

I also receive these errors, MW 1.17.2:

• jquery is not defined - line 7:

   jQuery.getCSS = function( url, media ) { 

  
  

• stylepath is not defined - line 860: <pre> 'result': { htmlMsg: [ 'wikieditor-toolbar-help-content-file-result', stylepath ] } </syntaxhighlight>
  

• jquery is not defined - line 108:

    } )( jQuery ); 

  
  

• jquery is not defined - line 133: <pre> })(jQuery); </syntaxhighlight>
  

• jquery is not defined - line 10:

    ;jQuery.ui || (function($) {  

  
  

I can provide more information, if you need. -- I also can not use the trunk version of Liquidthreads because I am currently locked into MW 1.17 50.32.71.188 16:08, 21 May 2012 (UTC)

Another company using the name Liquid Threads

Just so this company is aware, there is another business using this name....i just didn't want that other business to tarnish your name. The other business is located in Frankfort Square,IL......Just wanted you to have a heads up. The name of the company is Liquid Threads, might get confusing. 166.249.129.168 19:23, 2 May 2012 (UTC)

Nobody cares. Nemo 18:44, 28 September 2012 (UTC)

Still - thanks for the heads-up, even if it turns out not to matter. :) Sharihareswara (WMF) (talk) 02:53, 29 September 2012 (UTC)

Really silly question about "You have new messages" bar

Does LQT have anything to do with disabling the "You have new messages" orange bar (Manual:Hooks/UserRetrieveNewTalks)? Mine does not appear even when new messages are posted to my talk page via LQT on my private wiki - I can't pinpoint the cause.    Thorncrag   17:21, 31 May 2012 (UTC)

I'm finding myself getting confused by this. The bar -IS- appearing for LQT threads; however, it does NOT appear when the actual talk page is edited (referred to as "discussion page header" by LQT). This is a failure when used in conjunction with WikiLove, because the love is posted to the talk page, not to LQT, resulting in no new message notification going to the user upon receiving WikiLove. I'm still testing.    Thorncrag   17:45, 31 May 2012 (UTC)

Okay, found bug 33260 courtesy of MZMcbride :-)    Thorncrag   18:01, 31 May 2012 (UTC)

Clicking the file icon gives: <wikieditor-toolbar-tool-file-pre>Example.jpg]]

Why is it that when you click the file icon, it give you:<wikieditor-toolbar-tool-file-pre>Example.jpg]]

Is there anything I can change to fix that? Everything else works fine.

Also, I hope you don't mind me asking but is there an extension (not SocialProfile) that gives me a PM (just PM, not AWC forum) system?

Thanks a bunch! Muqman 52 (talk) 20:19, 31 May 2012 (UTC)

LQT with WYSIWYG

I'm using LQT with extension:WYSIWYG in MW 1.18. But when edit discussion / reply, editor doesn't appear. I think LQT is based on WikiEditor, but now I'm not using WikiEditor. How to solve this problem to use LQT with WYSIWYG? Quirax (talk) 14:24, 8 June 2012 (UTC)

Liquid Threads does not display properly

Here's a link to what it looks like (at the bottom)

http://en.sturmkrieg.com/User_talk:Inquisitor_Ehrenstein

It clearly does not look the way it is intended to look. It looks like it did not finish loading or something. I read something recently that makes me think it could maybe have to do something with cache expiry? Инкуиситор Саша Ехренстеин аус дем Стурмкриг Сектор (Talk) (Contributions) 14:38, 5 July 2012 (UTC)

There are lots of "404 (Not Found)" errors in the console when accessing that page. Helder 14:55, 5 July 2012 (UTC)

I believe I am having the same problem with my wiki. It's like the "more" menu in the lower right hand corner doesn't load correctly. Did you ever find a solution? Craig131 (talk) 23:03, 10 September 2012 (UTC)

WikiEditor and LiquidThreads 2.0

I have a MW 1.19 installed with WikiEditor 0.31 et LiquidThreads 2.0. LiquidThreads worked on MW 1.18 but not in MW 1.19. When I start a new thread, a circle-shaped wait indicator appeared in page.

Did you know how can I fix that ? Plalemand (talk) 13:25, 14 July 2012 (UTC)

I am facing same issue, I have MW 1.19.1 I tried LQT development version (trunk) as well as 1.19.x but issue is still not solved. Aimtohigh (talk) 07:32, 9 August 2012 (UTC)

Another interesting issue: the WikiEditor is invoked within LiquidThreads, even when it is disabled by default. Why? Arided (talk) 20:57, 15 November 2012 (UTC)

This is bug 29681. Helder 19:06, 8 June 2013 (UTC)

Solution: Exclude LiquidThreads from certain namespaces / avoid conflict with Wikilog

Here is a solution for excluding LiquidThreads 2.0 from certain namespaces and to avoid conflicts with other extensions such as Wikilog:

$IP/extensions/LiquidThreads/LiquidThreads.php: insert at the end of the file:

//Namespaces in which NOT to enable LQT
$wgLqtExcludeNamespaces = array();

$IP/extensions/LiquidThreads/classes/Dispatch.php: insert in the function isLqtPage ( $title ) (line 114) after the lines

		if ( !$title ) {
			return false;
		}

the following lines

// Ignore it if it's e.g. a blog,
// makes no sense to have LiquidThreads there.
	global $wgLqtExcludeNamespaces;
	if ( in_array( $title->getNamespace(), $wgLqtExcludeNamespaces ) ) {
			return false;
	     }

$IP/LocalSettings.php: now provides a variable for specifying the namespaces which are to be excluded from the LiquidThreads functionality. Example:

##LiquidThreads
require_once("$IP/extensions/LiquidThreads/LiquidThreads.php");
$wgLqtExcludeNamespaces[]=401;

## Wikilog
require_once( 'extensions/Wikilog/Wikilog.php' );
Wikilog::setupNamespace( 400, 'Blog', 'Blog_talk' );

According to this specification Wikilog creates the namespaces 400 ("Blog") and (implicitly defined) 401 ("Blog_talk"). For LiquidThreads namespace 401 is excluded. It thus can be used for the comment function of Wikilog

Tested with MW 1.19, MW 1.18 + LQT 2.0-alpha + Wikilog 1.2.0 Kappa (talk) 15:35, 17 July 2012 (UTC)

Development Help

Before letting this project die maybe there are some people that would help with development? First I have some questions.

1. Is it possible to run LQT3 on Jenkins to maybe find bugs there?
2. Maybe there could be a ZendDebugger run on wikimedia server that can be accessed remotly from Eclipse/Aptana that can be used for debugging?
3. Waybe an instance of LQT3 could be installed somewhere so it could be tested?

Maybe this could be a beginning for really re-energizing LQT and to involve people outside WMF that are interested in the project to help with the Development. I'm ready to start! --DaSch (talk) 18:24, 24 July 2012 (UTC)

>Is it possible to run LQT3 on Jenkins to maybe find bugs there?

Why not just do this locally (I somewhat doubt LQT3 has tests yet given its incomplete).

>Maybe there could be a ZendDebugger run on wikimedia server that can be accessed remotly from Eclipse/Aptana that can be used for debugging?

I've never heard of/used ZendDebugger, but given this code is not really in the "it works" state yet, I'm unsure how useful that would be, or what the benefit of having it on Wikimedia servers would be.

>Waybe an instance of LQT3 could be installed somewhere so it could be tested?

Sounds like a use case of labs.

>I'm ready to start!

Yay! enthusiasm. Let me know if there's anything I can do to help. (Well anything that takes virtually no effort or time on my part ;) I'm not currently devoting all that much time to MW development related things). Bawolff (talk) 19:33, 24 July 2012 (UTC)

so maybe starting at wikimedia labs ;)

never worked with it. So maybe you could help me to get it installed/runnig there. This would help a lot. DaSch (talk) 19:45, 24 July 2012 (UTC)

Hmm, I might even have me an account (I think I got one automatically when I got my gerrit account, not really sure). Bawolff (talk) 19:49, 24 July 2012 (UTC)

I fear, that when developing LQT3 nobody thought about testing. So there is no database scheme delivered. So the source code is useless. Or I would have first to reengenieree the database before I can start testing or something elese. DaSch (talk) 19:58, 24 July 2012 (UTC)

Incompetent writers

Just a heads up, "maintaince" is not a word. 50.100.157.188 08:19, 26 July 2012 (UTC)

ever thought about the fact, that not the everbody is speaking english!? DaSch (talk) 09:45, 26 July 2012 (UTC)

Luckily it is a wiki, so even you can fix such mistakes! Bawolff (talk) 12:56, 26 July 2012 (UTC)

I've fully protected the page due to edit warring; I'll attempt to make the fix. Jasper Deng (talk) 16:16, 26 July 2012 (UTC)

lol, in that case I'll stop being so condescending with the sofixit remarks ;) Bawolff (talk) 13:05, 27 July 2012 (UTC)

As an aside, why doesn't the "view source" view state the reason for protecting? probably some MW bug. Bawolff (talk) 13:06, 27 July 2012 (UTC)

I've added this as bugzilla:38764. :-) Jdforrester (WMF) (talk) 18:36, 27 July 2012 (UTC)

I'm going to unprotect the page, as there seems to be no more dispute. Jasper Deng (talk) 18:40, 27 July 2012 (UTC)

Database Error

I installed LQT. Unzipped it, renamed it, put it in the right directory. I added the "require once" line of code to my LocalSettings.php

Now when I load the wiki, it gives me the following error... "A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "NewMessages::newMessageCount". Database returned error "1146: Table 'ecovativewiki.ew_user_message_state' doesn't exist (localhost)"."

What should I do about this? I need it fixed ASAP 66.109.35.130 19:05, 8 August 2012 (UTC)

You forgot to create the necessary database tables. Try running /maintenance/update.php. Jasper Deng (talk) 19:20, 8 August 2012 (UTC)

I tried running that, but anytime I go to my browser and type in "wiki.ecovativedesign.com/maintenance/update.php"

It says I don't have access and I am forbidden to view the document. But I'm the webmaster!

I even tried copying "update.php" into the main directory. Then it gives me access to the document, but says there is a server error.

Any ideas? 66.109.35.130 13:25, 9 August 2012 (UTC)

You have to run that from your command line. Jasper Deng (talk) 16:46, 9 August 2012 (UTC)

If you don't know how to run it from the command line, like Jasper suggests, you can do it in your browser by navigating to /mw-config/ and following the instructions there. So, in your case you would type "wiki.ecovativedesign.com/mw-config/" into your address bar. Let me know if you need more help with this. Craig131 (talk) 00:25, 21 September 2012 (UTC)

A database query error has occurred. This may indicate a bug in the software.

Query:

SELECT user_claim FROM `user` WHERE user_id=

Function: DatabaseBase::select

Error: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near at line 1 (localhost) 210.89.56.38 06:47, 28 February 2014 (UTC)

Please give your MediaWiki, MySQL, and LiquidThreads versions. Jasper Deng (talk) 08:04, 28 February 2014 (UTC)

You should create a new thread for this issue.

Apparently, an empty user_id is being passed to the query, which produces the error. ¿Did you deleted stuff from database directly, or used any extension to do a cleanup of spam user accounts? Ciencia Al Poder (talk) 10:28, 28 February 2014 (UTC)

Allow anonymous to post to liquid thread

Ok So I have my Wiki set to allow anonymous to edit pages but not add new pages. anonymous can edit or add talk pages just not main pages. Why will Liquid Threads not allow anonymous users to post a thread then. Does anyone know how to change Liquid Threads to allow anonymous users to post even though creatpage is disabled. Below are my permissions. The Wiki is www.trailwiki.us if you want to see what I am talking about.

$wgGroupPermissions['*']['createpage'] = false;

$wgGroupPermissions['*']['createtalk'] = true;

$wgGroupPermissions['*']['edit'] = true;

$wgGroupPermissions['*']['edittalk'] = true;

$wgGroupPermissions['user']['createpage'] = true; fox15rider 22:15, 8 August 2012 (UTC)

Thanks to your post I found out how to disable LiquidThreads for anonymous writers (exactly the opposite of what you wanted to do ;)

I had to set ['*']['createpage'] to false.

It seems you managed to enable LiquidThreads for anons now? Stefahn (talk) 10:03, 1 October 2012 (UTC)

I have still not figured out how to allow anonymous people to add comments on liquid threads. I would like to only allow users to edit pages but allow anonymous users to post on liquid threads.. Anyone out there know how? Fox15rider - www.TrailWIKI.org 21:26, 20 February 2013 (UTC)

I'd consider this bugzilla:26383. Nemo 08:19, 21 February 2013 (UTC)

$wgNamespaceProtection[NS_MAIN]      = array( 'ns-protected' );
$wgNamespaceProtection[NS_USER]      = array( 'ns-protected' );
$wgNamespaceProtection[NS_SPECIAL]      = array( 'ns-protected' );
$wgNamespaceProtection[NS_FILE]      = array( 'ns-protected' );
$wgNamespaceProtection[NS_MEDIAWIKI]      = array( 'ns-protected' );
$wgNamespaceProtection[NS_TEMPLATE]      = array( 'ns-protected' );
$wgNamespaceProtection[NS_HELP]      = array( 'ns-protected' );
$wgNamespaceProtection[NS_CATEGORY]      = array( 'ns-protected' );
$wgGroupPermissions['*']['createaccount']  	 		= true;
$wgGroupPermissions['*']['read']           			= true;
$wgGroupPermissions['*']['edit']            			= true;
$wgGroupPermissions['*']['createpage']      			= true;
$wgGroupPermissions['*']['createtalk']      			= true;
$wgGroupPermissions['*']['ns-protected']      			= false;

This allow to create new thread only TALK namespaces which LiquidThreads in. Other default namespaces is not allowed to non user.

If you want check non-human bot, use ConfirmEdit extensions with these options :

$wgGroupPermissions['*'            ]['skipcaptcha'] = false;
$wgGroupPermissions['autoconfirmed']['skipcaptcha'] = false;
$wgGroupPermissions['user'         ]['skipcaptcha'] = true;
$wgGroupPermissions['bot'          ]['skipcaptcha'] = true; // registered bots
$wgGroupPermissions['sysop'        ]['skipcaptcha'] = true;
$wgCaptchaTriggers['edit']          = true; 
$wgCaptchaTriggers['addurl']        = true; 
$wgCaptchaTriggers['createaccount'] = true;
$wgCaptchaTriggers['badlogin']      = true;

in MediaWiki 1.20.3, this works very well. 211.61.23.35 02:10, 8 March 2013 (UTC)

If your MediaWiki use autoconfirmed for confirm users, may it be variable array $wgNamespaceProtection associated with this right.

$wgAutoConfirmAge = 6000;
$wgNamespaceProtection[NS_MAIN]      = array( 'autoconfirmed' );
$wgNamespaceProtection[NS_USER]      = array( 'autoconfirmed' );
$wgNamespaceProtection[NS_SPECIAL]   = array( 'autoconfirmed' );
$wgNamespaceProtection[NS_FILE]      = array( 'autoconfirmed' );
$wgNamespaceProtection[NS_MEDIAWIKI] = array( 'autoconfirmed' );
$wgNamespaceProtection[NS_TEMPLATE]  = array( 'autoconfirmed' );
$wgNamespaceProtection[NS_HELP]      = array( 'autoconfirmed' );
$wgNamespaceProtection[NS_CATEGORY]  = array( 'autoconfirmed' );
$wgGroupPermissions['*']['createaccount']  = true;
$wgGroupPermissions['*']['read']           = true;
$wgGroupPermissions['*']['edit']           = true;
$wgGroupPermissions['*']['createpage']     = true;
$wgGroupPermissions['*']['createtalk']     = true;
$wgGroupPermissions['*']['autoconfirmed']   = false;

I use it with git master branch MW (1.26alpha). Want (talk) 12:15, 14 July 2015 (UTC)

auto place template in header?

I'd love to put some directions/advice for use in the header (ideally with a template) for each LT page on my wiki. any advice on how to do this without having to manually place it on each new discussion page? 209.6.119.94 19:43, 10 August 2012 (UTC)

bugzilla:25441. Nemo 18:19, 28 September 2012 (UTC)

New messages(3) could not be clean.

It looks like some database error made the new messages could not be clean.

The My new messages (3) shows to every one

How can I reset it to none?

I want to solve it ASAP! Zoglun (talk) 18:45, 14 August 2012 (UTC)

That seems to be bugzilla:31251 again... Helder 00:26, 15 August 2012 (UTC)

Why I hate LiquidThreads

Disclaimer: I'm sorry for the offensive subject. I try to be as constructive as I can.

1. The whole idea of threaded messages is wrong. Look at how people use it: Everything is a single branch of messages going deeper and deeper. Everybody knows it's a stupid idea to put an answer somewhere in the middle of the thread and nobody does it. Nobody will see your answer there (bugzilla:20543). I know the current discussion style (using nested lists) in the Wikipedia projects has the same problem. The point is: LiquidThreads does not fix any of the problems we have with the current discussion style in the Wikipedia projects.
2. It's a mess. Everything is scattered around millions and millions of tiny little sub-pages. Don't tell me this is an implementation detail and I don't have to care about. Why am I able to see this if I don't have to care about?
3. There is no history. When I try to access a history all I get are useless single-entry lists like this.
4. It's impossible to use without JavaScript. Sure, you are able to access the messages even with JavaScript disabled. But again it's a mess. You can't use it. It looks like a lazy AJAX experiment gone horribly wrong.
5. It's so damn slow. Every click takes seconds. Often even without an AJAX spinner animation. And you have to click hundreds and hundreds of links.
6. Nothing is shown in my watch list (bugzilla:20541).
7. When I clicked "read" everything is gone from my new messages page. There is no way to go back to the latest discussions.
8. I can't choose what I want to read first.
9. When I unwatch a discussion it is not removed from my new messages page (bugzilla:21732).
10. Editing a message (for example to fix a typo or to add something) is almost impossible. It gets messy very, very fast. The date of the message does not change so nobody will notice I added something. All I can do is to add a new message which makes the mess even more painful. Again, I know the current discussion style in the Wikipedia projects has the same problems. Again, LiquidThreads does not fix any of these problems.
11. I hate the sliding jQuery animations. You are wasting my time! When I click something I want to see it. Now. A link entitled "more" should show more. It's not entitled "start fancy animation" (bugzilla:25039). TMg 13:15, 28 August 2012 (UTC)

Great. I hate regular talk pages. Much more than I hate LiquidThreads.

So what are you going to do about it? :). siebrand (talk) 20:55, 28 August 2012 (UTC)

Exactly! Helder 00:23, 30 August 2012 (UTC)

1. I disagree that is stupid. I see no point in putting a reply in the end if I'm comment about one of the first comments (to which no one else replied)

3. Have you tried the "history" link on top of the thread?

6. Everything is shown in the Special:NewMessages (including the messages you said on first item nobody would notice)

8. How so? Why not?

10. Sure they will. It appears on Special:NewMessages.

11. Bug 30401? Helder 00:33, 30 August 2012 (UTC)

What is this supposed to be? Where are the "prev" and "compare revisions" links? Where are the "undo" links?

Special:NewMessages is a mess. Especially with JavaScript disabled.

At Special:NewMessages everything is shown on a giant page. I can't choose which topic is more important for me and what I want to read first. I can't order it. Even when I try to collapse the threads they do not collapse but are shown as a useless "mini" threads instead, still wasting space.

See 6.

New Bug: The "preview" button is broken. I have to click twice to see the preview (browser is Opera 12.02). TMg 20:09, 21 September 2012 (UTC)

3. The "prev", "undo" and "compare revisions" are available for each reply. But I don't think they make much sense for the thread as a whole. Helder 15:11, 22 September 2012 (UTC)

"Why I hate liquid threads" number 13: I had read a new message. I even wrote a reply. But the top navigation bar still tells me there is a new message. What new message? The one you just replied to.

Number 14: The nesting of the gray boxes looks ugly. See this box. The top border line is missing. Why are there even boxes?

Number 15: Again I had one of these AJAX spinners on the screen forever. Literally. No timeout. Not even a hint on what's going on or even if something is going on or not. Just that fake animation that is in no way connected to the real action.

Number 5 again: Why takes rendering a preview so damn long? It's less than half the time if I show the preview of a regular wiki page. TMg 22:40, 8 January 2013 (UTC)

Thank god that the preview works. It's been completely broken for a long time (well, it surely felt very long). Nemo 09:55, 9 January 2013 (UTC)

Number 12 seems to be missing. Allow me to add a candidate: There is no "Show changes" when i am editing a message.

16. You can't change the location (URL) of a thread.

17. When the title of a thread changes, the new value applies retroactively to all older revisions. Jokes_Free4Me (talk) 23:47, 7 April 2014 (UTC)

Own hooks seem to be blocked by LiquidThreads if there is no discussion yet!?

Hi all.

I use hook "ArticleViewHeader" to add a message on top of all discussion pages. Since I enabled extension LiquidThreads the hook is no longer called on discussion pages. This happens only on discussion pages which are empty, i.e. where nobody has posted so far.
I found the same behavior with hook "OutputPageBeforeHTML".

Can anybody please tell me how I can call my hook on empty liquid threads?
Thanks for your help! Stefahn (talk) 12:08, 1 October 2012 (UTC)

Bug with watch and unwatch links

If I click the watch/unwatch links (next to a headline) nothing happens.
I can only watch/unwatch a thread by navigating to the permalink of the thread and use the watch/unwatch link (star) from the user menu in the very top. This is very cumbersome...

I found out that the links from the user menu contain my watchlist token at the very end - whereas the watch links within LiquidThreads don't have any token. Maybe this is the reason? Stefahn (talk) 18:16, 1 October 2012 (UTC)

I also entered this bug here: https://bugzilla.wikimedia.org/show_bug.cgi?id=40665 Stefahn (talk) 18:31, 1 October 2012 (UTC)

Can I convert an existing talk page?

I want to use LQ on my own talk page but I don't want to lose previous discussions. I guess it's not possible? Subfader (talk) 21:02, 16 October 2012 (UTC)

The existing discussions will stay as they are, in the top of the page, but you can also choose to archive them in a subpage. Helder 21:39, 16 October 2012 (UTC)

Thanks, just did so now Subfader (talk) 21:58, 16 October 2012 (UTC)

LiquidThread CSS not loading - threads look unpleasant

Hi all.

I've recently installed LiquidThreads and got it working on my site. However the CSS is not loading so the page looks really bad. I see that in the extensions/LiquidThreads directory there is a file called "lqt.css" but it's not loading the CSS at all.

Is there a step I'm missing? Must I create an article Mediawiki:lqt.css or something like that?

Any help appreciated. 196.8.104.55 14:43, 7 November 2012 (UTC)

Can you link us the wiki? Nemo 22:09, 8 November 2012 (UTC)

Hi Nemo,

Thanks for the reply.

Unfortunately the wiki is on an internal network behind a very strict firewall :( I can send a screenshot if that helps? 196.8.104.55 04:08, 11 November 2012 (UTC)

Yes, you can try bugzilla with a screenshot. However, I'm not a dev and LQT is an unsupported extension, so it might be almost as unlikely to get help there as here. Nemo 22:53, 11 November 2012 (UTC)

• There is no need to create Mediawiki:lqt.css (that page is not used, creating it won't do anything)
• It is working fine on Wikimedia and on TranslateWiki so it is likely a configuration error on your wiki. Perhaps look into Manual:How to debug and $wgExtensionAssetsPath . Krinkle (talk) 19:45, 12 November 2012 (UTC)

Had the same problem with my wiki, solved it by commenting out the dependency on 'mediawiki.action.edit.preview' in LiquidThreads.php.

'dependencies' => array(

'jquery.ui.dialog',

'jquery.ui.droppable',

//'mediawiki.action.edit.preview',

),

149.243.232.3 12:25, 4 December 2012 (UTC)

Why was the development cancelled?

What was the real reason this project was cancelled (=not deployed widely to all wikis). Was it a lack of community consensus for enabling this (probably at least on English Wikipedia)? Kozuch (talk) 10:58, 3 December 2012 (UTC)

The English Wikipedia had no consensus. In addition, the current version (the one being used here) scales poorly. Jasper Deng (talk) 18:07, 3 December 2012 (UTC)

There was/is consensus for use of LQT in more than one wiki, even if it scales poorly. Helder 23:50, 18 December 2012 (UTC)

I would guess that it was felt that a new extension (Echo) would better achive the foundation's goals. Bawolff (talk) 01:07, 19 December 2012 (UTC)

Maybe voting is difficult in a traditional thread model 75.112.161.130 04:08, 7 February 2013 (UTC)

That makes no sense, voting is quite possible on internet forums, all of which necessarily have threaded discussion. I do prefer threaded discussion, and threads can be distributed over multiple pages. Myrtonos (talk) 02:36, 26 October 2013 (UTC)

They can with traditional wikitext, but they can't with LQT. Nemo 17:56, 26 October 2013 (UTC)

Why is voting possible both on forums and with unstructured wikitext talkpages, but not with liquid threads? Myrtonos (talk) 08:48, 27 October 2013 (UTC)

I was replying to "threads can be distributed over multiple pages": they can't, with LQT, because you can't transclude LQT threads. Nemo 20:34, 27 October 2013 (UTC)

__DIR__ in LiquidThreads.php is empty

In LiquiThreads.php why line $dir = dirname( __FILE__ ) . '/'; has been replaced by $dir = __DIR__; with a __DIR__ not defined ? Champagne (talk) 17:26, 26 December 2012 (UTC)

It's predefined by PHP... Krenair ^{(talk • contribs)} 17:30, 26 December 2012 (UTC)

... if you use version 5.4.0. ( i have php 5.2.6-1 )

Thanks anyway Champagne (talk) 17:41, 26 December 2012 (UTC)

It says added in 5.3.0, which was released 30th of June 2009, so it's not exactly an unreasonable requirement. Krenair ^{(talk • contribs)} 21:02, 26 December 2012 (UTC)

I've specified the requirement in the infobox; it's a requirement for newer MediaWikis anyway, and if you're using LQT on an older MediaWiki you are especially adventurous (even more than normal LQT users!). Nemo 21:38, 26 December 2012 (UTC)