<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Requests and Ideas (new posts)</title>
		<link>http://www.wikidot.org/forum/c-28017/requests-and-ideas</link>
		<description>Posts in the forum category &quot;Requests and Ideas&quot; - Feature requests and ideas for developers.</description>
				<copyright></copyright>
		<lastBuildDate></lastBuildDate>
		
					<item>
				<guid>http://www.wikidot.org/forum/t-39387#post-245463</guid>
				<title>cleanly separate dis-allowed menu options: Re: cleanly separate dis-allowed menu options -- and more -- and &#039;if&#039;</title>
				<link>http://www.wikidot.org/forum/t-39387/cleanly-separate-dis-allowed-menu-options#post-245463</link>
				<description></description>
				<pubDate>Mon, 25 Aug 2008 15:03:25 +0000</pubDate>
				<wikidot:authorName>spir</wikidot:authorName>				<wikidot:authorUserId>179225</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Can we think at an overall separation or hiding for things that that user aren't allowed to see / follow / use. Such as nav entries, edit+ buttons, links to page. I would be happy if all of this would be grayed, rather than hidden, so that people would</p> <ol> <li>get familiar to it and</li> <li>be 'pulled' to join.</li> </ol> <p>To do it simply, this may lead to a conditional statement, that is an <strong>if</strong>. This would be used to test system variables such as :<br /> [[if %user.status="member"]]<br /> <a class="newpage" href="http://www.wikidot.org/meta:organisation">organisation</a><br /> [[/if]]<br /> [[if %user.status&lt;&gt;"member"]]<br /> [grey]<br /> <a class="newpage" href="http://www.wikidot.org/meta:organisation">organisation</a><br /> [/grey]<br /> [[/if]]<br /> (the meta-pages about the wiki's organisation are opened only to members)<br /> No matter if greyed links look more or less like unexisting links.</p> <p>denis</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-39387#post-245453</guid>
				<title>cleanly separate dis-allowed menu options: Re: cleanly separate dis-allowed menu options</title>
				<link>http://www.wikidot.org/forum/t-39387/cleanly-separate-dis-allowed-menu-options#post-245453</link>
				<description></description>
				<pubDate>Mon, 25 Aug 2008 14:51:41 +0000</pubDate>
				<wikidot:authorName>spir</wikidot:authorName>				<wikidot:authorUserId>179225</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <h3><span>Michal :</span></h3> <p>I don't really understand your answer.</p> <ul> <li>The link you provide [<a href="http://www.wikidot.org/doc:wiki-syntax#toc45">http://www.wikidot.org/doc:wiki-syntax#toc45</a>] leads to the "include" feature paragraph.</li> <li>"You can use a [[button]] to show individual page options" ? I used the [[button]] for changing the edit menu, but this for all users. How does it allow to adapt a menu or anything to individual users' permissions ?</li> </ul> <h3><span>Matt :</span></h3> <p>wikidot.org is dedicated to the open-source delivering of wikidot software — which also allows you to install it on a personal server<br /> dev.wikidot.org is a section on which is talket about the (open) developement of wikidot</p> <p>denis</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-65829#post-187449</guid>
				<title>Tags Suggest: Tags Suggest</title>
				<link>http://www.wikidot.org/forum/t-65829/tags-suggest#post-187449</link>
				<description></description>
				<pubDate>Mon, 09 Jun 2008 11:24:51 +0000</pubDate>
				<wikidot:authorName>Giovanni Savastano</wikidot:authorName>				<wikidot:authorUserId>106332</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Hi all,<br /> I'm trying to implement some new features in wikidot v1<br /> one of these is "tags suggest". this feature works as usersearch do. while you type a tag in the form PageTagsModule, it "suggest" you what similar tags you have already used in other pages.</p> <p>this is the main function (a poor copy&amp;past&amp;modify from PageLookupQModule….):</p> <div class="code"> <pre> <code>class TagsLookupQModule extends QuickModule { public function process($data){ // does not use data $search = $_GET['q']; $siteId = $_GET['s']; if(!is_numeric($siteId)) return; if($search == null || strlen($search) ==0) return; $search1 = pg_escape_string(preg_quote($search)); $search2 = pg_escape_string($search); Database::init(); $q1 = "SELECT tag, tag_id FROM page_tag WHERE " . "tag ~* '^$search1' AND tag != '$search2' AND site_id = '$siteId'"; $q1 .= "ORDER BY tag LIMIT 20"; $q2 = "SELECT tag, user_id FROM page_tag WHERE " . "tag = '$search2' AND site_id ='$siteId'"; $db = Database::connection(); $result1 = $db-&gt;query($q1); $result1 = $result1-&gt;fetchAll(); $result2 = $db-&gt;query($q2); $result2 = $result2-&gt;fetchAll(); if($result1 == null &amp;&amp; $result2 != null) $result = $result2; if($result2 == null &amp;&amp; $result1 != null) $result = $result1; if($result1 != null &amp;&amp; $result2 != null){ $result = array_merge($result2, $result1); } return array('tags' =&gt; $result); } }</code> </pre></div> <p>now I need to modify PageTagsModule.js in order to allow search operation.<br /> anyone can help me? I think this feature would be very usefull for everyone.</p> <p>thanks,<br /> Gio</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-57842#post-157622</guid>
				<title>add markdown support: add markdown support</title>
				<link>http://www.wikidot.org/forum/t-57842/add-markdown-support#post-157622</link>
				<description></description>
				<pubDate>Mon, 05 May 2008 01:09:04 +0000</pubDate>
				<wikidot:authorName>thomasn</wikidot:authorName>				<wikidot:authorUserId>122915</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Markdown — see Wikipedia — is becoming really well supported, with loads of tools to convert to (and in some cases from) HTML, PDF, LaTeX, DocBook, groff etc etc. This makes it a great choice as a standard doc format, much easier to write than an XML dialect, and also a good choice as a simple wiki format.</p> <p>You can see some of the available engines in action at<br /> <a href="http://babelmark.bobtfish.net/?markdown=++*+foo%0D%0A%0D%0Abar">http://babelmark.bobtfish.net/?markdown=++*+foo%0D%0A%0D%0Abar</a> ,<br /> or have a look at the converter at <a href="http://johnmacfarlane.net/pandoc/try">http://johnmacfarlane.net/pandoc/try</a></p> <p>The PHP implementation is one of the most solid. Is there any interest in adding an option to use the portable Markdown syntax instead of the (probably more powerful) Wikidot syntax?</p> <p>— Thomas.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-55023#post-153724</guid>
				<title>Editing Meta Tags: Re: Editing Meta Tags</title>
				<link>http://www.wikidot.org/forum/t-55023/editing-meta-tags#post-153724</link>
				<description></description>
				<pubDate>Mon, 28 Apr 2008 10:36:45 +0000</pubDate>
				<wikidot:authorName>mccalleyt</wikidot:authorName>				<wikidot:authorUserId>119395</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I as well would like to see the possibility of editing meta tags for Google's Webmaster tools.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-55023#post-150157</guid>
				<title>Editing Meta Tags: Editing Meta Tags</title>
				<link>http://www.wikidot.org/forum/t-55023/editing-meta-tags#post-150157</link>
				<description></description>
				<pubDate>Tue, 22 Apr 2008 14:18:32 +0000</pubDate>
				<wikidot:authorName>thevisitor</wikidot:authorName>				<wikidot:authorUserId>95668</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>It would be really nice to have some way of editing the META tags. Yes, they may be abused at times by spammers. And no: they aren't dead, or completely ignored by search engines.</p> <p>One particular area where they would be useful, are the Google Webmaster Tools. The functionality seems very similar to the one for Google Analytics - you get a key, and the system makes a simple tag out of it. So for starters, it could be adapted from that '3rd party tool'. (Also note that there are many people screaming for it over at <a href="http://community.wikidot.com/forum/t-7625/google-webmaster-tools">wikidot forums</a>.)</p> <p>I would be happy if the Webmaster Tools were available. But the general capability to edit Meta tags would be very useful by itself.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-49506#post-132952</guid>
				<title>Expand QueryString variables in templates: Expand QueryString variables in templates</title>
				<link>http://www.wikidot.org/forum/t-49506/expand-querystring-variables-in-templates#post-132952</link>
				<description></description>
				<pubDate>Fri, 28 Mar 2008 00:43:10 +0000</pubDate>
				<wikidot:authorName>Witness</wikidot:authorName>				<wikidot:authorUserId>94315</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Hi, templates can expand variables passed in like {$number_books}. Would be helpful to be able to link to a template page passing variables in a LINK, like mypage?num_books=20. This way, template can be used as is filling necessary info in a link. Say I have a page that is good for a number of stocks but has some elements that depend on a stock symbol. I can define it as a template but I need to create a separate page for each stock just to pass in symbol as a parameter. It would be nice if I can do that in a link reference directly.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-39387#post-111446</guid>
				<title>cleanly separate dis-allowed menu options: Re: cleanly separate dis-allowed menu options</title>
				<link>http://www.wikidot.org/forum/t-39387/cleanly-separate-dis-allowed-menu-options#post-111446</link>
				<description></description>
				<pubDate>Thu, 21 Feb 2008 18:54:55 +0000</pubDate>
				<wikidot:authorName>Gabrys</wikidot:authorName>				<wikidot:authorUserId>2462</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I believe Wikidot.org is about the software and DEV.wikidot.com is about the team (developers). And it may seem that is more about v2 than v1.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-39387#post-102886</guid>
				<title>cleanly separate dis-allowed menu options: Re: cleanly separate dis-allowed menu options</title>
				<link>http://www.wikidot.org/forum/t-39387/cleanly-separate-dis-allowed-menu-options#post-102886</link>
				<description></description>
				<pubDate>Wed, 06 Feb 2008 00:02:29 +0000</pubDate>
				<wikidot:authorName>Matt Wilkie</wikidot:authorName>				<wikidot:authorUserId>70840</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Thank you Michal, the buttons will help.</p> <p>Re: dev.wikidot.org, what is the (intended) difference between that wiki and this one? I was under the impression that dev was for v2 and this one is for v1. Am I mistaken?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-39387#post-101905</guid>
				<title>cleanly separate dis-allowed menu options: Re: cleanly separate dis-allowed menu options</title>
				<link>http://www.wikidot.org/forum/t-39387/cleanly-separate-dis-allowed-menu-options#post-101905</link>
				<description></description>
				<pubDate>Mon, 04 Feb 2008 09:59:32 +0000</pubDate>
				<wikidot:authorName>michal frackowiak</wikidot:authorName>				<wikidot:authorUserId>1</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>You can use a [[button]] to show individual page options. Moreover, you could add several buttons into your side-bar, or add them manually at the bottom of a page.</p> <p><a href="http://www.wikidot.org/doc:wiki-syntax#toc45">http://www.wikidot.org/doc:wiki-syntax#toc45</a></p> <p>Ups. There is no option to add a "discuss" button. Something that could be added indeed — and it should be done by adding options to the <a href="http://svn.wikidot.org/svn/showfile.svn?path=%2fwikidot1%2ftrunk%2flib%2fText_Wiki%2fText%2fWiki%2fRender%2fXhtml%2fButton.php&amp;revision=HEAD&amp;name=wikidotorg">lib/Text_Wiki/Wiki/Render/Xhtml/Button.php</a> file. But other buttons should work fine.</p> <p>And yes, I <span style="text-decoration: underline;">am</span> trying to invite everyone to <a href="http://dev.wikidot.org">dev.wikidot.org</a> :-D Improving Wikidot is not that difficult.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://www.wikidot.org/forum/t-39387#post-101876</guid>
				<title>cleanly separate dis-allowed menu options: cleanly separate dis-allowed menu options</title>
				<link>http://www.wikidot.org/forum/t-39387/cleanly-separate-dis-allowed-menu-options#post-101876</link>
				<description></description>
				<pubDate>Mon, 04 Feb 2008 08:10:47 +0000</pubDate>
				<wikidot:authorName>Matt Wilkie</wikidot:authorName>				<wikidot:authorUserId>70840</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Please don't show, or show together in a different place, menu items which users don't have permissions to use. For example I don't mind if anonymous visitors view page <em>history</em> or want to <em>discuss</em> the page, but currently those two actions are mixed in with things they can't do, like <em>edit</em> or add <em>tags</em> for example, and there is no visual distinction between them.</p> <p>thanks.</p> <p><em>update:</em> it would be sufficient to just display them differently, grayed out if they can't be used for example. They wouldn't have to be in a different place.</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>