Extension talk:LiquidThreads

Archives

Archive 1 Archive 2

See also Talk:LiquidThreads 3.0/Design, Talk:LiquidThreads 3.0.

Previous page history was archived for backup purposes at Extension talk:LiquidThreads/LQT Archive 1 on 2015-07-10.

Don't use Manual:Combating_spam#Bad_Behavior_and_Project_HoneyPot together with LQT.

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?

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

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

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

i did't understand how you solved it

could you post more precisely how you did it?

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

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.

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

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?

This post was posted by Kappa~mediawikiwiki, but signed as Kappa.

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.

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.

define("NS_THREAD",90);
define("NS_THREAD_TALK",91);
$wgExtraNamespaces[NS_THREAD] = "Thread";
$wgExtraNamespaces[NS_THREAD_TALK] = "Thread_Talk";

This post was posted by Kappa~mediawikiwiki, but signed as Kappa.

Can you make screenshots?

screenshots of what?

Of how things look after removing LQT

I don' have a screenshot, but I can describe what happens: all contributions appear on pages of their own (pages and subpages, depending on the previous nesting). The look-and-feel of a thread on one page will be lost, but the texts of the individual contributions are saved.

This post was posted by Kappa~mediawikiwiki, but signed as Kappa.

I think this ( Extension talk:LiquidThreads ) is a very good discussion system like reddit? How can I install or add this discussion system to my wiki? Thanks.

Note that this talk page is not using LiquidThreads, but Structured Discussions

The supported alternative to this product is Extension:Flow

Hi All,

This extension looks really handy, and exactly the sort of thing I'd like to add to my wiki. I don't particularly want to take it though if it's unmaintained and we're being advised to not install on new instances.

Can anyone recommend the best supported replacement for LiquidThreads? Perhaps this was cancelled because it is/will be available natively in a newer version of MediaWiki?

Thanks

You can try Extension:Flow which is the discussion board you're using right now.

Thanks Ciencia!

I've only just seen this and that's exactly what I was looking for! :)

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;

This post was posted by 67.40.190.150, but signed as fox15rider.

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?

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?

I'd consider this bugzilla:26383.

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

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

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

This post was posted by Raid~mediawikiwiki, but signed as Raid.

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)

This post was posted by Kappa~mediawikiwiki, but signed as Kappa.

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?

This post was posted by Lieutenant S. Reznov, but signed as Inquisitor Ehrenstein.

There are lots of "404 (Not Found)" errors in the console when accessing that page.

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?

How can i hide thread list ('contents') in discussion page?

thanks.

This post was posted by Dgiim~mediawikiwiki, but signed as Dgiim.

I completed install liquid threads but I can't 'start new discussion' link. Exactly, when I click link, a circle-shaped wait indicator appeared in page, but the page ever pass to next phase.

I installed setted LocalSetting.php like this:

require_once("$IP/extensions/LiquidThreads/LiquidThreads.php");

and I runned update.php.

I'm using on Apache server on Windows 7 Professional with MySQL.

ps. Is it possible relationship with $wgHook setting? I'm newbie on mediawiki and server admin so I did nothing set about any hooks.

HELP ME PLEASE!!

This post was posted by Dgiim~mediawikiwiki, but signed as Dgiim.