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
Next revision Both sides next revision
media [2014/12/18 18:50]
tower [Internal Link Dialog]
media [2016/08/31 16:40] (current)
tower [Unix-type systems]
Line 3: Line 3:
 ===== Tool bar icons and dialogs ===== ===== Tool bar icons and dialogs =====
  
-{{tag>​toolbar links filebrowser image keys flash samba security}} ​  ​In Dokuwiki uploading media files to the server and inserting images and external media urls are handled by the media manager; in addition, internal links can be set from a pop-up menu attached to the internal like tool bar item.  In the FCKeditor, these features are handled by three dialogs modified in fckgLite to accommodate Dokuwiki. ​ These are the image and link dialogs and the file browser.+{{tag>​toolbar links filebrowser image keys flash samba security}} 
 + 
 +In Dokuwiki uploading media files to the server and inserting images and external media urls are handled by the media manager; in addition, internal links can be set from a pop-up menu attached to the internal like tool bar item. In the FCKeditor, these features are handled by three dialogs modified in fckgLite to accommodate Dokuwiki. These are the image and link dialogs and the file browser.
  
 The toolbar buttons which activate the link and image dialogs are the familiar Dokuwiki icons: The toolbar buttons which activate the link and image dialogs are the familiar Dokuwiki icons:
Line 10: Line 12:
  
 ===== Link Dialog ===== ===== Link Dialog =====
 +
  
 The link dialog has three fields, two of which are drop-down menus. The link dialog has three fields, two of which are drop-down menus.
Line 161: Line 164:
 Dokuwiki by-passes these prohibitions by use of php scripts which do not use direct URL access. But the fckgLite filebrowser is outside of this system and needs work-arounds to handle images. ​ Otherwise, you will be able to see the names of the images but not the images themselves, which will be replaced by the broken image icon. Dokuwiki by-passes these prohibitions by use of php scripts which do not use direct URL access. But the fckgLite filebrowser is outside of this system and needs work-arounds to handle images. ​ Otherwise, you will be able to see the names of the images but not the images themselves, which will be replaced by the broken image icon.
  
-<​sup><//​nowiki></​nowiki>​%<​nowiki>​%\</​nowiki><​nowiki></​nowiki></​nowiki> ​ //      </​sup>​ 
  
 ==== Unix-type systems ==== ==== Unix-type systems ====
  
-Dokuwiki'​s media files are secured by an .htaccess file in the data directory which prohibits direct web access to the files stored in the data directory and all of its subdirectories. ​ To by-pass this prohibition,​ fckgLite accesses the media directory indirectly through symbolic links in the fckeditor/​userfiles directory. ​ The defaullt .htaccess file in the userfiles directory allows complete we access to the media directory. If your wiki is open to the internet, you might want additional security. There is an .htaccess file in the fckg/​fckeditor/​userfiles directory which prohibits direct access to all files except image files. ​  ​This file is named .htaccess.security. To use it you must remove the ”.security” extension and rename it  .htaccess:+Dokuwiki'​s media files are secured by an .htaccess file in the data directory which prohibits direct web access to the files stored in the data directory and all of its subdirectories. To by-pass this prohibition,​ fckgLite accesses the media directory indirectly through symbolic links in the fckeditor/​userfiles directory. The defaullt .htaccess file in the userfiles directory allows complete we access to the media directory. If your wiki is open to the internet, you might want additional security. There is an .htaccess file in the fckg/​fckeditor/​userfiles directory which prohibits direct access to all files except image files. This file is named .htaccess.security. To use it you must remove the ”.security” extension and rename it .htaccess:
  
-<file apache .htaccess.security>​order allow,​deny +<file apache .htaccess.security>​ 
-allow from all+<​IfModule mod_authz_host>​ 
 +    Require all denied 
 +</​IfModule>​ 
 +<​IfModule !mod_authz_host>​ 
 +    Order allow,​deny 
 +    ​Deny ​from all 
 +</​IfModule>​
  
-Options -Indexes +<​FilesMatch "​\.(gif|jpe?​g|png)$">​ 
- +<​IfModule mod_authz_host>​ 
-order allow,​deny +    Require all granted 
-deny from all +</​IfModule>​ 
- +<​IfModule !mod_authz_host>​ 
-<​FilesMatch "​\.(gif| jpe ?g| png )$">​ +    Order allow,​deny 
-order allow,​deny +    ​Allow ​from all 
-allow from all+</​IfModule>​ 
 +</​FilesMatch>​
  
 Options -Indexes Options -Indexes
 </​file>​ </​file>​
  
-In order for this file to be effective, the Apache configuration file (httpd.conf) must apply the **AllowOverride All**    directive either to the userfiles directory or to one of its parent directories. ​   This directive must be in a Directory container, for instance: +In order for this file to be effective, the Apache configuration file (httpd.conf) must apply the **AllowOverride All** directive either to the userfiles directory or to one of its parent directories. This directive must be in a Directory container, for instance:
 <​code>​ <​code>​
 <​Directory "/​var/​www/​html">​ <​Directory "/​var/​www/​html">​
Line 192: Line 200:
 </​code>​ </​code>​
  
-If you have to add the AllowOverride All directive, because it is not already in effect for the userfiles directory, then you will have to restart your web server. ​ For more information about AllowOverride,​ see the [[http://​httpd.apache.org/​docs/​2.2/​mod/​core.html#​allowoverride|Apache documentation]].+If you have to add the AllowOverride All directive, because it is not already in effect for the userfiles directory, then you will have to restart your web server. For more information about AllowOverride,​ see the [[http://​httpd.apache.org/​docs/​2.2/​mod/​core.html#​allowoverride|Apache documentation]].
  
-Notice that the .htaccess security file only allows image files through the security wall. Urls for any other files will be denied. ​ You can change this if you wish; for instance if you want to allow access to pdf files, you can add pdf to your list of allowed extensions:+Notice that the .htaccess security file only allows image files through the security wall. Urls for any other files will be denied. You can change this if you wish; for instance if you want to allow access to pdf files, you can add pdf to your list of allowed extensions:
  
 <​code>​ <​code>​
-<​FilesMatch "​\.(gif|jpe?​g|png)$">​ +<​FilesMatch "​\.(gif|jpe?​g|png|pdf)$">​ 
-order allow,​deny +
-allow from all+
 </​FilesMatch>​ </​FilesMatch>​
 </​code>​ </​code>​
Line 207: Line 214:
 ==== Windows ==== ==== Windows ====
  
-if your filebrowser does not display images, then try placing the .htaccess from userfiles into your data/media directory. ​ If the AllowOverride directive has been set to '​All'​ for the media directory or one of its parent directories,​ you should be able to see your images in the filebrowser. See the Unix discussion above for further details. ​ Also see [[:​media#​moving_files|moving_files]].+if your filebrowser ​or image pop-up ​does not display images, then try placing ​one of the .htaccess ​friles ​from userfiles into your data/media directory. If the AllowOverride directive has been set to '​All'​ for the media directory or one of its parent directories,​ you should be able to see your images in the filebrowser. See the [[#​unix-type_systems|Unix discussion]] above for further details. ​It is also possible to use the unix style set-up for the filebrowser. 
 + 
 +It is also possible to set the [[configuration#​conf_15|nix_style]] configuration option to ''​true''​. 
 + 
 +Also see [[:​media#​moving_files|moving_files]].
  
 ==== Troubleshooting ==== ==== Troubleshooting ====