Extension talk:Wikilog

Parse error: syntax error, WikilogUtils.php on line 100
Continued in the 2010 archives. --Juliano 03:21, 11 February 2011 (UTC)

Namespace Restriction
Is there a way to restrict the functionality of this extension so that it is only applied to certain namespaces or pages in MediaWiki? For example, would I be able to have Wikilog only function under the 'talk' namespace for registered users, or have it only apply to pages that belong to certain categories?

Thanks

--Enterprise user 20:14, 5 January 2011 (UTC)


 * Answered in the mailing list. --Juliano 19:23, 7 January 2011 (UTC)


 * Got it; thanks --Enterprise user 22:47, 7 January 2011 (UTC)

How to use Wikilog functions in Main Namespace?
Is there a way to use Wikilog fucnctions in Main Namespace or file Namespace ? --Iwikia 01:22, 14 January 2011 (UTC)


 * It may be possible, but such configuration is not supported. You may try adding NS_MAIN to $wgWikilogNamespaces, but this was never intended or tested. Use at your own risk. The extension was designed to operate on its own namespaces. It definitely won't work in the File/Image namespace, since that namespace has a specific handler that cannot coexist with the Wikilog handler.
 * --Juliano 14:09, 17 January 2011 (UTC)

I want to use Wikilog Comment function in All Namespace?How to use it?
Wikilog Comment is a nice disccussion function,I don't want to use other comment extension in my website,How to use Wikilog Comment in all Namespace?Thank you!

--Iwikia 01:22, 14 January 2011 (UTC)


 * As I said before, it is in the list of features to be considered, but it is considered of low importance, since it is out of the scope of the extension. The extension creates a blog in a wiki, the commenting interface is a bonus to make blog articles more interactive like traditional blogs. Other people showed interest in having the commenting interface in other articles, but this is beyond what Wikilog was intended for. There are other extensions, like LiquidThreads that already fill this niche. I know and I agree that LiquidThreads is bloated, and the simplicity of WikilogComments is attractive, that is why I'm considering the feature. But again, I have other high-priority features to implement and little free time to employ.
 * See: https://code.google.com/p/mediawiki-wikilog/issues/detail?id=10
 * --Juliano 14:15, 17 January 2011 (UTC)

[SOLVED] Dedicated User Blog
I'm attempting to setup my Wiki so that a recently created/logged in user will automatically have a dedicated blog; an alternative to having their own talk page. The only solution I've come up with thus far is to create an automatic link in the sidebar that retrieves the username and uses it in the title of a blog page. In other words, I would place a link similar to this in the sidebar:

http://www.mywiki.com/index.php/Blog:[$USERNAME]

The issue I'm finding is that MediaWiki, by default, doesn't provide a magic word for the retrieval of a username in its Wiki syntax. Does anyone have experience with, or know of a way by which I can retrieve the username of the logged in user for inclusion in a wikilog link?

Thanks --Enterprise user 17:21, 19 January 2011 (UTC)


 * Use  in the user page.
 * --Juliano 17:39, 19 January 2011 (UTC)


 * A possible alternative, but it somewhat defeats the purpose of placing the link in the Sidebar. Most of the users won't be spending time, or even exploring their user pages, and hence will be unaware of the link. A Sidebar link will be something they immediately observe regardless of where they are in the Wiki.


 * As a solution, I've decided to utilize the extension CustomSidebar, since it generates the magic word . I set $wgDefaultSideBarText to  , and placed the link   in my sidebar. --Enterprise user 17:56, 20 January 2011 (UTC)

Extension namespace registration
Hi, perhaps you might want to register a namespace for this extension. Cheers --&#91;&#91;kgh&#93;&#93; 23:22, 25 March 2011 (UTC)


 * Wikilog is designed so that the users are completely free to choose any namespace they want. The extension doesn't require any specific namespace. Even the number of namespaces is free: the extension is completely fine with one, two, three or even more namespaces configured as wikilog namespaces.-- I don't think we would get any benefit from registering namespaces, and may contribute for general user confusion instead.
 * --Juliano 19:52, 27 March 2011 (UTC)


 * Hi Juliano, actually it is quite good that it does not require a specific number for a namespace. This makes it flexible. However I have seen a couple of extensions here which suggest 100 as the number to use. On top the instructions for wiki specific namespaces suggests 100 too. Inexperienced admins might run into trouble here. A "registration" would at least block your suggestion for this extension and prevent other developers to use it. Still I might overdo it a bit at the moment. :) Cheers and thank you again for this cool extension. Cheers --&#91;&#91;kgh&#93;&#93; 14:44, 28 March 2011 (UTC)


 * Hi kgh. You are welcome. The number 100 is the first namespace number available for custom namespaces (see Manual:Using custom namespaces). From the little research I've done, it seems that there is little support for the namespace registry in Extension namespace registration from the MediaWiki developers. The whole idea of namespace numbers need to be revised. I'm quite divided about this. I do not want to make it look that Wikilog has a fixed namespace number, or that it only supports a single namespace assigned. I'll think about it. --Juliano 00:16, 31 March 2011 (UTC)


 * Hi Juliano, I agree entirely with you. This issue should have been treated with much more attention from the beginning to avoid the mess. Thankfully it is now picking up more and more attention. Yeah, your extension it special in many ways and thus I fully understand your hesitance. :) Perhaps it should be left as is until there is some kind of real problem and not a hypothetical one . Cheers --&#91;&#91;kgh&#93;&#93; 17:13, 31 March 2011 (UTC)

How to enable e-mail notification for comments?
How to enable e-mail notification for comments? --Корогодин Илья 20:06, 25 April 2011 (UTC)


 * Wikilog still doesn't offer a feature to watch and receive notifications when new comments are added. You can suggest this feature in the bugtracker. --Juliano 23:40, 26 April 2011 (UTC)
 * added to bugtracker here - feel free to extend it :-) --Erkan Yilmaz 16:25, 23 August 2011 (UTC)

Liquid Threads & Wikilog
Liquid Threads is installed across WMF's wikis, and is becoming popular outside WMF... It's not clear that Wikilog has been tested with Liquid Threads installed, as it's count of blog comments is always zero... could Liquid Threads be accommodated here? Thanks very much for the extension.... john


 * Wikilog comments are a intended to be a very simple and friendly interface for leaving comments on Wikilog posts, exactly like in normal blogs. Liquid Threads goes in the opposite direction, with full-featured interface for supporting long discussions between multiple people. Wikilog was not designed to be used with Liquid Threads, and will not support it.
 * --Juliano 21:58, 2 July 2011 (UTC)

[SOLVED] PHP Error when creating blog page
When I create a new blog page, I get thew following errors in apache's error.log: [Tue Jul 12 10:43:16 2011] [error] [client 10.49.20.149] PHP Warning: Illegal offset type in isset or empty in  /srv/www/mwiki/includes/Title.php on line 137, referer: http://tbwebface/mwiki/index.php?title=Blog:News&action=submit

[Tue Jul 12 10:43:16 2011] [error] [client 10.49.20.149] PHP Warning: trim expects parameter 1 to be string, array given in  /srv/www/mwiki/includes/Title.php on line 2591, referer: http://tbwebface/mwiki/index.php?title=Blog:News&action=submit

[Tue Jul 12 10:43:16 2011] [error] [client 10.49.20.149] PHP Fatal error: Call to a member function registerWatcher on a non-object in  /srv/www/mwiki/includes/parser/Parser.php on line 191, referer: http://tbwebface/mwiki/index.php?title=Blog:News&action=submit

Mediawiki 1.17 --Oliver Wieland 09:19, 12 July 2011 (UTC)
 * The last error message is similar to this bug report which I just had in MW 1.17.0, --Erkan Yilmaz 16:23, 23 August 2011 (UTC)
 * Error is gone since Wikilog V1.1.2. Thanks! --Oliver Wieland 10:45, 20 September 2011 (UTC)

thank you (for 2.5 years of blogging possibility)
Hello Juliano,

I just saw I'm using Wikilog for 2.5 years (now also with Mediawiki 1.17.0). Thanks for this goo dpiece of software. Keep on! --Erkan Yilmaz 05:06, 12 August 2011 (UTC)


 * You are welcome!
 * I've been neglecting Wikilog a little lately due to overwhelming amount of work, but I should be able to update it in a few months.
 * Thank you,
 * --Juliano 23:02, 12 August 2011 (UTC)
 * good news
 * if you need a guinea pig for the new version: ping me, --Erkan Yilmaz 16:03, 14 August 2011 (UTC)

Blog disappears
Hello,

first I want to say that my English is very bad, but I need a little Help with my Wikilog. I have installed the Wikilog after the description on this site. When I create a new Blog like Blog:Test I can edit and save the site. But there is only a blank site without any error message. I have tried to execute the update.php-script again and now there is the site available. Its everytime the same. When I update I can blog a post and I see it. But also when I want to comment a post there come a blank site. And this problem even can't solve with update.php. Can anyone help me? The version informations of my system are here: "MediaWiki 1.17.0, PHP 5.3.3-7+squeeze1 (apache2handler), MySQL 5.1.49-3"
 * Can you enable debugging? see here (my wikilog) - perhaps that shows you some specific errors. --Erkan Yilmaz 17:09, 26 August 2011 (UTC)
 * There comes this message

Fatal error: Call to a member function registerWatcher on a non-object in /var/www/ratswiki/includes/parser/Parser.php on line 191"
 * Im a really greenhorn. Can you help me to fix this problem? --84.185.139.55 17:28, 26 August 2011 (UTC)
 * see the fix here, --Erkan Yilmaz 17:29, 26 August 2011 (UTC)
 * first I want to thank you for your fast help. I have tried to delete the 4 rows from the WikilogCommentPager.php but know the error is also at the blog-pages which have worked after I use the update.php. --84.185.139.55 17:42, 26 August 2011 (UTC)
 * Then I guess you'll have to wait for dev feedback. e.g. add a note or a new report here.
 * (You are using the newest Wikilog 1.1.1? As I see also my php + mysql are lower versions than yours), --Erkan Yilmaz 17:50, 26 August 2011 (UTC)
 * In the second try deleting the 4 rows the comment-part of the problem is fixed. But the same error message came when i create a new blog-page. Here is a blank page like before. This part isn't fixed. I will follow the report on your linked site. Maybe there comes a new solution. thanks for your help --84.185.139.55 17:54, 26 August 2011 (UTC)
 * The Wikilog-Version from my special:version-page is "Wikilog (Version 1.1.99.1dev)"
 * here are official releases, I don't see yours there. So if you ask me, make a backup + try 1.1.1 --Erkan Yilmaz 17:59, 26 August 2011 (UTC)
 * done! but problem is still alive :) i have replaced all files ins extensions/wikilog with the 1.1.1-version-files and then i run the update.php. i will continue tomorrow. thanks erkan! --84.185.139.55 18:12, 26 August 2011 (UTC)

Solved!!! I have forgot to to the fix the first part in issue12 and add the line in the WikilogItemPager.php ... a really greenhorn mistake. Thank you for all.


 * This should be fixed now.
 * Wikilog 1.1.99.1dev is simply the current development version from hg or svn, a few things may be only partially implemented or not working completely. The current released version is 1.1.2.
 * --Juliano 03:37, 29 August 2011 (UTC)

New template parameter
I needed a template parameter which gives me a unique ID for each Wikilog entry. So I added the following line to WikilogItemPager.php, line 369: $vars = array(	'class'        => $divclass,	'wikilogTitle'  => $item->mParentName,	'wikilogPage'   => $item->mParentTitle->getPrefixedText,	'title'         => $item->mName,	'page'          => $item->mTitle->getPrefixedText,	'authors'       => $authors,	'tags'          => $tags,	'published'     => $item->getIsPublished ? '*' : ,	'pubdate'       => $pubdate, # Deprecated, to be removed on Wl 1.2.0.	'date'          => $publishedDate,	'time'          => $publishedTime,	'updated'       => $updated, # Deprecated, to be removed on Wl 1.2.0.	'updatedDate'   => $updatedDate,	'updatedTime'   => $updatedTime,	'summary'       => $wgParser->insertStripItem( $summary ),	'hasMore'       => $hasMore ? '*' : ,	'comments'      => $comments, /* New template parameter START */	'pageId'	=> $item->mID /* New template parameter END */ ); --Oliver Wieland 14:35, 20 September 2011 (UTC)
 * 1) Template parameters.

publishedTime doesn't consider time zones
Is it possible to consider the time zone which the actual user set in his settings? --Oliver Wieland 14:40, 20 September 2011 (UTC)

MW 1.18.0 Beta1 should be used with wikilog development branch
Note: Current MW version 1.18.0 Beta1 needs the installation of wikilog development branch. Wikilog 1.1.2 has some issues with this version, e.g. loading of comment pages is broken and some other php errors are produced. --Singlespeedfahrer 09:19, 7 November 2011 (UTC)

Renaming WlFeed
Heiya, I would like to suggest renaming "WlFeed" into something like "WikilogFeed" or "Wikilog - Feed". This would make their relation much more clear. Cheers --&#91;&#91;kgh&#93;&#93; 13:50, 11 December 2011 (UTC)


 * Hi,
 * There is already a class (and its corresponding file) named "WikilogFeed".
 * WlFeed is an utility sub-extension that is actually independent of Wikilog. The "Wl" prefix is rather arbitrary, it just denotes that it originally derived from Wikilog. WlFeed can be used by any other extension without any relation to or dependency on Wikilog. I could have named it "EnhancedFeedClasses" or something else, but I just kept "WlFeed" for simplicity. On the other hand, the WikilogFeed class is an actual part of Wikilog (hence the name), which uses WlFeed to render RSS and Atom feeds for wikilog pages.
 * In the future, I intend to also split the commenting code into another sub-extension, "WlComments" which, again, will be independent of Wikilog.
 * --Juliano 20:12, 11 December 2011 (UTC)


 * Heiya Juliano, that you for your detailed response which I appreciate a lot. Just by reading it I believe to rename it would be even more recommendable. Perhaps an independant extension page would be good too. I do not know how many people out there are aware that it may be used independently from Wikilog. It may be useful to them and so far the have only a minimum chance of detecting it. Cheers --&#91;&#91;kgh&#93;&#93; 21:00, 11 December 2011 (UTC)


 * Hello kgh,
 * Yeah, perhaps I could make WlFeed more visible. I just keep forgetting this mostly because WlFeed is not an extension that does anything that is user-visible... if you make an analogy with operating systems, WlFeed is like a library or shared object file (.DLL on Windows): the file itself does nothing for the user, it is used by other programs instead. Since WlFeed is virtually invisible to the end user, I never bothered creating a page for it (since it would only confuse most users).
 * But I don't know if I want to make a separate extension. I intend to maintain WlFeed as part of the Wikilog package to simplify my job (and to keep both Wikilog and WlFeed in the same Hg repository and the same directory in MediaWiki's SVN repo). Changes to WlFeed are motivated by changes on Wikilog, both also share the same version number and both are always updated and released together. This is why I want to keep them together.
 * Other extensions may still use WlFeed freely.
 * I originally intended to write a page for it, at Extension:Wikilog/WlFeed (and perhaps with a Extension:WlFeed redirect). I'll see if I do this in the following weeks.
 * About the name, I don't really see a problem with the current name. As I said, the "Wl" prefix is arbitrary, just to make a unique name for that component. I could have called it "JFeed" (the "J" is from my name), for example (except that "JFeed" is already the name of jQuery plugin). On the other hand, changing the name now may cause some problems, since the "WlFeed" is already recognized and registered at least in translatewiki.net. I'd rather keep the name as it is.
 * --Juliano 23:37, 11 December 2011 (UTC)


 * Heiya Juliano, I am getting to it right now. It is reasonable to do it like you did. A subpage with a redirect will be a good solution. I believe this makes WlFeed visible in the extension matrix and you could still treat this extension as one "extension organism". Another reason for not renaming it would also be that WlFeed is established under this name. I agree with you. Thank you for all this information and cheers --&#91;&#91;kgh&#93;&#93; 16:13, 12 December 2011 (UTC)