source: branches/MootoolsFileManager-Update/plugins/MootoolsFileManager/config.php @ 1300

Last change on this file since 1300 was 1300, checked in by gogo, 8 years ago

Update the MootoolsFileManager? to the latest cpojer with some modifications.
Add a demo for the MFM examples/mootools-file-manager.php
Change the default config for ImageManager? and ExtendedFileManager? for added security.

File size: 6.3 KB
Line 
1<?php
2  /**
3    = MootoolsFileManager Configuration File =
4       
5    Configure either by directly editing the config.php file (not recommended) or
6    as follows...
7
8    1. You need to be able to put PHP in your XinhaConfig.js, so
9      you may want to call it XinhaConfig.php instead, or whatever other
10      method you choose (eg put the config as an inline script in your
11      main php page).
12     
13    2. In step 3 of your XinhaConfig write something like...
14      {{{
15        with (xinha_config.MootoolsFileManager)
16        {
17          <?php
18            require_once('/path/to/xinha/contrib/php-xinha.php');
19            xinha_pass_to_php_backend
20            (       
21              array
22              (
23                'images_dir' => '/home/your/directory',
24                'images_url' => '/directory',
25                'allow_images_upload' => true,
26              )
27            )
28          ?>
29        }
30      }}}
31
32    This will work provided you are using normal file-based PHP sessions
33    (most likely), if not, you may need to modify the php-xinha.php
34    file to suit your setup.
35 
36  * @author $Author$
37  * @version $Id$
38  * @package MootoolsFileManager
39  *
40  */
41
42
43  /**   
44    == File Paths REQUIRED ==
45   
46    This plugin operates (optionally) in two modes.
47   
48    1. As a File Manager where people are inserting a link to a file
49      (eg a doc or pdf commonly), we call this "files" mode.
50    2. As an Image Manager where people are inserting an inline image,
51      we call this "images" mode.
52   
53    You may provide one of, or both of, files_dir and images_dir.  If you do not
54    provide one, that mode of MootoolsFileManager will be disabled.
55   
56    # `files_dir` -- Directory path to the location where ordinary files are stored
57                      (eg /home/you/public_html/downloads/ )                   
58    # `files_url` -- The URL path to the files_dir
59                      (eg /downloads/) 
60    # `images_dir` -- Directory path to the location where inline images are stored
61                      (eg /home/you/public_html/images/)
62    # `images_url` -- The URL path to the images_dir
63
64    === Security Caution ===
65
66    You should ensure that the paths you specify are protected against having PHP and
67    other scripts from being executed.  The following .htaccess file is a good idea
68
69    {{{
70      <IfModule mod_php.c>
71        php_flag engine off
72      </IfModule>
73      AddType text/html .html .htm .shtml .php .php3 .php4 .php5 .php6 .php7 .php8 .phtml .phtm .pl .py .cgi
74      RemoveHandler .php
75      RemoveHandler .php8
76      RemoveHandler .php7
77      RemoveHandler .php6
78      RemoveHandler .php5
79      RemoveHandler .php4
80      RemoveHandler .php3
81    }}}
82   
83  */
84
85  $IMConfig['files_dir']  = FALSE; // No trailing slash
86  $IMConfig['files_url']  = FALSE; // No trailing slash
87
88  $IMConfig['images_dir'] = FALSE; // No trailing slash
89  $IMConfig['images_url'] = FALSE; // No trailing slash
90 
91  $IMConfig['thumbs_dir'] = NULL;  // Will default to images_url/.thumbs or files_url/.thumbs
92
93  /**
94    == Turning On Uploads ==
95    We have two sets of settings for turning on uploads, one controls the files mode
96    of the plugin, the other is for images mode.
97
98    Note that allowing upload also permits the user to create subdirectories to better
99    organise the files.
100   
101    === Maximum File Sizes ===
102
103    Each mode can have a different maximum file size that can be uploaded, this
104    size is a number followed by one of M, KB or B.
105
106    === Suggested Image Dimensions ===
107
108    Each mode can have a different "suggested maximum image dimension", when the
109    user uses the Mootools File Manager to upload a file, they are able to choose
110    to "resize large images" on upload.  This defines what "large" means.
111 
112  */
113
114  $IMConfig['allow_files_upload']     = false;
115  $IMConfig['allow_files_delete']     = false;
116  $IMConfig['max_files_upload_size']  = '3M';
117  $IMConfig['suggested_files_image_dimension']  = array('width' => 2048, 'height' => 1536);
118
119  $IMConfig['allow_images_upload']     = false;
120  $IMConfig['allow_images_delete']     = false;
121  $IMConfig['max_images_upload_size']  = '3M';
122  $IMConfig['suggested_images_image_dimension']  = array('width' => 1024, 'height' => 768);
123
124
125// -------------------------------------------------------------------------
126//                OPTIONAL SETTINGS
127// -------------------------------------------------------------------------
128
129/**
130
131== Plugin Path ==
132 
133 For most people the defaults will work fine, but if you have trouble, you can set
134 `base_dir` to be the directory path to xinha/plugins/MootoolsFileManager
135 `base_url` to be the url path to xinha/plugins/MootoolsFileManager
136*/
137
138$IMConfig['base_dir'] = getcwd();
139$IMConfig['base_url'] = preg_replace('/\/backend\.php.*/', '', $_SERVER['REQUEST_URI']);
140
141/**
142
143== HTML Compatability ==
144
145 For most people the default of using CSS will be fine, but if the HTML you are editing
146 in Xinha is destined for an email you will probably want to use hspace and vspace
147 instead of CSS margins because of poor Email support for CSS.
148 
149*/
150
151$IMConfig['UseHSpaceVSpace'] = TRUE;
152
153 /**
154  // Future use, not yet required.
155 
156  == ImageMagick Path ==
157 
158  Certain operations require that ImageMagick is available on your server,
159  mogrify, convert and identify executables are required.
160   
161  If these executables are not in your executable path, you'll want to
162  set the path to them here, for Linux/Unix etc this will be something like
163 
164  {{{
165    /usr/bin
166  }}}
167 
168  for Windows servers, something like
169 
170  {{{
171    C:/"Program Files"/ImageMagick-5.5.7-Q16/
172  }}}
173   
174 
175
176  $IMConfig['IMAGE_TRANSFORM_LIB_PATH'] = '';
177*/
178
179////////////////////////////////////////////////////////////////////////////////
180//       ================== END OF CONFIGURATION =======================      //
181////////////////////////////////////////////////////////////////////////////////
182
183
184// Standard PHP Backend Data Passing
185//  if data was passed using xinha_pass_to_php_backend() we merge the items
186//  provided into the Config
187require_once(realpath(dirname(__FILE__) . '/../../contrib/php-xinha.php'));
188
189if($passed_data = xinha_read_passed_data())
190{
191  $IMConfig = array_merge($IMConfig, $passed_data);
192}
193@session_write_close(); // Close session now so we don't lock.
194
195if(!isset($IMConfig['thumbs_dir']))
196{
197  $IMConfig['thumbs_dir'] = (isset($IMConfig['images_dir']) ? $IMConfig['images_dir'] : $IMConfig['files_dir']) . '/.thumbs';
198}
199?>
Note: See TracBrowser for help on using the repository browser.