Requests and Ideas (new threads)

Spammers on Wikidot

Thu, 27 May 2010 09:29:08 +0000

There are logged in users that regularly spam Wikidot (probably they are robots) with links to external sites.

Why isn't there a spam filter like Akismet or Sblam installed for edits / comments? The amount of spam on open wikis is becoming a nightmare and the only solution seems to be switching the permission schemas to allow edits from specific users only.

Robots="noindex" on not found pages

Thu, 28 Jan 2010 12:38:21 +0000

I've suggested this on Wikidot.com forum (http://community.wikidot.com/forum/t-214639/seo:canonical-page-and-noindex-on-lacking-pages):

Wikidot already supports some tags needed for SEO (Search Engine Optimization), but it lacks 2 features that are a "must" for SEO.

(…)

Robots tag = "noindex"

Secondly, Wikidot could use the code bellow on non-existing pages, so that the search engines won't index pages with that default text:

> + The page does not (yet) exist.
>
> The page blablabla you want to access does not exist.
>
> * create page

This is not only duplicated content, but also hides our real contents behind these "keywords": "page", "exist", "create"… This is specially true on newly created wikis, not fully populated yet.

The code needed on these pages is:

[[code type="HTML"]]

…

…

[[/code]]

The same could be done to admin:manage (anyone wants it to appear on Google?).

Doing a quick search on Wikidot.org source files, I think I've found a way of implementing it. Maybe the solution for the robots=noindex on not found pages might be like the following (code starts on line 50 of http://github.com/gabrys/wikidot/blob/master/templates/layouts/WikiLayout.tpl):

 php // [...] Line 50: <meta http-equiv="content-type" content="text/html;charset=UTF-8"/> <meta http-equiv="content-language" content="{$site->getLanguage()}"/> // *************** NEW CODE START *************** {if $pageNotExists} <meta name="robots" content="noindex" /> {/if} // **************** NEW CODE END **************** <script type="text/javascript" src="/common--javascript/WIKIDOT.js">script> // and so on... ?>

In my opinion it seems to be an easy solution for that problem of duplicated content and unwanted search keywords.

Tags Suggest

Mon, 09 Jun 2008 11:24:51 +0000

Hi all,
I'm trying to implement some new features in wikidot v1
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.

this is the main function (a poor copy&past&modify from PageLookupQModule….):

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->query($q1); $result1 = $result1->fetchAll(); $result2 = $db->query($q2); $result2 = $result2->fetchAll(); if($result1 == null && $result2 != null) $result = $result2; if($result2 == null && $result1 != null) $result = $result1; if($result1 != null && $result2 != null){ $result = array_merge($result2, $result1); } return array('tags' => $result); } }

now I need to modify PageTagsModule.js in order to allow search operation.
anyone can help me? I think this feature would be very usefull for everyone.

thanks,
Gio

add markdown support

Mon, 05 May 2008 01:09:04 +0000

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.

You can see some of the available engines in action at
http://babelmark.bobtfish.net/?markdown=++*+foo%0D%0A%0D%0Abar ,
or have a look at the converter at http://johnmacfarlane.net/pandoc/try

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?

— Thomas.

Editing Meta Tags

Tue, 22 Apr 2008 14:18:31 +0000

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.

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

I would be happy if the Webmaster Tools were available. But the general capability to edit Meta tags would be very useful by itself.

Expand QueryString variables in templates

Fri, 28 Mar 2008 00:43:10 +0000

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.

cleanly separate dis-allowed menu options

Mon, 04 Feb 2008 08:10:47 +0000

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 history or want to discuss the page, but currently those two actions are mixed in with things they can't do, like edit or add tags for example, and there is no visual distinction between them.

thanks.

update: 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.