First of all, my environment: I have an Ubuntu Linux machine at home, and I use a developer-friendly hosting service for my website. My provider supports PHP, Perl, Ruby on Rails, SVN, and plenty more. I have SSH and FTP access to my account, and I can ask the support team to install things (like PERL modules) and they will. If you have a hosting service that won't do this kind of stuff for you, you should switch. But hey, its your life….do what you want.
The website instructions are pretty straightforward, but a few steps weren't explained very well IMO.
1. Execute these commands or have your hosting provider run them for you. Using
sudo tells the operating system to run the
perl as the root user. This is necessary on Unix/Linux to get PERL to install the modules to a shared location, which you don't have write access to as yourself. (And thats good security…preventing just anybody from writing into the operating system directories). Each of these commands could ask a lot of questions, depending on how many perl modules you/your provider already have installed. Say 'yes' to all the questions about installing additional modules.
sudo perl -MCPAN -e 'install HTML::WikiConverter' sudo perl -MCPAN -e 'install HTML::WikiConverter::DokuWiki'
2. Confirm that everything works before continuing. Run this command and make sure you see output similar to mine. This confirms that the
html2wiki tool is installed, and its
Dokuwiki translator is present. DO NOT CONTINUE until you get this right!! Most future problems can be traced back to this.
chris@homemachine:~$ html2wiki --list Installed dialects: DokuWiki
3. I had to install the author's snippets plugin. This wasn't documented in the instructions, but it was easy to install:
svn co https://svn.liip.ch/repos/public/misc/dokuwiki/plugins/snippets
4. Install the FCKW plugin itself. Instructions are on the author's wiki. Like the above step, I retrieved it directly from SVN. But you could just download, unzip, and use FTP to put the files in the right place.
5. Finally, I had to make sure that my user Apache or PHP account had access to
html2wiki so it could run properly and convert between HTML and Dokuwiki syntax. I didn't have any issues, but I've heard that others do. This will depend on the settings imposed by your hosting service. There is nothing the author of the plugin can do to change that…you might have to work with your provider.
I've been using the plugin for a while now and I have several observations:
<code>tag is broken. Its hard/impossible to give source code examples without it
I have to admit that some of the limits here aren't due to FCKW, but rather to the PERL html2wiki translator being used behind the scenes to convert FCKW's HTML into DokuWiki syntax. But the end result is the same…a less-than-100%-function wiki. I think a more well-integrated
html2wiki translator would solve the problem. It would be able to sense what plugins are installed and write out the appropriate wiki syntax.
I think FCKW is great for basic users. I classify those as people who:
But currently1), FCKW is not a good fit for more advanced users. People who want to use more complex syntax are likely to be frustrated, and those who wish to use additional plugins are just plain out-of-luck.
Its sad that FCKW is so difficult to get working. Its a good visual editor for basic needs. If the installation process is made easier, it will be a nice option to have for Dokuwiki. I can see it being an included plugin that users can enable/disable as desired. However several install and operations kinks need to be worked out first.
I look forward to advances in the visual editing area for Dokuwiki. But as of today, I am uninstalling FCKW and returning to the default editor. The advantages of visual editing are not offset by the loss of functionality I'm experiencing.