Extension talk:Wikilog

Latest comment: 6 years ago by Kghbln in topic Issue with MW 1.28 and later



Version 1.31 edit

Tested Wikilog on Mediawiki version 1.31 and it does not work. 5.29.23.15

Parse error: syntax error, WikilogUtils.php on line 100 edit

Continued in the 2010 archives. --Juliano 03:21, 11 February 2011 (UTC)Reply

asdasdasd

Namespace Restriction edit

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

Answered in the mailing list. --Juliano 19:23, 7 January 2011 (UTC)Reply
Got it; thanks --Enterprise user 22:47, 7 January 2011 (UTC)Reply

How to use Wikilog functions in Main Namespace? edit

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

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

I want to use Wikilog Comment function in All Namespace?How to use it? edit

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

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

[SOLVED] Dedicated User Blog edit

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

Use [[Blog:{{PAGENAME}}]] in the user page.
--Juliano 17:39, 19 January 2011 (UTC)Reply
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 {{#__USERNAME}}. I set $wgDefaultSideBarText to MediaWiki:Sidebar, and placed the link blog:{{#_USERNAME}} in my sidebar. --Enterprise user 17:56, 20 January 2011 (UTC)Reply

Extension namespace registration edit

Hi, perhaps you might want to register a namespace for this extension. Cheers --[[kgh]] 23:22, 25 March 2011 (UTC)Reply

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)Reply
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 --[[kgh]] 14:44, 28 March 2011 (UTC)Reply
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)Reply
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 --[[kgh]] 17:13, 31 March 2011 (UTC)Reply

How to enable e-mail notification for comments? edit

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

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)Reply
added to bugtracker here - feel free to extend it :-) --Erkan Yilmaz 16:25, 23 August 2011 (UTC)Reply

I second this request... how is one supposed to know that a comment has been posted in the case where they are moderated? Imagine the case of multiple blogs! 188.104.118.206 07:57, 4 March 2012 (UTC)Reply

Liquid Threads & Wikilog edit

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)Reply
I have posted a solution for excluding LiquidThreads from the namespace "Blog_talk" and thus avoiding a conflict between LiquidThreads and Wikilog: http://www.mediawiki.org/wiki/Extension_talk:LiquidThreads#Solution:_Exclude_LiquidThreads_from_certain_namespaces_.2F_avoid_conflict_with_Wikilog_17440 Kappa (talk) 15:39, 17 July 2012 (UTC)Reply

[SOLVED] PHP Error when creating blog page edit

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

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)Reply
Error is gone since Wikilog V1.1.2. Thanks! --Oliver Wieland 10:45, 20 September 2011 (UTC)Reply

thank you (for 3 years of blogging possibility) edit

Hello Natalie,

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

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)Reply
good news
if you need a guinea pig for the new version: ping me, --Erkan Yilmaz 16:03, 14 August 2011 (UTC)Reply

3 years and still happy :-) --Erkan Yilmaz (talk) 18:06, 11 March 2012 (UTC)Reply

Blog disappears edit

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)Reply
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)Reply
see the fix here, --Erkan Yilmaz 17:29, 26 August 2011 (UTC)Reply
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)Reply
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)Reply
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)Reply
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)Reply
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)Reply

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

New template parameter edit

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:

# Template parameters.
$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)Reply

publishedTime doesn't consider time zones edit

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

MW 1.18.0 Beta1 should be used with wikilog development branch edit

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

Renaming WlFeed edit

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

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)Reply
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 --[[kgh]] 21:00, 11 December 2011 (UTC)Reply
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)Reply
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 --[[kgh]] 16:13, 12 December 2011 (UTC)Reply

There you can find the field: "Create new wikilog article" (see 1st picture below) edit

Hello, I dont have this "field" / "button". What did I do wrong?

Any more info would be great, e.g.
What versions of Mediawiki, WikiLog(, pjhp, OS) do you use?
Perhaps a screenshot (or description which buttons are available)? --Erkan Yilmaz 16:40, 4 February 2012 (UTC)Reply
thank you for your fast reply!
I will send you a tinyurl but please dont post the original url here :o)
tinyurl.com/8yjqouw
I am using Mediawiki the actual version. I just updated a few days ago. In addition I am using Semantic Mediawiki, maybe this could cause problems(?)
I just installed the actual Wikilog Edition
(, pjhp, OS) dont know what u mean here
again thank you so much for your help which is highly appreciated!
  • Have a look at how I did it: here.
  • most of my questions I can answer when I visit your Spezial:Version page
  • pjhp is a typo: php
  • I assume you did all the install steps correct?
  • if you've generated a blog post you should see it also on this page: Spezial:Wikilog, --Erkan Yilmaz 17:40, 4 February 2012 (UTC)Reply
here is my specialpage: tinyurl.com/796ndwz
I mean this button here, which does not show up:  
I had the same problem after moving mediawiki from windows to ubuntu. After logging out and in the button showed up again. Maybe it works for you too. 187.75.2.16 13:56, 15 June 2012 (UTC)Reply

PROBLEM: blog don't display articles edit

Hello, I use MW 1.18.1 and last version of wikilog.

Blog:My_Blog is OK I created Blog:My_Blog/First_article, on Blog:My_Blog, wikilog menu tells me that there is one article not published, I click on the link, it displays a table with not published article: the table is empty.

I publish the article, adding --~~~~ or checking the checkbox, it doesn't show in the blog. Still "one article not published"

I used the "Create article" button to create Blog:My_Blog/Second_article. I writed it and signed with --~~~~. Not shown and the wikilog menu tells me that there is only ONE article not published. Where is the second one?!

--88.125.47.2 20:18, 30 March 2012 (UTC)Reply

Hi,
If you add something like {{wl-publish: 2012-06-17 00:00:00 +0000}} to the end of your article and save, does it get published? It may be some problem with the conversion of the Juliano (talk)-style signature to the actual markup.
Did you remember to actually create "Blog:My_Blog" page before the article page? You need to create a page, even if it contains just some <!-- comment -->, that is just to make Wikilog know that that wikilog exists.
--Juliano (talk) 20:46, 17 June 2012 (UTC)Reply

Tables in database are empty edit

When I created my Blog:My_blog, I got the "wikilog" tab to create a new article. I looked into the DB, and all wiki_wikilog_xxx tables are EMPTY.

What happen ? --Iubito (talk) 20:32, 2 April 2012 (UTC)Reply

It depends on the specific table you are looking at.
It is normal for some tables to stay empty until you create the front wikilog page, and then the first actual article.
--Juliano (talk) 20:46, 17 June 2012 (UTC)Reply

User permissions edit

Hi, is it possible to forbid anonymous user writing a blog article ? Thanks for an answer ! --hollosch (talk) 10:03, 5 June 2012 (UTC)Reply

Yes, this is not really specific of Wikilog, it is a standard MediaWiki feature.
Take a look at Manual:User rights.
--Juliano (talk) 20:50, 17 June 2012 (UTC)Reply

RSS Graffiti (RSS -> Facebook) links don't work edit

I had a problem of links to wikilog blogs from Facebook posts created with https://www.facebook.com/RSS.Graffiti not working. Below is a workaround from within Apache; I don't know enough about PHP / RSS to know if the problem is actually with RSS Gradditi or Wikilog. Just sharing this in case anyone else has the same problem.

# Fix Wikilog URLs in Facebook
RewriteEngine On
RewriteCond %{QUERY_STRING} title=Blog:Recipes&view=archives&show=published&feed=rss/pikans\.org/public/Blog:Recipes(.*)
RewriteRule ^/w/index\.php$ /w/index\.php?title=Blog:Recipes%1 [R=302,NE,L]
Hi,
I don't know RSS.Graffiti, but this URL is really broken. I had a look over at your feeds, and your MediaWiki installation appears to have something misconfigured. Take a look at the URLs that are appearing in your Atom feed:
<link rel="alternate" href="//pikans.org/public/Blog:Recipes" type="text/html" />
Note the missing "http:" in front of the URL? This shouldn't happen.
Without looking at your configuration, I can't guess why this is happening. I suggest you to try a new, pristine MediaWiki installation (using the installation Wizard), then install just the Wikilog in this new installation. If it works correctly, compare the new configuration side-by-side with your current one and try to spot anything suspicious.
--Juliano (talk) 20:55, 17 June 2012 (UTC)Reply

For some reason the "wikilog" tab is not working... edit

I am using mediawiki 1.18.4, I don't know why it isn't working, I need it to work so it is easier for editors to make blog posts rather than typing in the dirty url followed by "&action=wikilog". Any help will be much appreciated! --Muqman 52 (talk) 20:28, 18 June 2012 (UTC)Reply

VitaliyFilippov (talk) 12:52, 11 October 2013 (UTC) I understand your question was answered long time ago, but maybe you were just using some non-standard skin which doesn't have appropriate hook point?Reply

Bugs edit

We are currently running MediaWiki 1.18.4 and have run into a few bugs with this extension. The first one is a big issue, as Wikilog allows blocked users to add comments. At present we have no way to prevent spam bots and troublesome users from posting, we have even tried to block such troublesome edits with other extensions such as Extension:AbuseFilter, once the core software failed. It seems Wikilogs ignores any kind of restrictions and allows the comment to be posted.

The other issue is deleted comments, they leave a persistent comment just containing the footer (the user links etc.) and nothing else. Based on the styling guide and also some of the related MediaWiki messages, it should add a message stating the comment has been deleted and appended the class with -deleted. Neither of these are happening.

Finally, restoring a already deleted comment dose nothing to add it back into the comment section. It restores the original page it is parsed from, but does not add it back to the comments. Many thanks in advance. 81.98.7.19 00:08, 9 July 2012 (UTC)Reply

VitaliyFilippov (talk) 12:52, 11 October 2013 (UTC) The issue with blocking is actually very easy to solve, I've fixed it on github (see notice on the extension page). Comment deletion was also fixed - now comments without replies are deleted permanently and comments with replies are actually marked as deleted. Also in mediawiki4intranet version there is a {{wl-comment: [<parent>][ | <anon name>] }} parser function added to each comment (to backup comment metadata), so undeleted comments are readded to the page back. But it's problematic to put it in its previous place, because it at least requires tracking not only the page ID, but also a page title in the DB row of each removed parent comment. So now, the replies to a deleted comment aren't moved to its new reincarnation. But I don't think it's a big bug.Reply

Mediawiki 1.20.3 - Strict standards edit

With PHP 5.4.7, MySQL 5.5.27 and MediaWiki 1.20.3 I have this error message:

Strict Standards:
Declaration of WikilogWikiItemPage::newFromID() should be compatible with
WikiPage::newFromID($id, $from = 'fromdb') in .... on line 212

I assume this is for Strict standards enabled in PHP and different declaration of child Class but can't fix it by myself Tank you --Federicodip (talk) 11:30, 5 May 2013 (UTC)Reply

Hi,
at least you can mitigate this issue by applying the following patch to extensions/Wikilog/WikilogItemPage.php:
 Index: extensions/Wikilog/WikilogItemPage.php
 ===================================================================
 @@ -181,7 +181,7 @@
  	 * Constructor from a page ID.
  	 * @param $id Int article ID to load.
  	 */
 -	public static function newFromID( $id ) {
 +	public static function newFromID( $id, $from = '' ) {
  		$t = Title::newFromID( $id );
  		return $t == null ? null : new self( $t );
  	}
Kind regards, René Schwarz (talk) 06:08, 21 June 2013 (UTC)Reply
VitaliyFilippov (talk) 12:52, 11 October 2013 (UTC) I've also found this issue, and it's fixed in my modified version on github...Reply
--hollosch (talk) 02:22, 13 February 2014 (UTC) I've the same error at MW 1.22.2 - can you post the fixed version ? Thanks!Reply
VitaliyFilippov (talk) 07:27, 13 February 2014 (UTC) http://github.com/mediawiki4intranet/Wikilog, info at http://wiki.4intra.net/Wikilog. Also there's a link in the notice box at the top of the extension page :-)Reply

Manipulating title linkage edit

Hello,

I'm in dire need for the following situation: I don't want to have links in titles. Is this possible somehow? Or even to remove titles? I appreciate any help, I tried to look at wikilog.php, but I'm no programmer, so I can't hack it well enough. Thanks in advance! --146.52.16.109 09:15, 25 August 2013 (UTC)Reply

-> Never mind, sorry for the spam, discovered and followed the instructions for template inclusion on
http://www.mediawiki.org/wiki/Extension_talk:Wikilog/2009#Brilliant

VitaliyFilippov (talk) 12:52, 11 October 2013 (UTC) Didn't even understand what do you mean by "not having links in titles" :)Reply

Showing tags on a blog entry? edit

I've been poking around the options at the manual in hopes of finding a way to show tags on individual blog entries. I can easily show them on the blog page (list of several entries), or when embedding a wikilog, but I seem unable to show them on the blog post itself.

Am I missing a Mediawiki page? Any ideas?

--Aekki99 (talk) 13:21, 11 September 2013 (UTC)Reply

VitaliyFilippov (talk) 12:52, 11 October 2013 (UTC) Maybe you'll just use categories instead of tags?Reply

I can't use Shell. Other idea? edit

So I can't use these command, because there isn't ssh in my webserver(cPanel):

$ cd /path/to/mediawiki

$ php extensions/Wikilog/maintenance/wikilogImportDocumentation.php

Atomjani (talk) 11:11, 10 December 2013 (UTC)Reply

VitaliyFilippov (talk) 13:09, 10 December 2013 (UTC) You can manually upload xml dump (Special:Import) and all images (Special:Upload) from 'documentation' subfolder if you need docs.Reply

Can't create post edit

Hi, i use the wikilog extension from http://wiki.4intra.net/Wikilog, but it's not possible to create a new wikilog-title
Error: Invalid item name entered, it must be shoter!
Can you help me ?
--hollosch (talk) 01:24, 19 February 2014 (UTC)Reply

Hi, it seems to work. Thanks --hollosch (talk) 23:25, 19 February 2014 (UTC)Reply

Unknown table 'page' edit

Hello, following database error occurs at my installation:

Abfrage:
   SELECT page.* FROM `mw_wikilog_subscriptions`,`mw_page` WHERE ws_user = '4' AND ws_yes = '1' AND (page_id=ws_page) ORDER BY page_namespace, page_title LIMIT 20
   Funktion: SpecialWikilogSubscriptions::execute
   Fehler: 1051 Unknown table 'page' (databasename)

Backtrace:

  1. 0 /../www/wiki/includes/db/Database.php(1039): DatabaseBase->reportQueryError('Unknown table '...', 1051, 'SELECT page.* ...', 'SpecialWikilogS...', false)
  2. 1 /../www/wiki/includes/db/Database.php(1496): DatabaseBase->query('SELECT page.* ...', 'SpecialWikilogS...')
  3. 2 /../www/wiki/extensions/Wikilog/SpecialWikilogSubscriptions.php(75): DatabaseBase->select(Array, 'page.*', Array, 'SpecialWikilogS...', Array)
  4. 3 /../www/wiki/includes/SpecialPage.php(631): SpecialWikilogSubscriptions->execute(NULL)
  5. 4 /../www/wiki/includes/SpecialPageFactory.php(488): SpecialPage->run(NULL)
  6. 5 /../www/wiki/includes/Wiki.php(298): SpecialPageFactory::executePath(Object(Title), Object(RequestContext))
  7. 6 /../www/wiki/includes/Wiki.php(602): MediaWiki->performRequest()
  8. 7 /../www/wiki/includes/Wiki.php(467): MediaWiki->main()
  9. 8 /../www/wiki/index.php(49): MediaWiki->run()
  10. 9 {main}

--hollosch (talk) 23:01, 24 February 2014 (UTC)Reply

Thanks. that works! --hollosch (talk) 22:05, 5 March 2014 (UTC)Reply

Blank page / Special:WikilogComments edit

Hi, i get a blank page on the special page Spezial:WikilogComments - Any ideas to fix? --hollosch (talk) 23:01, 24 February 2014 (UTC)Reply

VitaliyFilippov (talk) 13:23, 25 February 2014 (UTC) Are there any PHP errors? Maybe in the php/apache error log?Reply
I found this error:
Catchable fatal error: Argument 1 passed to WikilogCommentPagerSwitcher::checkType() must be an instance of Title, null given, called in /../wiki/extensions/Wikilog/WikilogCommentsPage.php on line 133 and defined in /../wiki/extensions/Wikilog/WikilogCommentPagerSwitcher.php on line 12 --hollosch (talk) 22:07, 5 March 2014 (UTC)Reply
VitaliyFilippov (talk) 22:36, 5 March 2014 (UTC) Oh. Sorry. How could I miss that O_o. Fixed in master.Reply

Thanks, but when i switch to Thread view the error comes again, (other line):
Catchable fatal error: Argument 1 passed to WikilogCommentPagerSwitcher::setType() must be an instance of Title, null given, called in /../wiki/extensions/Wikilog/WikilogCommentsPage.php on line 130 and defined in /../wiki/extensions/Wikilog/WikilogCommentPagerSwitcher.php on line 22 --hollosch (talk) 22:44, 5 March 2014 (UTC)Reply
Ok... Check again. Now it should go away, and finally support switching list/thread view on Special:WikilogComments :) VitaliyFilippov (talk) 23:02, 5 March 2014 (UTC)Reply
New error after update: Fatal error: Call to a member function getRealName() on a non-object in /../wiki/extensions/Wikilog/WikilogUtils.php on line 304 --hollosch (talk) 23:09, 5 March 2014 (UTC)Reply
VitaliyFilippov (talk) 20:08, 6 March 2014 (UTC) This one is strange. Are you seeing it on the same page? (Special:WikilogComments)? My first guess is that it may be caused by a forbidden username (for example, one like IP: 1.1.1.1, or one with /, or one with #) in wikilog_comments.wlc_user_text database column. But I don't know how could it get there... :) Can you check that column in your DB for values that look incorrect? How many comments do you have in your wiki DB?Reply
Hi, yes, on the same site. No entries in zhe DB looks incorrect and there are not so much comments in DB... --hollosch (talk) 21:44, 6 March 2014 (UTC)Reply
VitaliyFilippov (talk) 22:19, 6 March 2014 (UTC) Can you install php5-xdebug extension and post a full stack trace here? (xdebug generates stacktraces on errors)Reply
Sorry, can't install that. MW runs on a managed server :-( --hollosch (talk) 07:26, 7 March 2014 (UTC)Reply
VitaliyFilippov (talk) 08:43, 10 March 2014 (UTC) Hm... What to do next... Can you initialize an empty mediawiki database and check for the same error on it? Or maybe your wiki is public - can you post the URL so I try to check the error by myself?..Reply
Hi, you can have a look here: Stadtwiki Geislingen - Error on this link: http://geislingen.org/wiki/index.php?title=Spezial:WikilogComments&comment_pager_type=list --hollosch (talk) 09:33, 10 March 2014 (UTC)Reply
VitaliyFilippov (talk) 13:37, 10 March 2014 (UTC) Ok, it helped :) the list view crashed on replies to comments posted by anonymous users. Fixed in master.Reply
Yeah, that works! Thanks a lot! --hollosch (talk) 14:27, 10 March 2014 (UTC)Reply

How to move comments correctly ? edit

How to move comments correctly which are at the wrong place (e.g. wrong place for answer of a comment)?
--hollosch (talk) 21:45, 22 June 2014 (UTC)Reply

It seems it's not possible by now, because Wikilog won't remove comment entry when removing the comment page... Maybe I'll add this feature. VitaliyFilippov (talk) 11:42, 27 June 2014 (UTC)Reply
This would be great, because Non-Wiki-User have often not the overview to post an answer or comment at the right place.
--hollosch (talk) 14:31, 27 June 2014 (UTC)Reply

Deactivate comments on sites edit

Hi, is it possible to deactivate the comments-function per page ?
--hollosch (talk) 20:41, 19 July 2014 (UTC)Reply

VitaliyFilippov (talk) 23:10, 29 November 2014 (UTC) Not yet. File issues on github for all feature requests, so at least I don't forget about them :)Reply

Recent version edit

Hi, what is the recent version of wikilog? Here on Mediawiki it is v1.3.0 an when installing from http://wiki.4intra.net/Wikilog version is 1.2.0. Or is there a newer one of http://wiki.4intra.net/Wikilog ? --109.192.64.131 11:24, 29 November 2014 (UTC)Reply

VitaliyFilippov (talk) 23:09, 29 November 2014 (UTC) Our one has more features - in this sense it's newer (details here https://github.com/mediawiki4intranet/Wikilog/blob/master/RELEASE-NOTES.mediawiki). There are no releases with version numbers though, there is only the master branch on github. It's not in wikimedia git because I dislike their mandatory review process (when I've tried it was taking a lot of time to make any change so I don't want to try anymore). I see some maintenance commits in wikimedia git, probably related to newer MW versions... I don't use mediawiki 1.22+ yet, so I don't know if anything is broken. Try and file issues on github if it is :)Reply

Catchable fatal error on MediaWiki 1.24 edit

I've just upgraded MediaWiki from 1.23 to 1.24. Till 1.23 Wikilog worked just fine. In 1.24, when trying to create new blog post (url: .../index.php?title=Blog:My_blog&action=wikilog) I get the following error:

Catchable fatal error: Argument 1 passed to Linker::makeImageLink() must be an instance of Parser, null given, 
called in .../wiki/includes/Linker.php on line 691 and defined in .../wiki/includes/Linker.php on line 546

Is this the end of this great extension?

--Ioannis Protonotarios 13:14, 6 December 2014 (UTC)Reply

VitaliyFilippov (talk) 13:46, 6 December 2014 (UTC) :) don't be such a pessimist :) I'll have a look at this error :)Reply
VitaliyFilippov (talk) 12:18, 8 December 2014 (UTC) Hm... I've just done a fresh install of MediaWiki 1.24 + Wikilog, and didn't experience this error on a test blog. Can you install php5-xdebug extension and post the stack trace that it will print?Reply
I am not sure wether to install it or not. I am on grid server in Media Temple and I've found some instructions here but it's something new for me and it feels a little scary, especially since I have almost 20 web sites up there. I need to study it first.
Nevertheless, it's good news that Wikilog works with a fresh install of 1.24! That means that the problem lies somewhere in my own installation. So, at first, I will update all extensions to most recent versions and if this fails to cure the problem I will start deactivating them one by one to find the one causing the error. If the error persists then I will install the debbuger for sure.
I will report back my progress here. Thank you so much for your time and effort! --Ioannis Protonotarios 16:05, 8 December 2014 (UTC)Reply
VitaliyFilippov (talk) 23:38, 8 December 2014 (UTC) In fact there's no guarantee that it's some of your extensions to blame. It may be a skin or even some specific wiki content triggering the bug...Reply

P.S.: A working workaround edit

I've just found a workaround that seems to work! Instead of creating a new blog post via the wikilog tab, try to create a new wiki page with title "Blog:My blog/My new post" where "My blog" would be the name of the blog you want to post into and "My new post" would be the title of your new post. The new page is recognised as new blog post because, as you will notice, there will be a "sign and publish" check box at the bottom. Tick this, save and voila!

--Ioannis Protonotarios 13:30, 6 December 2014 (UTC)Reply

Where is its canonical bugtracker? edit

There is https://phabricator.wikimedia.org/tag/mediawiki-extensions-wikilog/ (migrated from Wikimedia Bugzilla). There is also https://code.google.com/p/mediawiki-wikilog/issues/list linked from https://www.mediawiki.org/wiki/Extension:Wikilog . Please clarify.

Also, infobox on https://www.mediawiki.org/wiki/Extension:Wikilog links to a 1.2.0 tarball download. But "Latest version" says 1.3.0.

How to translate the main tabs? edit

The main tabs are always shown as "Blog" and "Wikilog" no matter which language I'm using, I tried changing the Wikilog.i18n.php Wikilog.i18n.alias.php and Wikilog.i18n.ns.php, none of them works Rinick (talk) 07:22, 17 February 2015 (UTC)Reply

VitaliyFilippov (talk) 14:59, 17 February 2015 (UTC) 'Wikilog' tab message is 'wikilog-tab' in Wikilog.i18n.php and it already has all the necessary translations. If you mean "Blog" is the namespace name then it's in Wikilog.i18n.ns.php (with a russian translation only). Of course you must change mediawiki UI language to see the translations.Reply

Rinick (talk) 06:32, 18 February 2015 (UTC) doesn't work for me, and I also registered a account on the demo site http://wiki.4intra.net changed language to ru and it still shows "Blog"Reply

VitaliyFilippov (talk) 07:06, 18 February 2015 (UTC) Hm..sorry. It seems it's the way mediawiki works with namespaces - they're always shown in the content language ($wgLanguageCode), regardless of the user setting. "Wikilog" tab is translated though...Reply

Namespaces conflict edit

Hi, firstly, pardon my english.
Secondly, ther is my problem. After that i installed successfully Wikilog, i installed another extension : Yet another simple calendar (https://github.com/improper/mediawiki-extensions-yasec).
At this moment, Wikilog just ceased to work, all links were gone as the "Wikilog" tab. After investigation, i discovered that the problem came from this part of the configuration code of the extension :
$wgExtraNamespaces = array(100 => "Event",101 => "Event_talk",); $wgNamespacesToBeSearchedDefault = array(NS_MAIN => true,100 => true,);
I tried to change the namespaces by 102 and 103 but it has no effects. But when i put these lines in comment, wikilog reappeared. Why there is a namespace conflict and how to fix it ?
Best regards and thanks in advance.
Valentin.--37.163.239.4 13:46, 9 April 2015 (UTC)Reply

I would first try to figure out exactly how you use your namespaces and the fix each extension to use a single number. To get the list use Special:PrefixIndex page, and the look at the HTML source code. You will see something like ... <option value="100">Admin</option><option value="101">Admin Discussion</option> ... . In one of my wikis, the old version of Wikilog runs fine with Wikilog::setupNamespace( 104, 'Blog', 'Blog_talk' ); - Daniel K. Schneider (talk) 09:42, 17 April 2015 (UTC)Reply

Cannot access protected property (MW 1.25) edit

MediaWiki 1.25beta (696dc35) 00:43, 9 April 2015 Wikilog 1.2.0 (7928276) 08:45, 21 January 2015 PHP 5.5.9-1ubuntu4.7

Fatal error: Cannot access protected property LinksUpdate::$mDb in /data/portails/wikitest/extensions/Wikilog/WikilogLinksUpdate.php on line 44

I changed protected to public, but it didn't help. Changing $lupd->$mDb to wfGetDB(DB_MASTER) did help, but then LinksUpdate::$mOptions failed.... i.e. the issue is probably related to either PHP 5.5.9 or the MW API. Since I am not a programmer I cannot figure out what's wrong. Don't even understand from where the static LinksUpdate function gets its &$lupd parameter.

The wiki is life online, but I soon will migrate existing wikis to this machine and then change its alias Now: http://tecfalx5.unige.ch/wt/Special:Version Later: http://edutechwiki.unige.ch/wt/Special:Version

Btw: This error also pops up when I install the version from Mediawiki.org and I also reported this bug in Github. Greetings and thanx for any help - Daniel K. Schneider (talk) 09:35, 17 April 2015 (UTC)Reply

Workaround edit

I ran into the same problem after updating MW from 1.22 to 1.25. More precisely, this error message popped up after trying to save an edit. I could get rid of this error message by updating to the current version of wikilog (master branch instead of REL1_25).

# change to your wiki extension directory
cd wiki/extensions

# move the original folder 
mv Wikilog WikilogGerrit

# fetch current version of wikilog (mine was from gerrit)
git clone https://github.com/mediawiki4intranet/Wikilog.git

# update database
cd ..
php maintenance/patchSql.php extensions/Wikilog/archives/fill-wikilog-comment-meta.sql
php maintenance/update.php  --quick

Cjahn (talk) 16:32, 28 May 2015 (UTC)Reply

This removed the error when working outside of the namespace Blog.

To make the wikilog work, i.e. creating new entries or moving entries, I applied the change from above, plus changing the $mOptions from protected to public in the file includes/deferred/SqlDataUpdate.php

In summary,

  1. change includes/deferred/SqlDataUpdate.php:38 from protected $mOptions = array(); to public $mOptions = array();
  2. change extensions/Wikilog/WikilogLinksUpdate.php:44 from $this->mDb = $lupd->mDb; to $this->mDb = wfGetDB(DB_MASTER);

I am not familiar in programming extensions for MediaWiki, but I was able to figure out the relevant files involved in producing this error

  1. includes/deferred/LinksUpdate.php
    144Hooks::run('LinksUpdate',...) (as part of the function doUpdate)
  2. includes/deferred/SqlDataUpdate.php
    35: protected $mDb;
    38: protected $mOptions = array();
  3. extensions/Wikilog/Wikilog.php
    72: 'WikilogLinksUpdate' => $dir . 'WikilogLinksUpdate.php',
  4. extensions/Wikilog/Wikilog.php
    174: $wgHooks['LinksUpdate'][] = 'WikilogLinksUpdate::LinksUpdate';
  5. extensions/Wikilog/WikilogLinksUpdate.php
    162: static function LinksUpdate( &$lupd ) {
    173: static function Links
    41: function __construct( &$lupd, $parserOutput ) {

Cjahn (talk) 20:32, 1 June 2015 (UTC)Reply

https://github.com/mediawiki4intranet/Wikilog ? edit

[Edited on nov 4]

After upgrading to 1.25 in September 2015, I disabled this extension and then forgot checking fixes. As of nov 2015, it seemed to work again on my wikis: 5.5.9-1ubuntu4.14 and 1.25.2 (9dd054c)

I took the code from Vitaliy's GitHub.

git clone https://github.com/mediawiki4intranet/Wikilog.git

The only thing that may have changed is the line in LocalSettings.php.

// Wikilog::setupNamespace( 104, 'Blog', 'Blog_talk' );
Wikilog::setupBlogNamespace( 104, 'Blog', 'Blog_talk' ); // SET 104 TO YOUR nameSPACE

However, I did not notice immediately: the discussion pages remain broken, i.e. a blank page appears when editing.

- cheers ! - Daniel K. Schneider (talk) 20:35, 3 November 2015 (UTC), changed 19:33, 4 November 2015 (UTC)Reply

"Constant NS_BLOG already defined" and other warnings edit

I have just installed the extension from git and I get the following warnings:

Notice: Constant NS_BLOG already defined in C:\wamp\www\commonplace2\extensions\Wikilog\Wikilog.php on line 269

Notice: Constant NS_BLOG_TALK already defined in C:\wamp\www\commonplace2\extensions\Wikilog\Wikilog.php on line 270

Warning: Cannot modify header information - headers already sent by (output started at C:\wamp\www\commonplace2\extensions\Wikilog\Wikilog.php:270) in C:\wamp\www\commonplace2\includes\WebResponse.php on line 37

Warning: Cannot modify header information - headers already sent by (output started at C:\wamp\www\commonplace2\extensions\Wikilog\Wikilog.php:270) in C:\wamp\www\commonplace2\includes\WebResponse.php on line 37

Warning: Cannot modify header information - headers already sent by (output started at C:\wamp\www\commonplace2\extensions\Wikilog\Wikilog.php:270) in C:\wamp\www\commonplace2\includes\WebResponse.php on line 37

How can I make them go away? Halfbeing (talk) 20:07, 4 February 2016 (UTC)Reply

Commenting and publishing settings not working edit

Has anyone else had an issue with certain configuration options in LocalSettings just not taking? Here's what I have:

require_once( 'extensions/Wikilog/Wikilog.php' );
define( "NS_DATANET", 3000 );
Wikilog::setupNamespace(NS_DATANET, 'DataNet', 'DataNet_talk' );
$wgWikilogEnableComments = true;
$wgWikilogSignAndPublishDefault = true;
$wgWikilogEnableTags = true;

It's the comments and publishing defaults that aren't coming through. Everything set up fine, the namespaces work, people are using it, but it's still defaulting commenting to the Talk page and it's still making people check the checkbox to publish entries. It's mostly annoyances at this point, but I'd really like to have at least commenting working as it's supposed to.

Rozzingit (talk) 21:40, 29 March 2016 (UTC)Reply

Exception on Special:Wikilog edit

I could not get this extension working on MW 1.27.1. Upgraded to MW 1.28 in a fresh install and the problem continues. I followed all the installation instructions normally.

I spent some time trying to detect the problem, which seems to be in the following line in SpecialWikiLog.php:

fields['wikilog'] = Xml::inputLabelSep(
                        $this->msg( 'wikilog-form-wikilog' )->text(), 
                        'wikilog', 'wl-wikilog', 40,
                        str_replace( '_', ' ', $opts->consumeValue( 'wikilog' ) )
                );

If I remove the "$this->msg( 'wikilog-form-wikilog' )->text()", the program continues until the next error. If not, I get an internal error message.

Could any of you please help me find what's wrong? I'm not a PHP expert neither know MW API.

--Mgbf (talk) 23:13, 2 March 2017 (UTC)Reply

I guess it is best to report the issue at GitHub. --[[kgh]] (talk) 12:34, 16 June 2017 (UTC)Reply

Issue with MW 1.28 and later edit

Now Wikilog stopped to work for me with MediaWiki 1.28.0. Here is the error message:

2017/01/02 17:33:51 [error] 3546#0: *7104 FastCGI sent in stderr: "PHP message: PHP Fatal error: Call to undefined method SkinVector::link() in /../w/extensions/Wikilog/WikilogItemPager.php on line 192" while reading response header from upstream, client: 31.210.180.196, server: withoutvowels.org, request: "GET /wiki/Blog:Main HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm-withoutvowels.sock:", host: "withoutvowels.org", referrer: "https://withoutvowels.org/wiki/Project:Donate"

Note that I have Vector and only Vector skin installed.

I guess it is best to report the issue [https://github.com/mediawiki4intranet/Wikilog/issues at GitHub}}. --[[kgh]] (talk) 12:34, 16 June 2017 (UTC)Reply
Return to "Wikilog" page.