close   


DokuwikiFCK is no longer being supported.
It has been superceded by fckgLite and ckgedit.
close   
namespace:
close   
All questions, bug fixes, and feature requests should go through the mailing list. To subscribe to the list, do one of the following:

1. Send an email to fckglite-request@freelists.org with 'subscribe' in the Subject field
2. Visit the fckgLite page at http://www.freelists.org/list/fckglite
3. Or click the subscribe link below

Subscribe
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
docs:auto_install [2012/12/18 10:42]
tower [Linux/Unix systems]
docs:auto_install [2013/11/03 17:23]
tower [Using dokuwiki's plugin manager to install fckglite]
Line 1: Line 1:
 ====== Using dokuwiki'​s plugin manager to install fckglite ====== ====== Using dokuwiki'​s plugin manager to install fckglite ======
-{{tag>​install configuration linux windows}}+ 
 + 
 +{{tag>​install configuration linux windows ​symlinks}} 
 + 
 Unlike previous versions of fckgLite, which required manual installation,​ versions of fckgLite 06, starting November 24 2011, can now  be installed using the Dokuwiki Plugin Manager. ​ The prohibition against using the Dokuwiki Plugin manager was aimed primarily at Linux/Unix systems, because the Plugin Manager fails to install a set of symbolic links which are needed to run the filebrowser,​ as explained in more detail below. ​  The plugin manager will not remove the links once they have been created, but will not install them.  This is no longer a problem; ​ fckgLite will now check to see if these links exist and if not it will create them. Unlike previous versions of fckgLite, which required manual installation,​ versions of fckgLite 06, starting November 24 2011, can now  be installed using the Dokuwiki Plugin Manager. ​ The prohibition against using the Dokuwiki Plugin manager was aimed primarily at Linux/Unix systems, because the Plugin Manager fails to install a set of symbolic links which are needed to run the filebrowser,​ as explained in more detail below. ​  The plugin manager will not remove the links once they have been created, but will not install them.  This is no longer a problem; ​ fckgLite will now check to see if these links exist and if not it will create them.
  
  
 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. 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.
 +
 +
 +~~COMPLEX_TABLES~~
  
 ===== Background ===== ===== Background =====
Line 12: Line 19:
  
  
-**Plugin Manager:** When the plugin manager installs fckgLite, it fails to install a set of symbolic links in ''​fckg/​fckgeditor/​userfiles''​. These symlinks are used in the default configuration of the file browser.+**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.
  
  
Line 26: Line 33:
  
 {{  :​docs:​filebrowser.png?​518x82 ​ }} {{  :​docs:​filebrowser.png?​518x82 ​ }}
 +
 +
 +~~COMPLEX_TABLES~~
  
 ==== Windows ==== ==== Windows ====