fckglite plugin by Myron Turner
WYSIWYG editor. JavaScript Front end to FCKeditor
Last updated on 2010-02-24. Provides Syntax.
Compatible with DokuWiki 2009-12-25c "lemming".
Requires fckeditor (included with fckglite).
Similar to fckw, grensladawritezor, wysiwyg, wysiwyg_nicedit.
fckgLite is a pure JavaScript implementation of the FCKeditor for DokuWiki. If you don't need the graphic capabilities of DokuWikiFCK, this is the way to go. It saves its documents as native DokuWiki markup, unlike DokuWikiFCK, which relies upon an extended markup to render the graphics. fckgLite is built on the DokuWikiFCK architecture and provides many of its benefits.
fckgLite and DokuWikiFCK cannot both be installed at the same time; fckgLite installs into the same directory structure as DokuWikFCK in plugins/fckg and uses many of the same PHP classes.
Download and install the plugin using the Plugin Manager using the following URL. Refer to Plugins on how to install plugins manually.
Download fckgLite by clicking on the download button above or directly from the the fckgLite web site. For a manual installation, install by unzipping the tgz file into your plugins directory.
Version 03.03 implements non-Roman character support for the File Browser. It is based on the ACL-compliant version 02.03 and handles non-Roman ACL checks. If you don't need ACL checks you can turn them off in the configuration manager. And if you use your DokuWiki as an administrator, you will not be restricted by ACL. It is available from the fckgLite web site.
There is an issue with Firefox 3.6, which fails when large files are uploaded using the file browser. This issue appears to affect only Firefox 3.6 in Windows. If you wish to continue to use Firefox, and have upgraded to 3.6, you can revert to an earlier version by going to ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/. A quick check of Bugzilla shows a variety of upload issues.
Latest: Mozilla developers are aware of this bug and it may now be fixed. The problem is apparently an issue with the development tool Firebug. So if you don't have Firebug installed you are probably OK. Please update here if you have anything to report from your own experience.
I just reinstalled Firefox 3.6 with firebug 1.5.2 and there are no longer any problems uploading. The firebug bug tracker identifies this bug as solved with firebug 1.5.1.
The quick upload tab now uploads files to the namespace directory of the file being edited. Previously files were pushed to the top level media directory when using the quick upload tab. There was also a bug in January and February 2010 updates that prevented images from appearing in the Image Properties Window and in the editor when first being brought into the document, although they appeared in the browser and on subsequent reloads of the page into the editor. This is now fixed. 0.03 has also caught up with other versions of fckgLite in now re-writing filenames of uploads to the DokuWiki standard.
You can use the DokuWiki forum for reporting bugs and making feature requests. To do this click on the bug button above.
You can also subscribe to the fckgLite mailing list, where you can ask and answer questions. You can subscribe to the list in one of two ways:
The fckgLite web site should be consulted for documentation. You will find a good deal of information on the Features Page and in the change logs. If you are stumped, post a query to the DokuWiki forum.
Problem description
Lets say that you have DokuWiki, what can be accessed from the internet and has confidential files, what are protected with Wiki ACL.
If you have installed fckgLite, then all your files can be accessed without logging in: http://yoursite.com/wikitest/lib/plugins/fckg/fckeditor/userfiles/flash/secret/file.zip
In worst scenario +Indexes is on (Apache directory listing is allowed) and everyone can freely browse through your secret documents.
Solution
Add .htaccess file into lib/plugins/fckg/fckeditor/userfiles/ folder, containing:
Deny from all
- Mxrgus Pxrt
–
Actually, this won't work with fckgLite, because the FCKeditor is considered an intruder and is denied access. See Security below.
If you want to use Clean URLs add lines following lines in beginning of lib/plugins/fckg/parser.php:
global $conf; $conf['userewrite'] = '0';
Or links are broken.
- Mxrgus Pxrt
First, there is no lib/plugins/fckg/parser.php. Perhaps you mean, render.php. Setting userewrite to 0 will presumably turn nice urls off, and the reason it doesn't (if you are talking about render.php) is that the resetting of this value comes too late in the loading process to take effect.
Which version of fckgLite are you referring to? Support for nice URLs was added as of Nov 26 2009.
If when clicking the media “Browse server” button you get the error “Forbidden.” You don't have permission to access /lib/plugins/fckg/fckeditor/editor/filemanager/browser/default/browser.html on this server.” then you may have a mod security problem.
If the server is running Apache 1 you may be able to fix it by adding the following to the .htaccess file in your server root.
SecFilterEngine off SecFilterSelective off
For Apache 2 you whitelist the domain for the appropriate rule. You may require your web host to organize this for you.
If the inserted images don't display in the editor until after the page is displayed you may have a permissions problem with the media files. Add a .htaccess file into (webroot)/data/media/ with the lines
order allow,deny allow from all
This will allow the images to display directly from the editor. [
Are there any security issues with this?]
Technically, there is a security issue, if you keep sensitive documents in your media directory. Since those will not be images, however, what you can do is to create a folder (or folders) for sensitive documents, place an .htaccess file in these directories which denies direct access to the folders
order allow,deny deny from all
You can then still link to them if you need to, using the link browser's “Non-DokuWiki Internal Files” link type. This works because the documents are fetched internally by a DokuWiki script and not by means of a URL. However, you will not be able to use the File Browser to upload to these directories. If the files have non-standard characters in them, a good practice would be to upload these files to a directory which accepts them and then move them over to the protected folder; this will assure that the files conform to the DokuWiki typographic requirements. -M.T.
If you are, list your site here.
I use fckgLite, but on a documentation private server of my company. Not connected to internet… PaoloG
Using it also, but in private… very nice though! –Pena