Extension talk:LiquidThreads

From MediaWiki.org
Jump to: navigation, search
Start a new discussion
First page
First page
Previous page
Previous page
Last page
Last page

How to Recover Content of Talk Pages?

So, I've been recovering an old wiki from a laptop that died, and had to upgrade it from 1.18.5 (I think) to 1.24.1 to get it to work on my newer version of XAMPP. I've actually managed to get everything working pretty well, except for LiquidThreads. I'm thinking it might be best just to uninstall it and use regular talk pages, but I'd like to recover the content of those talk pages.

Is that possible, perhaps by somehow viewing the data tables in phpMyAdmin?

I have not uninstalled LiquidThreads yet, but I am currently unable to open talk pages. Instead I get the following error:

Fatal error: Call to undefined method MediaWiki::getVal() in E:\XAMPP\htdocs\mywiki\extensions\LiquidThreads\classes\Dispatch.php on line 25
Glameglumps33 (talk)18:53, 18 February 2015

You must upgrade Liquid Threads as well, downloading the 1.24 version.

Ciencia Al Poder (talk)10:39, 19 February 2015

Yeah, you're right. I thought I had updated it when I was updating the rest of my extensions, but it looks like I somehow skipped that one. My bad :p

Glameglumps33 (talk)11:10, 19 February 2015

Were you successful?

  • I am transfering the contents to a new wiki. And getting a similar problem. I was using LiquidThreads before, but unfortunately the pages are no longer found... or empty. I am using the 1.24 version... and it seems that I can only manually copy and paste into a new thread... on the new wiki. Any ideas?
TDeeming (talk)10:06, 21 April 2015

LQT nor formatting properly after changing web host

I've recently moved a mediawiki installation (mw: 1.23.3, lqt: 2.1 alpha) to a new web host and as a result liquid threads no longer formats properly. On the page responses to threads do not appear in ordered grey boxes but rather appear in plain list down the page without any formatting, as though no CSS is being picked up.

Any idea what the cause might be?

Lee Bunce (talk)19:00, 19 November 2014

Open the web developer tools of your browser (hit F12), switch to the console view, and reload the page where you have LQT.

Look on the console view if you see any JavaScript error or if some HTTP request receive HTTP 5XX/4XX responses.

Ciencia Al Poder (talk)10:18, 21 November 2014

Thanks, I don't get those errors. I get the following:

  • Error in parsing value for 'display'. Declaration dropped. load.php:1
  • Unknown property 'zoom'. Declaration dropped. load.php:1
  • Expected declaration but found '*'. Skipped to next declaration. load.php:1
  • Expected 'important' but found 'ie'. Expected ';' or '}' to terminate declaration but found 'ie'. Declaration dropped. load.php:1
  • Error in parsing value for 'background-image'. Declaration dropped. load.php:1
  • Unknown property 'user-select'. Declaration dropped. load.php:1
  • Unknown pseudo-class or pseudo-element '-ms-input-placeholder'. Ruleset ignored due to bad selector. load.php:1
  • Unknown pseudo-class or pseudo-element '-webkit-search-decoration'. Ruleset ignored due to bad selector. load.php:1


  • "Use of "delayedBind" is deprecated. Use the jquery.throttle-debounce module instead" load.php:148
Lee Bunce (talk)12:47, 21 November 2014

Those are just CSS errors/warnings, but they're normal.

Did you found any 5XX/4XX HTTP errors?

Is your wiki public so you can post a link to it here?

Ciencia Al Poder (talk)10:41, 22 November 2014

No, only a few HTTP/1.1 304 Not Modified messages. The wiki is private sadly. The only thing that changed to stop it working is the web host, any ideas what the difference could be?

Lee Bunce (talk)13:23, 23 November 2014

No idea. The only thing I can suggest is to append ?debug=true to the URL (or &debug=true if the URL already contains a question mark), that way every JavaScript and CSS file will be downloaded separately and you could track if one of them of LQT doesn't load in your wiki, comparing to here. But apart from that, there's nothing more we can do...

Ciencia Al Poder (talk)17:21, 23 November 2014

force-refresh a discussion page?

Is there any way to force-refresh a discussion page? I am sick of getting a notification about a new comment, going to the talk page and not finding the discussion. Makes me forget about threads I should answer all the time.

F.trott (talk)12:38, 28 March 2014

New comments appear in Special:NewMessages as well, no need to go to your talk page.

Ciencia Al Poder (talk)11:29, 29 March 2014

Well, maybe I should get sent a link to my Special:NewMessages then.

F.trott (talk)16:17, 29 March 2014

Sent where? It's in your personal tools.

Nemo09:05, 31 March 2014

Sent to me by email instead of the link to the discussion page where the new comment is not showing up.

F.trott (talk)09:08, 31 March 2014

That's bugzilla:34247. LQT is unmaintained, remember.

Nemo13:47, 31 March 2014

display discussion below article; closed-<talkpage> tag breaks page. [Bug 29211 ]

Edited by another user.
Last edit: 20:51, 22 October 2014

i can't find any information that using <talkpage /> will display discussion page below the main article page. can you confirm that's true? i can only see a blank page after saving a page with this phrase., 30 May 2011
  • Filed as Bug 29211 - "LiquidThreads crahes (shows an empty page) if tag <talkpage /> is found". I can confirm your observation.
Wikinaut19:33, 30 May 2011

Undefined Index errors

Seeing this alot with MW 1.23.5:

PHP Notice: Undefined index: thread in ../extensions/LiquidThreads/classes/ParserFunctions.php on line 68

Any ideas why?

Wmat (talk)21:04, 7 October 2014

JavaScriptless LQT silently fails to create a new topic

JavaScriptless LQT returns no error after I try to start a new topic and click submit. No topic is created, either. The message I typed is lost.

Gryllida10:56, 31 August 2014

Is it possible to access the discussion contributions from the wiki after removal of LQT?

I am wondering whether it is possible to find the discussion page created with LQT in the wiki after LQT has been removed from LocalSettings.php. In the DB I still can find a page with the name "Talk:SamplePage/Contribution1" in namespace 90 in the "page" table. If I follow the keys from the "page" table to the "revision" table and then to the "text" table, I also find the text of the contribution. I did however not succeed in finding the contribution in the wiki after removing LQT. If LQT is included in the wiki, the "show permalink" option renders the following permalink for the contribution: "Theme:Talk:SamplePage/Contribution1". As long as LQT is included, this link actually leads to the contribution. As soon as LQT is removed, the link however leads to a non-existing page. Does anybody have an idea, how to solve this problem?

Kappa (talk)14:24, 29 July 2014

It's "Theme:Talk:SamplePage/Contribution1" or "Thread:Talk:SamplePage/Contribution1"? It should probably be the second.

I guess the problem is the Thread: namespace that creates LQT, that is no longer present when not installed. You could try defining the Thread: namespace again in LocalSettings.php and you may be able to access messagess as individual pages, although I haven't tested it.

Ciencia Al Poder (talk)19:22, 29 July 2014

Great! Defining the namespace in LocalSettings.php works fine. Thank you very much for your quick and helpful answer. By the way: in the German version the namespace name is "Thema", but using "Thread" as namespace name in LocalSettings.php also works fine for other languages.

$wgExtraNamespaces[NS_THREAD] = "Thread";
$wgExtraNamespaces[NS_THREAD_TALK] = "Thread_Talk";
Kappa (talk)11:16, 30 July 2014

Can you make screenshots?

Nemo06:47, 31 July 2014

screenshots of what?

Ciencia Al Poder (talk)09:19, 31 July 2014

Of how things look after removing LQT

Nemo12:16, 31 July 2014

How to disable section editing

Apparently, saving the page after editing a particular section (through "edit section") leads to the loss of all other sections. Is there a way we can disable section editing for LQT?

Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)09:13, 16 June 2014

That's a bug. Alternatively, you can put __NOEDITSECTION__ on a message with sections

Ciencia Al Poder (talk)09:39, 16 June 2014

Thanks, I know about the magic word. I was just wondering if there was a more general setting for the Thread: namespace. Maybe 'editsection' can be used as a user right in $wgNamespaceProtection.

Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)10:27, 16 June 2014

The bug has been filled already: bug 46284

Ciencia Al Poder (talk)19:59, 16 June 2014

Okay, that's good to know.

Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)11:07, 17 June 2014

Why I hate LiquidThreads

Edited by 2 users.
Last edit: 10:09, 4 September 2012

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).
TMg13:15, 28 August 2012

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


Helder00:23, 30 August 2012

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?

Helder00:33, 30 August 2012
  1. What is this supposed to be? Where are the "prev" and "compare revisions" links? Where are the "undo" links?
  2. Special:NewMessages is a mess. Especially with JavaScript disabled.
  3. 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.
  4. See 6.

New Bug: The "preview" button is broken. I have to click twice to see the preview (browser is Opera 12.02).

TMg20:09, 21 September 2012

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.

Helder15:11, 22 September 2012

"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.

TMg22:40, 8 January 2013

Thank god that the preview works. It's been completely broken for a long time (well, it surely felt very long).

Nemo09:55, 9 January 2013

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

General Threads Overview

I stuck in this complex code trying to develop a special page allowing for an General Threads Overview. It is actually like any talk page but without the restriction on the article allowing to view the most recent discussions on all pages of a smaller wiki.

Has anyone done something like this before?

VolkoV (talk)06:49, 2 March 2014

Yes, that would be useful.

Perhaps you can also use the Semantic MediaWiki extension, make sure that the namespace "Thread" allows for semantic properties, and produce a table of single threads sorted by modification date. But I haven't tested this.

Cavila (MW 1.22, MySQL 5.1.72-2, Php 5.3.3-7 squeeze, SMW, SF 2.5.4)07:36, 2 March 2014

At least I found an SQL-Statement that can do that:

FROM prefix_thread
WHERE (thread_parent IS NULL OR thread_ancestor=thread_id) AND (thread_type<>2)
ORDER BY thread_modified DESC
VolkoV (talk)06:11, 3 March 2014

I have written an extension with a special page showing all threads without a summary - therefore a summary can be used to close a thread. As soon as I have cleaned up the coding I will post it here.

VolkoV (talk)12:57, 11 March 2014

Here we go, it is still quick and dirty:


VolkoV (talk)14:04, 11 March 2014

Good work! Having just tested this I can confirm that it works. Obviously it would be great if the devs could adopt this.

Cavila (MW 1.22, MySQL 5.1.72-2, Php 5.3.3-7 squeeze, SMW, SF 2.5.4)07:21, 12 March 2014

How to fully uninstall LQT?

There seems to be some artifacts with removing the LQT extension and lingering "what links here" links to old LQT threads. Is there a way to fully remove LQT? I can provide a link to the issue if needed, but thanks in advance if not.

Skunark (talk)05:23, 4 March 2014

AFAIK there is no exit strategy for LQT. LQT are forever.

Nemo20:21, 6 March 2014

It should be possible to remove all threads with nukeNS.php

Ciencia Al Poder (talk)20:57, 6 March 2014

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, 8 August 2012

You forgot to create the necessary database tables. Try running /maintenance/update.php.

Jasper Deng (talk)19:20, 8 August 2012

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?, 9 August 2012

You have to run that from your command line.

Jasper Deng (talk)16:46, 9 August 2012

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

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), 28 February 2014

Please give your MediaWiki, MySQL, and LiquidThreads versions.

Jasper Deng (talk)08:04, 28 February 2014

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

Internal error for Special:NewMessages

Yesterday I pulled the latest version from Git, which solved one issue but introduced another. This time Special:NewMessages has become unavailable, leading to an "Internal error":

[4208aaa9] /wiki/Special:NewMessages Exception from line 376 of .../includes/SpecialPage.php: Call to undefined method SpecialNewMessages::getPageTitle


#0 .../extensions/LiquidThreads/pages/SpecialNewMessages.php(23): SpecialPage->__call(string, array)
#1 .../extensions/LiquidThreads/pages/SpecialNewMessages.php(23): SpecialNewMessages->getPageTitle()
#2 .../includes/SpecialPage.php(631): SpecialNewMessages->execute(NULL)
#3 .../includes/SpecialPageFactory.php(488): SpecialPage->run(NULL)
#4 .../includes/Wiki.php(298): SpecialPageFactory::executePath(Title, RequestContext)
#5 .../includes/Wiki.php(602): MediaWiki->performRequest()
#6 .../includes/Wiki.php(467): MediaWiki->main()
#7 .../index.php(49): MediaWiki->run()
#8 {main}

Any ideas?

Cavila (MW 1.22, MySQL 5.1.72-2, Php 5.3.3-7 squeeze, SMW, SF 2.5.4)12:02, 13 February 2014

It's a change in the code relating to MW 1.23 that brought about the error:


Restoring getPageTitle to getTitle (deprecated in MW 1.23 but still used in MW 1.22) solved things.

Cavila (MW 1.22, MySQL 5.1.72-2, Php 5.3.3-7 squeeze, SMW, SF 2.5.4)12:13, 13 February 2014

Infinite ajax loader (again)

here is the problem, i have installed the 1.21 version of LQT but it didn't solve the problem of the infinite ajax loader... here is my wiki

http://www.greymatters.altervista.org/index.php/Discussione:Grey_Matters, 6 November 2013


Did this get resolved? Even I am facing the same issue.

Amitk75mw (talk)12:06, 6 December 2013

I've reproduced the issue. It seems there's a problem with the LiquidThreads version for MediaWiki 1.21, reported as bug 55694.

I've successfully installed version at the time of gerrit:58817, that you can download from here: [1]

It solves that issue for me. I haven't tested all of LQT features for this version, so I'm not sure if there's anything else broken for 1.21 version.

I hope someone fixes the 1.21 release branch of LQT soon.

Ciencia Al Poder (talk)18:23, 6 December 2013

Also, that version of LQT requires Extension:WikiEditor to be enabled, otherwise it throws a JavaScript error about unknown module ext.wikieditor

Ciencia Al Poder (talk)18:36, 6 December 2013

Thank you for posting this, it resolved my issue too and we using LiquidThreads quite a bit.

Fireflyt (talk)16:45, 24 January 2014

How to uninstall LiquidThreads ?

Hi guys. I want to uninstall LiquidThreads from my wiki. When I tried to simply remove [require_once( "$IP/extensions/LiquidThreads/LiquidThreads.php" );] from my config file, my wiki shows white-screen only, no response.

How to uninstall this extensions safely? (wiki version is 1.21.3), 21 November 2013

You should check your PHP error log file to see what error was happening when you got blank screens.

Krenair (talkcontribs)00:52, 21 November 2013

Cannot read property 'token' of undefined


After upgrading MediaWiki i have began to encounter the following error:

Uncaught TypeError: Cannot read property 'token' of undefined

It happens on at the following execution.

var token = data.threadaction.token;, 14 October 2013

I've looked at what 'data' is, and it's:

  • data -> Object
    • error -> Object
      • code = "notoken"
      • info = "The token parameter must be set"


There are some __proto things there too, let me know if you need them, 14 October 2013

This error is not on bugzilla, it would be helpful to file it. However, we need to know what version of MediaWiki and LQT you're using; I've not encountered this error myself.

Nemo07:52, 14 October 2013

I'm getting the same error with the latest version of MediaWiki. Running on Windows Server 2012 R2 with MySQL., 19 November 2013

[RESOLVED] Edit/History/Delete on top of each other (paragraph inserted)

I just upgraded a Wiki to 1.21.1 and installed LiquidThreads 2.0 on top of that (so I don't know if the problem occurs with earlier mediawiki-versions).

The threads seem to work fine. The only problem seems to be that p-tags seem to be inserted between the [ and the Edit/History etc button. No idea at which level this happens: MediaWiki/the plugin/the Skin.

Any hints?

Bgschaid (talk)13:47, 19 July 2013

Mystery solved: it's not the extension. It's the ParseBeforeTidy-hook recommended for Project Honeypot

Bgschaid (talk)13:31, 22 July 2013

Nice. Have you filed a bug or otherwise reported it to them?

Nemo18:04, 25 July 2013

Wouldn't know where to report it. Added the hook according to this recipie. From my limited understanding of PHP this is harmless enough. My theory is that one step after that hook inserts the p-tags. And I don't want to remove all the Extensions to make sure whether it is the Mediawiki-engine, one of the extensions or the skin

Bgschaid (talk)19:30, 25 July 2013

i did't understand how you solved it, 4 November 2013

could you post more precisely how you did it?, 4 November 2013

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

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

There was/is consensus for use of LQT in more than one wiki, even if it scales poorly.

Helder23:50, 18 December 2012

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

Maybe voting is difficult in a traditional thread model, 7 February 2013

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

They can with traditional wikitext, but they can't with LQT.

Nemo17:56, 26 October 2013

Why is voting possible both on forums and with unstructured wikitext talkpages, but not with liquid threads?

Myrtonos (talk)08:48, 27 October 2013

I was replying to "threads can be distributed over multiple pages": they can't, with LQT, because you can't transclude LQT threads.

Nemo20:34, 27 October 2013

How to show LiquidThread properly when browser is toggled to MobileView on Android phone?

LiquidThread works gracefully on the Desktop view of my wiki site. But after I installed MobileFrontEnd extension and toggled the view to mobile, LiquidThread fails to show properly. This page is exactly what I saw about LiquidThread. http://m.mediawiki.org/wiki/LiquidThreads_Test_Page#What_is_your_preference_of_this_plugin.3F_18820

Can you help fix this issue and let LiquidThreads work also in mobile browsers?, 11 June 2013

Flow will work on mobile, and will be the successor to LiquidThreads.

Andrew Garrett (talk)02:29, 14 October 2013

Successor? Do you have a source for this claim? Terry said, when asked, «No. LiquidThreads will live or die on its own». The talk page of the page you linked says «LiquidThreads has nothing whatsoever to do with the new Flow system» (bold not added).

Nemo18:13, 14 October 2013

Update extension

Hi please update this extension and fix a bug which causes people who have not log in and there ip are visible and try to edit a tread wait ages and it won't save please fix that bug, 3 June 2013

LiquidThreads is mostly unmaintained, and has basically been abandoned in favor of making something else from scratch.

Jasper Deng (talk)19:15, 3 June 2013
  1. It's not true that the extension is mostly unmaintained. There is some maintaince work done in the last month. Please report your bug at bugzilla.
  2. The "making something else from scratch" is also not true. The development of the "new" LQT 3.0 was stopped because the developers didn't get around with LQT and started developing something other that doesn't has anything todo with LQT.
DaSch (talk)13:04, 9 June 2013
First page
First page
Previous page
Previous page
Last page
Last page