I feel that I can make more of a difference in these other [personal] projects. [...] I hope others will pick up the slack and make sure that PDO gets love, at people diligently follow up on todo items mentioned on internals and that someone else picks up wiki.php.net and takes care of some regular maintenance stuff.

He mentions one thing specifically - an update that will need to happen to the Dokuwiki software the wiki runs on. If you're interested, send Lukas an email/leave a comment and he'll point you in the right direction.

During the last few weeks I wrote a few new DokuWiki plugins and updated some old ones. This post is to give you a short introduction about each and what is new in the updated ones.

The plugins that made the list are:

• the CAPTCHA plugin
• an S5 Presentationplugin
• The Bureaucracy Plugin (handling form validation)
• A plugin to interface with the Disqus commenting system
• A plugin that generates dynamic graphics via a Flash component

Every good programmer knows, that passwords should never be stored in clear text. Instead a one way hash (or digest) should be used. This way user passwords are not at risk in case of an intrusion.

He points out the multiple ways that PHP offers for both simple hashing (like md5 or sha1) and the true encryption types (like ssha, apr1 and crypt). He shows how they work in the DokuWiki application via a call to auth_cryptPassword to make it and db_get_hash/auth_verifyPassword to check against it.

Today I spent some time to figure out how to compile a relocatable Apache with PHP support. Yes, this might result in a Linux version of the DokuWiki on a Stick project. Read on for detailed instructions.

The installation is pretty similar to the normal compile with a few small differences. Check out the post for the complete process, commands and all.

Inspired by the recent buzz around OpenID I did some research to see what it's all about and what would be necessary to add OpenID logins to DokuWiki.

He talks about why he'd even want to integrate the login type into his application and, with the plugin in place, what steps it takes to authenticate the user.

I promised to investigate the steps needed to set up DokuWiki with the simplest authentication scheme for a friend and I thought others might benefit from it too, so here it is.

There's about fifteen steps in all, including the download/install of the package and creating the basic functionality (like a simple Auth schema - he gives an example). Create the superuser and set up the desired restrictions and you're home free. If you want more information on authentication in DokuWiki, check out this page on the DokuWiki's wiki.

In case you don't know: DokuWiki parses Wiki syntax into an instruction array which then is "rendered" to the desired output format. This output format is usually the XHTML to display a nicely formatted Wiki page.

Pluggable renderers allow plugin authors to write their own renderer to output any format they want. This adds another bit of flexibility to DokuWiki.

The idea for these renderers was inspired by the S5 system (developed by Eric Meyer) that was essentially a web-based slide show (without the need for a messy client-side application). Unfortunately, the slide shows were hard to make - which is where the renderers come in. In fact, he's already created the tool to get you started - the S5 DokuWiki Plugin. Check out his example to see the results.

In my opinion DokuWiki is the best wiki software out there (see features). In addition to all those cool features like namespaces, it stores pages in plaintext files, thus no database backend is required. Setting it up is pretty easy also. I promised to investigate the steps needed to set up DokuWiki with the simplest authentication scheme for a friend and I thought others might benefit from it too, so here it is.

He starts from, well, the beginning - grabbing the latest DokuWiki download, copying it over and running through the installation and configuration. Then it's on to the web inferface, changing the Access Controls to allow for more of a fine tuning on who can do what.

You can read up on his full advisory here, including the location/code of the issue.