Rewrite Configuration
This is an old revision of this page, as edited March 24, 2013, 11:50 AM by pegasus(contribs). It may differ significantly from the current revision.
If you use vBSEO or some other method of catch-all URL rewriting, keep in mind that VaultWiki's rewrite rules should super-cede and completely replace the rules for your existing solution.
If you do not do this, your wiki will be inaccessible and you will just get a "Configuration Error" all the time.
Using the vBSEO example, your .htaccess file might already contain something similar to the following:
Code:RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !/(admincp|modcp|clientscript|cpstyles|images)/
RewriteRule ^(.+)$ vbseo.php [L,QSA]
This block should be completely commented out or removed, since VaultWiki accomplishes the same thing.
Next you would locate a section that looks like this:
Code:RewriteCond %{REQUEST_URI} !(admincp/|modcp/|cron|vbseo_sitemap|api\.php)
RewriteRule ^((archive/)?(.*\.php(/.*)?))$ vbseo.php [L,QSA]
Then, in the part of the line that ends like so:
Code:|api\.php)
you want to add more information right before the closing parenthesis. Usually, the following will be enough:
Code:|wiki
In order for vBSEO to continue doing its original job with these changed rules, you also need to modify vault/config.php. Find the line that defines DEFAULT_SCRIPT, and change it to 'vbseo.php'