WP-Dokuwiki development update


I’ve decided to move the development of WP-Dokuwiki over to the official [[http://dev.wp-plugins.org/ | WordPress plugins repository]]. Why did I do this? [[http://dev.wp-plugins.org/wiki/GetHosted|This page]] explains it all.

The source for the plugin can now be found at [[http://dev.wp-plugins.org/browser/wp-dokuwiki/]]. Please use the [[http://dev.wp-plugins.org/newticket|bug tracker]] to for bugs. If you want to test the bleeding edge code, you can track the trunk:


$ cd /path/to/wp-content/plugins
$ svn co http://svn.wp-plugins.org/wp-dokuwiki/trunk/wp-dokuwiki

I will continue to host the tar-balls for each version. Meanwhile you can always download the plugin directly from dev.wp-plugins.org, or get a Zip file from [[http://redalt.com/External/plugins.php|RedAlt's WordPress plugin download interface]].

4 comments

  1. sorin

    Currently I’m using dokuwiki and I’m looking for switching to WordPress because i need:
    - categories (tree), (dw namespaces are too hard to work with)
    - comments with management

    Your plugin was the solution, but I’ve discovered that is slowing the page loading a LOT. I can’t use it because I need speed (page loadtime un 1000ms). Currently It can take up to 7 seconds with your plugin (0.3) and wordpress (2.0.4). Disabling it will make WP work normaly. Still my personal copy of wordpress is very fast.

    Do you have any ideea on what should I do to make it work normaly?

  2. Diwaker Gupta

    *@sorin*: Glad you found use for the plugin. Yes, the Dokuwiki parser is not the fasted, and since the parser is invoked _several_ times to generate each page, this can really take quite a while.

    There are a couple of things you can do:
    - use WP-Cache 2 (http://mnm.uib.es/gallir/wp-cache-2/). I succesfully use wp-cache2 with really large expiration time-outs, and that helps a lot.
    - don’t write short posts (like Aside) using the Wiki markup — just let them through RAW html or something.
    - reduce the amount of “true” dynamic content on your webpage (for instance, feeds pulled in from last.fm or del.icio.us may break the caching at times).

    Let me know if that helps you.

Leave a Reply