<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: MediaWiki - Nice to have</title>
	<atom:link href="http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/</link>
	<description>- weblog of Mizanur Rahman</description>
	<pubDate>Wed, 08 Feb 2012 08:48:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jeeny</title>
		<link>http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/comment-page-1/#comment-574</link>
		<dc:creator>jeeny</dc:creator>
		<pubDate>Wed, 30 Jul 2008 16:48:10 +0000</pubDate>
		<guid isPermaLink="false">http://booleandreams.wordpress.com/2007/03/23/mediawiki-nice-to-have/#comment-574</guid>
		<description>Hallo!
I dont know where to ask, i just searched google. I have installed mediawiki and i have some questions really about it. It is nice to have the right protect all pages from anonymos users read it, but i want just to protect one page, and it is a liitle stupid to protect all, and than allow to see all other without that one. I searched for solutions and installed patch, with allow only administrator or current user to see a tex written in
 {{ #ifeq: {{CURRENTUSER}} &#124; user &#124;  }}

it seemed to me really nice, but again, i protect current page from editing, but it show source on the page. so that text wich i was hidden is still seen for everyone.

please maybe you have some advise or you know where i can ask for it or help.</description>
		<content:encoded><![CDATA[<p>Hallo!<br />
I dont know where to ask, i just searched google. I have installed mediawiki and i have some questions really about it. It is nice to have the right protect all pages from anonymos users read it, but i want just to protect one page, and it is a liitle stupid to protect all, and than allow to see all other without that one. I searched for solutions and installed patch, with allow only administrator or current user to see a tex written in<br />
 {{ #ifeq: {{CURRENTUSER}} | user |  }}</p>
<p>it seemed to me really nice, but again, i protect current page from editing, but it show source on the page. so that text wich i was hidden is still seen for everyone.</p>
<p>please maybe you have some advise or you know where i can ask for it or help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: booleandreams</title>
		<link>http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/comment-page-1/#comment-572</link>
		<dc:creator>booleandreams</dc:creator>
		<pubDate>Mon, 21 May 2007 11:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://booleandreams.wordpress.com/2007/03/23/mediawiki-nice-to-have/#comment-572</guid>
		<description>hi Daniel
thanks for sharing your thoughts on the issue. i really liked your ideas and also agree with you on the notes. i know there are lots of extensions and hacks available for mediawiki and one problem i found is that some hacks or extensions do not work properly as version changes. they are too much version specific. so if something is build in with the software rather than adding any third party extension, that would have been nice.

thanks for sharing your knowledge and i believe we will be doing that in future too.

best regards
Mizan</description>
		<content:encoded><![CDATA[<p>hi Daniel<br />
thanks for sharing your thoughts on the issue. i really liked your ideas and also agree with you on the notes. i know there are lots of extensions and hacks available for mediawiki and one problem i found is that some hacks or extensions do not work properly as version changes. they are too much version specific. so if something is build in with the software rather than adding any third party extension, that would have been nice.</p>
<p>thanks for sharing your knowledge and i believe we will be doing that in future too.</p>
<p>best regards<br />
Mizan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Kinzler</title>
		<link>http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/comment-page-1/#comment-573</link>
		<dc:creator>Daniel Kinzler</dc:creator>
		<pubDate>Mon, 21 May 2007 09:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://booleandreams.wordpress.com/2007/03/23/mediawiki-nice-to-have/#comment-573</guid>
		<description>Hi there

1) Section protection is not possible, because sections are not a structural concept represented in the database. However, you can compose a page by including other pages into it (any page can be used as a template) - you can then protect the individual pages.

2) WYSIWYG is conceptually the wrong choice for wikis - there are too many things that can not be represented visually (like template inclusion, categories, etc). There is also the technical problem that most (if not all) in-browser rich-text editors are really edit HTML/DOM - which is not powerful enough to express MediaWiki markup (again, templates, magic words, etc).

However, it would be nice to make things easier for users - for example using the WYSIWYM concept (what you see is what you mean). WikEd seems a good start: it has syntax highlighting and could probably be enhanced to include some more what-you-get formating. For this and more, see http://meta.wikimedia.org/wiki/WYSIWYG

3) The usual solution to this is to save drafts as a subpage of your user page, or into some other special place, where it will not be included in searches, etc, per default. Using something like http://www.mediawiki.org/wiki/Extension:Lockdown, you can also hide namespaces from anonymous visitors - so you could make a "Drafts:" namespace. Lockdown is active on my website.

4) Using http://www.mediawiki.org/wiki/Extension:TalkHere, you can (ab)use the talk page as an easy to use comment system for articles. It's also active on my site

5) Some more AJAX stuff would be nice, though I personally would be even more interested in XSLT based page delivery - see http://brightbyte.de/page/Client-side_skins_with_XSLT for some ranting about this.

Regards,
Daniel</description>
		<content:encoded><![CDATA[<p>Hi there</p>
<p>1) Section protection is not possible, because sections are not a structural concept represented in the database. However, you can compose a page by including other pages into it (any page can be used as a template) - you can then protect the individual pages.</p>
<p>2) WYSIWYG is conceptually the wrong choice for wikis - there are too many things that can not be represented visually (like template inclusion, categories, etc). There is also the technical problem that most (if not all) in-browser rich-text editors are really edit HTML/DOM - which is not powerful enough to express MediaWiki markup (again, templates, magic words, etc).</p>
<p>However, it would be nice to make things easier for users - for example using the WYSIWYM concept (what you see is what you mean). WikEd seems a good start: it has syntax highlighting and could probably be enhanced to include some more what-you-get formating. For this and more, see <a href="http://meta.wikimedia.org/wiki/WYSIWYG" rel="nofollow">http://meta.wikimedia.org/wiki/WYSIWYG</a></p>
<p>3) The usual solution to this is to save drafts as a subpage of your user page, or into some other special place, where it will not be included in searches, etc, per default. Using something like <a href="http://www.mediawiki.org/wiki/Extension:Lockdown" rel="nofollow">http://www.mediawiki.org/wiki/Extension:Lockdown</a>, you can also hide namespaces from anonymous visitors - so you could make a &#8220;Drafts:&#8221; namespace. Lockdown is active on my website.</p>
<p>4) Using <a href="http://www.mediawiki.org/wiki/Extension:TalkHere" rel="nofollow">http://www.mediawiki.org/wiki/Extension:TalkHere</a>, you can (ab)use the talk page as an easy to use comment system for articles. It&#8217;s also active on my site</p>
<p>5) Some more AJAX stuff would be nice, though I personally would be even more interested in XSLT based page delivery - see <a href="http://brightbyte.de/page/Client-side_skins_with_XSLT" rel="nofollow">http://brightbyte.de/page/Client-side_skins_with_XSLT</a> for some ranting about this.</p>
<p>Regards,<br />
Daniel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: booleandreams</title>
		<link>http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/comment-page-1/#comment-571</link>
		<dc:creator>booleandreams</dc:creator>
		<pubDate>Wed, 28 Mar 2007 10:45:34 +0000</pubDate>
		<guid isPermaLink="false">http://booleandreams.wordpress.com/2007/03/23/mediawiki-nice-to-have/#comment-571</guid>
		<description>Hi Marcel
Thanks for the information.  As i told you those are extensions build by developers and this particular extension is a good one that we can look for. my point was to have this functionality build in with MediaWiki. MediaWiki have page protection functionality and they can enhance that to perform more protection option here.

thanks for your post and also participating in the discussion

regards
Mizan</description>
		<content:encoded><![CDATA[<p>Hi Marcel<br />
Thanks for the information.  As i told you those are extensions build by developers and this particular extension is a good one that we can look for. my point was to have this functionality build in with MediaWiki. MediaWiki have page protection functionality and they can enhance that to perform more protection option here.</p>
<p>thanks for your post and also participating in the discussion</p>
<p>regards<br />
Mizan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcel de Ruiter</title>
		<link>http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/comment-page-1/#comment-570</link>
		<dc:creator>Marcel de Ruiter</dc:creator>
		<pubDate>Tue, 27 Mar 2007 21:26:21 +0000</pubDate>
		<guid isPermaLink="false">http://booleandreams.wordpress.com/2007/03/23/mediawiki-nice-to-have/#comment-570</guid>
		<description>Hi Mizan,

At work we use: http://meta.wikimedia.org/wiki/PageProtection

I have not much experience with it but "the guys" seem comfortable with it.

Hope it helps.

Best regards,

Marcel</description>
		<content:encoded><![CDATA[<p>Hi Mizan,</p>
<p>At work we use: <a href="http://meta.wikimedia.org/wiki/PageProtection" rel="nofollow">http://meta.wikimedia.org/wiki/PageProtection</a></p>
<p>I have not much experience with it but &#8220;the guys&#8221; seem comfortable with it.</p>
<p>Hope it helps.</p>
<p>Best regards,</p>
<p>Marcel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: booleandreams</title>
		<link>http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/comment-page-1/#comment-569</link>
		<dc:creator>booleandreams</dc:creator>
		<pubDate>Fri, 23 Mar 2007 23:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://booleandreams.wordpress.com/2007/03/23/mediawiki-nice-to-have/#comment-569</guid>
		<description>hi Marcel
It will be really nice to look at your example. what i found so far in MediaWiki, we cant actually protect any particular section. if you click the edit link of a section and in that edit page you click protect link at the top, it actually protect the whole page not the particular section. What i am looking for user based protection not even user group based protection. Like i have an section which only me and Sysop can change no one else. So let me know about the solution you have for it.

i found one solution where they implemented it by hacking the code.

http://www.thejackol.com/2007/02/16/disable-anonymous-editing-in-mediawiki/

but its not in build in MediaWiki. We can hack lots of things but there are few things those should be included within the software. ;)

thanks
Mizan</description>
		<content:encoded><![CDATA[<p>hi Marcel<br />
It will be really nice to look at your example. what i found so far in MediaWiki, we cant actually protect any particular section. if you click the edit link of a section and in that edit page you click protect link at the top, it actually protect the whole page not the particular section. What i am looking for user based protection not even user group based protection. Like i have an section which only me and Sysop can change no one else. So let me know about the solution you have for it.</p>
<p>i found one solution where they implemented it by hacking the code.</p>
<p><a href="http://www.thejackol.com/2007/02/16/disable-anonymous-editing-in-mediawiki/" rel="nofollow">http://www.thejackol.com/2007/02/16/disable-anonymous-editing-in-mediawiki/</a></p>
<p>but its not in build in MediaWiki. We can hack lots of things but there are few things those should be included within the software. <img src='http://www.mizanurrahman.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /><br />
thanks<br />
Mizan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcel de Ruiter</title>
		<link>http://www.mizanurrahman.com/2007/03/23/mediawiki-nice-to-have/comment-page-1/#comment-568</link>
		<dc:creator>Marcel de Ruiter</dc:creator>
		<pubDate>Fri, 23 Mar 2007 22:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://booleandreams.wordpress.com/2007/03/23/mediawiki-nice-to-have/#comment-568</guid>
		<description>Hi Mizan,

If I understood correctly the wish under 1 (section protection) is really already possible. We have it at work, with some features on who can edit). I will check it out and come back to you later next week.

Best regard,
Marcel</description>
		<content:encoded><![CDATA[<p>Hi Mizan,</p>
<p>If I understood correctly the wish under 1 (section protection) is really already possible. We have it at work, with some features on who can edit). I will check it out and come back to you later next week.</p>
<p>Best regard,<br />
Marcel</p>
]]></content:encoded>
	</item>
</channel>
</rss>

