Extension talk:LiquidThreads

From MediaWiki.org
Jump to: navigation, search
Start a new discussion

Contents

Thread titleRepliesLast modified
Why I hate LiquidThreads823:53, 7 April 2014
force-refresh a discussion page?719:36, 31 March 2014
General Threads Overview618:26, 12 March 2014
How to fully uninstall LQT? 220:57, 6 March 2014
Database Error710:28, 28 February 2014
Internal error for Special:NewMessages112:16, 13 February 2014
Infinite ajax loader (again)416:45, 24 January 2014
How to uninstall LiquidThreads ?100:52, 21 November 2013
Cannot read property 'token' of undefined417:12, 19 November 2013
[RESOLVED] Edit/History/Delete on top of each other (paragraph inserted)807:21, 6 November 2013
Why was the development cancelled?820:34, 27 October 2013
How to show LiquidThread properly when browser is toggled to MobileView on Android phone?218:13, 14 October 2013
Update extension302:29, 14 October 2013
Creating a thread from another extension216:16, 22 September 2013
Disabling "search terms"212:46, 13 September 2013
Don't allow anons to use LiquidThreads613:54, 1 September 2013
ip editing409:01, 16 August 2013
"Edit" and "Delete" disappear210:00, 8 August 2013
Database error209:34, 5 July 2013
new thread notification?018:53, 11 June 2013
First page
First page
Previous page
Previous page
Last page
Last page

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

Exactly!

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
 

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
 
 
 
 
 

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 1.8.0.5, SF 2.5.4)07:36, 2 March 2014

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

SELECT *
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:

https://github.com/GeneralVolkoV/LiquidThreadsOverview

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 1.8.0.5, 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

66.109.35.13019:05, 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?

66.109.35.13013:25, 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)
210.89.56.3806:47, 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

Backtrace:

#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 1.8.0.5, 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:

https://git.wikimedia.org/commitdiff/mediawiki%2Fextensions%2FLiquidThreads/3680e12bd1cd5372c6a57abbc2b03800bfc1bee4

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 1.8.0.5, 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

94.34.114.2518:33, 6 November 2013

Hi,

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)

211.61.23.3500:51, 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

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.9204:59, 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

85.26.184.15205:37, 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.

66.148.137.6617:12, 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

151.19.178.19413:59, 4 November 2013

could you post more precisely how you did it?

151.19.178.19414:00, 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

75.112.161.13004:08, 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?

128.227.176.13820:03, 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

176.26.166.2017:48, 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
 

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.15003:32, 21 September 2013

Does this example from WikiLove extension helps?

Helder12:38, 21 September 2013

Thanks, this helped a lot.

85.26.184.15116:16, 22 September 2013
 
 

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

Yes, it's a recent bugfix (10 days ago). You have to test the last version to see if it works for you too.

Nemo11:28, 13 September 2013

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
 
 

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

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

I've filled bug 53363 for this issue. This should be something configurable on LQT

Ciencia Al Poder (talk)19:38, 26 August 2013

Thanks.

Does somebody still fix LQT issues? I hope so since we use LQT a lot...

Stefahn (talk)08:20, 29 August 2013

Yes, there have been a lot of LQT bugs fixed during this year: [1]

Ciencia Al Poder (talk)09:22, 29 August 2013
 

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.

Nemo05:18, 30 August 2013

Thanks u2 for the clarification.

Stefahn (talk)13:54, 1 September 2013
 
 
 
 
 

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.12911:39, 12 August 2013

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

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.12910:09, 13 August 2013

Tested and reported as bug 52805

Ciencia Al Poder (talk)17:11, 13 August 2013

thanks

86.169.208.19109:01, 16 August 2013
 
 
 
 

"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

It's expected behaviour, you'll now find them below whatever content there is in the actual talk page, now called "header".

Nemo12:56, 5 August 2013

Thanks for the info Nemo.
I hide the LQT header - that's why I didn't notice...

Stefahn (talk)10:00, 8 August 2013
 
 

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

OK, to go by http://www.mediawiki.org/wiki/Thread:Extension_talk:LiquidThreads/Workaround_for_error_1071:_Specified_key_was_too_long_on_install#Workaround_for_error_1071:_Specified_key_was_too_long_on_install_3612 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

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
 
 

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
First page
First page
Previous page
Previous page
Last page
Last page