Extension talk:LiquidThreads/2013

Feedback on LiquidThreads

Sweet (bitter?) numbers to crunch:

• 119 users reported 619 bugs
• 33 people discussed it on mailing lists
• 15 editors on w:de:Wikipedia Diskussion:LiquidThreads and 21 on w:de:Wikipedia Diskussion:WikiProjekt LiquidThreads and too many more to count

and now I got sick of it. Nemo 08:02, 17 February 2013 (UTC)

What would you like to say with this? DaSch (talk) 18:05, 17 February 2013 (UTC)

I was just wondering what order of magnitude was the number of people involved with discussing and debugging LQT, that's it.

For a moment I thought that maybe its problems annoyed only me, or that nobody cared except a handful users; but I see that e.g. while the majority of bug reports comes from a handful of reporters there's also a huge number of other involved people, especially in comparison to talk pages here. Nemo 18:59, 17 February 2013 (UTC)

I think that LQT is a great project and that many people think the same way, but because the WMF developer thought they could make a new version they started LQT 3.0 and took the development to them and then nearly killed the project because they are not grown up to it and now try to hold it down because they are afraid that it could show that other people could do a better job then they do and they are not worth their money.

And if you need help to with LQT I'd really love to help, I'm just not that good in coding ;) DaSch (talk) 19:34, 17 February 2013 (UTC)

Triaging bugs is also a useful activity, and maybe also track on bugzilla, from other discussion venues, issues that nobody never bothered to file as bugs... there are surely many and you know several languages we don't know anything about (as regards LQT).

Most helpful of course is code review, because there's nobody helping with LQT and being alone is a big deterrent for any developer, especially with such a complex extension that has been abandoned for so many years. Nemo 20:58, 17 February 2013 (UTC)

Bug Day focusing on triaging LiquidThreads bug reports

You are invited to join the next Bug Day tomorrow Mar 07. We will go through open reports filed against LiquidThreads. It is a good chance to learn about Bug management and meet the people working on a daily basis with the bug database. No MediaWiki expertise is actually required. There is work for everybody. See https://www.mediawiki.org/wiki/Bug_management/Triage/20130318 for more information. AKlapper (WMF) (talk) 14:51, 19 March 2013 (UTC)

Don't allow anons to use LiquidThreads

I'm trying to block anons from using LiquidThreads.

I tried the following three things (one after the other), but none of them worked:

$wgNamespaceProtection[NS_LQT_THREAD] =
$wgNamespaceProtection[NS_LQT_THREAD_TALK] =
$wgNamespaceProtection[NS_LQT_SUMMARY] =
$wgNamespaceProtection[NS_LQT_SUMMARY_TALK] = array('foo');
$wgGroupPermissions['*']['foo'] = false; // don't allow anons to access LQT namespaces

$wgNamespaceProtection[NS_LQT_THREAD] =
$wgNamespaceProtection[NS_LQT_THREAD_TALK] =
$wgNamespaceProtection[NS_LQT_SUMMARY] =
$wgNamespaceProtection[NS_LQT_SUMMARY_TALK] = array('foo');
$wgGroupPermissions['my_user_group']['foo'] = true; // only allow my_user_group to access LQT

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

The only thing that seems to work is

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

but I can't use it since I want to allow anons to edit certain other namespaces (which works fine).

Thanks for any help! Stefahn (talk) 14:12, 15 April 2013 (UTC)

Finally found a way to make this work:

I use Extension:Lockdown with this code:

$wgNamespacePermissionLockdown[NS_LQT_THREAD]['*'] = array('foo');
$wgNamespacePermissionLockdown[NS_LQT_THREAD_TALK]['*'] = array('foo');
$wgNamespacePermissionLockdown[NS_LQT_SUMMARY]['*'] = array('foo');
$wgNamespacePermissionLockdown[NS_LQT_SUMMARY_TALK]['*'] = array('foo');

Replace "foo" with the user group that you would like to grant permission to LQT. Stefahn (talk) 13:13, 20 August 2013 (UTC)

I've filled bug 53363 for this issue. This should be something configurable on LQT Ciencia Al Poder (talk) 19:38, 26 August 2013 (UTC)

Thanks.

Does somebody still fix LQT issues? I hope so since we use LQT a lot... Stefahn (talk) 08:20, 29 August 2013 (UTC)

Yes, there have been a lot of LQT bugs fixed during this year: [1] Ciencia Al Poder (talk) 09:22, 29 August 2013 (UTC)

In general: no, nobody maintains it. However, this year (as said above) we have had some very prolific weeks by volunteer Krenair whose patches, reviewed by translatewiki.net staff, fixed a lot of bugs. This doesn't mean that you can expect LQT to work with future releases of MediaWiki: it may, or not. Nemo 05:18, 30 August 2013 (UTC)

Thanks u2 for the clarification. Stefahn (talk) 13:54, 1 September 2013 (UTC)

Token is not set for normal users

I keep getting "Uncaught TypeError: Cannot read property 'token' of undefined load.php:23" wich causes to a endless load. Anyone found a workaround for this? YOUR1 (talk) 14:40, 16 May 2013 (UTC)

Is this still happening? Have you tried adding ?debug=true to the URL to see if there is a more specific error message in the browser's console? Helder 13:32, 4 June 2013 (UTC)

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 176.26.166.20 17:48, 3 June 2013 (UTC)

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 (UTC)

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 (UTC)

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

new thread notification?

how is working the new thread notification?

when a new thread is started what's up? who is noticed and it? and how can I change the default options about this behaviour?

sorry for my english

thx Raid (talk) 18:53, 11 June 2013 (UTC)

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? 128.227.176.138 20:03, 11 June 2013 (UTC)

Flow will work on mobile, and will be the successor to LiquidThreads. Andrew Garrett (talk) 02:29, 14 October 2013 (UTC)

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). Nemo 18:13, 14 October 2013 (UTC)

Database error

Hi all,

I tried to create the tables in PHPMyAdmin in the manner that is suggested in the documentation. Things look a bit different in my version, with some additional options being presented, which I left unchanged:

• character set: UTF-8 (default)
• NO_AUTO_VALUE_ON_ZERO is switched on
• SQL Mode (compatibility mode) is set to "None"

However, the following error message occurs:

CREATE INDEX thread_article_title ON /*$wgDBprefix*/thread(
thread_article_namespace,
thread_article_title,
thread_sortkey
);

MySQL [...]
#1071 - Specified key was too long; max key length is 1000 bytes 

Can anyone advise me what to do here? Cavila (MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2} 14:51, 4 July 2013 (UTC)

OK, to go by http://www.mediawiki.org/wiki/Extension%20talk%3ALiquidThreads/2011#c-IvanLanin-2011-04-30T06%3A05%3A00.000Z-Workaround_for_error_1071%3A_Specified_key_was_too_long_on_install this is a long-standing bug, which still requires a fix. Like Ivan, I was able to create the tables by abbreviating line 35, but this results in a database error message on the site.

P.S. The tables are automatically rendered in MyISAM (there's no other option in the panel as far as I can see). Cavila (MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2} 19:22, 4 July 2013 (UTC)

Another update. I've looked more closely into the latter database error. The message shown on the website (after the tables were created) reports missing database tables:

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
    SELECT 1 FROM `[prefix]_user_message_state` WHERE ums_user = '1' AND ums_read_timestamp IS NULL LIMIT 500 
from within function "NewMessages::newMessageCount". Database returned error "1146: Table '[nameofdatabase].[prefix]_user_message_state' doesn't exist (localhost)".

(The name of my database and the prefixes used are disguised here)

In other words, the tables could not be found, because it is expecting them to have the required prefixes in their names. I've added them manually and lo and behold, the extension is working! I'll update the documentation. Cavila (MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2} 09:34, 5 July 2013 (UTC)

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

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

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 (UTC)

Mystery solved: it's not the extension. It's the ParseBeforeTidy-hook recommended for Project Honeypot Bgschaid (talk) 13:31, 22 July 2013 (UTC)

Nice. Have you filed a bug or otherwise reported it to them? Nemo 18:04, 25 July 2013 (UTC)

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 (UTC)

i did't understand how you solved it 151.19.178.194 13:59, 4 November 2013 (UTC)

could you post more precisely how you did it? 151.19.178.194 14:00, 4 November 2013 (UTC)

I did not really "solve" it. The problem was introduced by the hook described in http://www.mediawiki.org/wiki/Manual:Combating_spam#Bad_Behavior_and_Project_HoneyPot

The "fix" was removing that hook Bgschaid (talk) 15:46, 4 November 2013 (UTC)

HoneyPot is not among the recommended methods anyway, as far as I know (if someone has positive experiences with it, please share on that page's talk). I added a warning there. Nemo 18:49, 5 November 2013 (UTC)

Sorry for the duplicate answer. When I had entered the first message it was not visible. Then I entered the second copy and when I didn't see that I gave up Bgschaid (talk) 20:51, 5 November 2013 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

"Edit" and "Delete" disappear

I added LQT to some of my content pages by adding {{#useliquidthreads:1}}.
This lets the "Edit" and "Delete" tabs disappear.
Is this usual behavior or a bug? Stefahn (talk) 10:40, 5 August 2013 (UTC)

It's expected behaviour, you'll now find them below whatever content there is in the actual talk page, now called "header". Nemo 12:56, 5 August 2013 (UTC)

Thanks for the info Nemo.

I hide the LQT header - that's why I didn't notice... Stefahn (talk) 10:00, 8 August 2013 (UTC)

ip editing

hi please fix an issues when editing in a ip because when you write a message and misspelt something or want to add more to the message you carnt because a little circle goes around for ever and then you just have to reply because you carnt edit the message it works when you are logged in but wont when using an ip address so please fix the issue 86.141.190.129 11:39, 12 August 2013 (UTC)

It would really help if you could give more information about your current configuration settings and version numbers. Jasper Deng (talk) 19:21, 12 August 2013 (UTC)

I am using it on here Mediawiki when I am using it on project support I carnt re edit my question it just loads and loads and doesent save but when your a user it works 86.141.190.129 10:09, 13 August 2013 (UTC)

Tested and reported as bug 52805 Ciencia Al Poder (talk) 17:11, 13 August 2013 (UTC)

thanks 86.169.208.191 09:01, 16 August 2013 (UTC)

Disabling "search terms"

Is there a way we can disable the "search terms" box? It would be useful for those of us not having the luxury of being able to install Lucene on the server. Sometime this week the searchbox temporarily disappeared from this website, so that got me wondering. Cavila (MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2} 08:36, 13 September 2013 (UTC)

Yes, it's a recent bugfix (10 days ago). You have to test the last version to see if it works for you too. Nemo 11:28, 13 September 2013 (UTC)

Thanks! I replaced $talkpageHeader .= $this->getSearchBox(); with the alternative code suggested by the patch and it works! Cavila (MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2} 12:46, 13 September 2013 (UTC)

Creating a thread from another extension

Hello, i'd like to be able to add a greeting to the newly created users from another extension. Is there a way to do so? 85.26.184.150 03:32, 21 September 2013 (UTC)

Does this example from WikiLove extension helps? Helder 12:38, 21 September 2013 (UTC)

Thanks, this helped a lot. 85.26.184.151 16:16, 22 September 2013 (UTC)

Cannot read property 'token' of undefined

Hello,

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;

85.26.186.92 04:59, 14 October 2013 (UTC)

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 85.26.184.152 05:37, 14 October 2013 (UTC)

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. Nemo 07:52, 14 October 2013 (UTC)

https://bugzilla.wikimedia.org/show_bug.cgi?id=55694 85.26.183.131 11:26, 14 October 2013 (UTC)

I'm getting the same error with the latest version of MediaWiki. Running on Windows Server 2012 R2 with MySQL. 66.148.137.66 17:12, 19 November 2013 (UTC)

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 94.34.114.25 18:33, 6 November 2013 (UTC)

Hi,

Did this get resolved? Even I am facing the same issue. Amitk75mw (talk) 12:06, 6 December 2013 (UTC)

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: [2]

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 (UTC)

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 (UTC)

Thank you for posting this, it resolved my issue too and we using LiquidThreads quite a bit. Fireflyt (talk) 16:45, 24 January 2014 (UTC)

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) 211.61.23.35 00:51, 21 November 2013 (UTC)

You should check your PHP error log file to see what error was happening when you got blank screens. Krenair ^{(talk • contribs)} 00:52, 21 November 2013 (UTC)