pegasus
Well-known member
When using this mod to install VaultWiki Lite (or VaultWiki), it uploads files to the wrong location. In particular, it uploads an index.html file from one of the lower level directories into the XenForo root directory, which in many setups results in that file being served instead of the XenForo site. This leads many users to the incorrect initial assumption that installing VaultWiki (which was actually never installed at this point, just uploaded wrong) has crashed their sites, and has directly led to at least 1 scalding review of the add-on.
You can download VaultWiki Lite from the Resources area to test things out, but the directory structure looks like this:
- CHANGELOG
- LICENSE
- README
- the XML file (which doesn't actually install anything except some admin routes and a link to the real installer)
- do_not_upload/
- upload/
---- library/
------ vw/
---- vault/
------ core/
------ resources/
---- yui_loader.php
Also, VaultWiki developers have stated that the addon XML file and the install script must be separated because of limitations in the current Install/Upgrade system provided by XenForo. In order to avoid timeouts on most client machines, the install process must be able to support both paged and batched install routines (1 refresh for each step, extra refreshes for steps with multiple batches), as well as mid-process modals if user input is required by a step.
You can download VaultWiki Lite from the Resources area to test things out, but the directory structure looks like this:
- CHANGELOG
- LICENSE
- README
- the XML file (which doesn't actually install anything except some admin routes and a link to the real installer)
- do_not_upload/
- upload/
---- library/
------ vw/
---- vault/
------ core/
------ resources/
---- yui_loader.php
Also, VaultWiki developers have stated that the addon XML file and the install script must be separated because of limitations in the current Install/Upgrade system provided by XenForo. In order to avoid timeouts on most client machines, the install process must be able to support both paged and batched install routines (1 refresh for each step, extra refreshes for steps with multiple batches), as well as mid-process modals if user input is required by a step.