Issue: URL rewriting to move VaultWiki to it's own base url

If you have already changed the Wiki Base URL setting, the only thing you need is a mod_rewrite rule at / that points /wiki to /forum/index.php

Example /.htaccess:
If /wiki is a real folder, this may not work.

If this does not achieve the desired effect, you will need to post or PM the mod_rewrite configuration so that we can review it.

Try removing the leading slashes from the RewriteRule:
If /forum exists and contains index.php, you should at least see a XenForo error page, not a 404.

The wiki home page is cached. Sometimes the cache update will not propagate if an error occurs. You can clear it manually by temporarily disabling VW_CACHE_ON in /vault/config.php

Okay, that works, but now all the CSS and /vault resources 404 as they don't exist in the root directory. Instead of looking in the /forum directory, it's checking in the root. I could copy them over, but that doesn't seem like an ideal solution.

I was able to resolve the CSS issue with the following rule:
I tried the same to resolve the /vault assets issue:
However, the results in the following error:

Refused to execute script from 'https://www.example.com/vault/resources/js/tab.js?v=4012' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.

However, the problem with CSS and other resources sounds like a bug. VaultWiki should be aware that the resource URLs are under the forum root if the wiki root is different. I think it's using the wiki root to prevent cross-domain errors when the wiki root is a different sub-domain, but I think it should be smart enough to handle all these scenarios automatically. I will try to reproduce the issue on a test board.

You also need a rewrite rule from wiki-base-url/yui_loader.php to forum-base-url/yui_loader.php

Otherwise, I have tried this in our demo (forum in /xf and wiki in /xf-wiki), and I only encountered an issue with some URLs when the "Name of the Wiki Route" setting was left blank (which does not apply to your case unless your /wiki was actually entered in the base URL setting). The bugs related to this blank setting have been fixed for the next release.

I did not encounter any of the issues you described with broken CSS, but I see that my XenForo is serving a BASE tag in the HTML. I wonder if you are using an earlier version of XenForo that does not serve the BASE tag, or if you are using a browser that does not recognize the BASE tag.

To avoid configuration issues in the future, I have added a new folder xf_subdomain to the do_not_upload folder. The contents of this folder would be dropped into a real /wiki folder if it does not reside at the forum root. A sample .htaccess is included in the folder as well.

I am closing this report since all the issues I found when attempting a setup like yours are now fixed in the next release. If you have any new information to add I will gladly reinvestigate.

I just recently revisited this and tried the new method of creating a wiki folder and using the sample contents. It ultimately ends up in a 404 error, so I went back to the current method of just using rewrites to direct everything. Just wanted to let you know, so you could see if you could reproduce it. It could be something unique to my setup, and if so, isn't really a big deal.