Please locate your version to enable the control panel. These rewrite rules are essential for other site operations as well, so please be sure you have the correct rewrite rules for each version. Lyons will be the last release we anticipate making rewrite rule changes. Apologies for the inconvenience.
For Lyons, the deki folder must be added a RewriteRule exclusion. Be sure that your RewriteRule exclusions look like this:
RewriteCond %{REQUEST_URI} !^/(@api|editor|skins|config|deki)/
You can also remove any references to /@gui/ in your rewrite rules. When in doubt, refer to our Apache configuration for 9.02 and try to match it up as closely as possible.
Starting with Kilen Woods, MindTouch Deki contains a new control panel, which must be enabled through a modification of the Apache's Rewrite Rules. For the Kilen Woods release, we will keep the old administration files in place as a fallback, but subsequent releases will have these files removed.
To enable the new control panel, locate your Apache configuration file (on the VMs, it is located in /etc/apache2/sites-available/dekiwiki). Then, locate the lines which contain folders to be excluded. It will look something like this:
RewriteCond %{REQUEST_URI} !^/(@api|editor|skins|config|@gui)/
For Kilen Woods, modify this by appending the folder deki-cp :
RewriteCond %{REQUEST_URI} !^/(@api|editor|skins|config|@gui|deki-cp)/
You may also need to add index.php to your dir_module settings, by adding this section in the same file:
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule mod_dir.c>
DirectoryIndex index.html index.php
</IfModule>
Restart Apache (on the VMs: "/etc/init.d/apache2 restart") and your new control should now be active!
| Images 0 | ||
|---|---|---|
| No images to display in the gallery. |
or
https://svn.mindtouch.com/source/public/dekiwiki/8.08/config/deki-apache.conf
with any sort of thing like below:
<IfModule mod_dir.c>
DirectoryIndex index.html index.php
</IfModule>
Do I just add this entire thing somewhere inside the <VirtualHost> </VirtualHost> section?