Using dokuwiki's plugin manager to install fckglite
Early versions of fckgLite required manual installation. But versions of fckgLite, as of November 24 2011, can be installed using the Dokuwiki Plugin Manager.
If you have previously used a manual install for fckgLite, the Plugin Manager may not be able to install a new instance of fckgLite over top of the old one, because it may not have the correct permissions. In this case you may want to delete the old installation of fckgLite or change the permissions so that the web server has write permission to the files and directories of the fckgLite plugin.
Plugin Manager: When the plugin manager installs fckgLite, it may fail to install a set of symbolic links in
fckg/fckgeditor/userfiles. These symlinks are used in the default configuration of the file browser.
Current installs: All versions of fckgLite, dated after Nov 24 2011, will create the required symlinks if they do not already exist. In its default configuration for Linux, the file browser is set up to access
where image and file are symlinks which point to
On Windows systems the symlinks are not required, because in its default configuration the file browser is set up to directly access
However, up-to-date versions of fckgLite will also create symlinks on Windows beginning with Vista.
If the symlink creation fails, there will be a message notifying you of the failure. You then have two choices:
- You can install manually
- You can create the symbolic links your self. You will have to create four symlinks:
They must all point to the
In Unix-type systems you create symbolic links from the command line. For instance, to create the
file link and have it point to your media directory, you would use the following command:
ln -s /path/to/data/media file
Another solution is to copy the following file to the fckg/fckeditor directory: :userfiles.tgz. Then extract it:
tar -xzf userfiles.tgz
This will copy the necessary links to the fckg/fckeditor/userfiles directory. A copy of userfiles.tgz is also stored at Sourceforge.
On Windows systems you use the mklink command from the Command Prompt window. Here the syntax is as follows:
mklink /D "path\to\data\media" "path\to\link\name"
mklink /D "C:\dokuwiki\data\media" "C:\dokuwiki\lib\plugins\fckg\fckeditor\userfiles\file"
The quotation marks are usually needed.
userfiles.tgz solution mentioned above will not work in Windows since Windows uses a different kind of symbolic link.
Force symlink creation
To force fckgLite to attempt to create symlinks after a failure, delete the file data/meta/fckl/symchk.meta.
After the symlink creation module has run, it creates symchk.meta, which will contain the version id of your fckgLite distribution. By checking this file, the module knows it has attempted symlink creation for the current distribution. If you delete this file, it will try again. When you upgrade, fckgLite will do this check again. If it finds the symlinks, it will do nothing and exit without comment. If the symlinks have been removed, it will re-create them.
There are two new configuration options.
- plugin»fckg»nix_style: For Windows Servers (Vista and Later). This setting makes it possible to access data\media through fckg\fckeditor\userfiles, if links to media and file have been successfully created in userfiles
- plugin»fckg»no_symlinks: Disable automatic creation of symbolic links in fckg/userfiles.
The first of these makes it possible for Windows installations to use the nix-style filebrowser installation. The second of these is a fail-safe setting, aimed at preventing nuisance messages from being printed to the top of the browser if something goes wrong with the symlink creation and fckgLite wants to keep warning you of the fact. This is unlikely, but you should have the option just in case.