Since XenForo 1.2, it may now be possible to route wiki pages with dynamic paths through XenForo's index.php. If that's the case, from a rewrite config perspective, it would be better to do this.
Working on this right now. So far the results are positive, and it seems the change can be backported to XenForo 1.1. This means that VaultWiki's rewrite rules for XenForo change in Beta 5.
XenForo's rules would remain untouched (if you changed them for VaultWiki, change them back), and the following should be added immediately before the try_files directive in nginx:
It's possible to continue using wiki_cp.php unwrapped just as admin.php?wiki/
To wrap it would require further refactor, but the scope of this issue is merely to get the scripts accessible via index.php/admin.php rather than separate scripts.
Wrapping the Admin Panel can be handled by a separate report and/or another release.
Last item on the agenda is to make sure the install/upgrade process is accessible. The initial install process is different for XenForo now:
Go to XF ACP, and import a stub XML file.
Under Applications > VaultWiki, click "Run Install Script."
Due to the wiki CP passing through XenForo's routes, it's now necessary to import an XML file before running the install script, or XenForo won't be able to find the proper route prefix for VaultWiki's install script. The XML file would include:
VaultWiki addon ID, title, and fake version info
init_dependencies Code Event Listener which initializes the VaultWiki god class
admin navigation: VaultWiki > Run Install Script
admin route prefix for the install script
admin permission required to access the install script
This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.