For those deprecated messages, VaultWiki v4.1.7 is not fully compatible with PHP 8.2. You will continue receiving them in your log until we publish a new release, or you switch to another PHP like 8.1. We are currently working on a compatible release that covers 8.2 and 8.3, as well as the most recent versions of XenForo. Please note that XenForo itself only made a release fully compatible with PHP 8.2 very recently (
2.2.14 on January 30, 2024, see:
https://xenforo.com/community/thread...raries.210516/)
However, I don't think that PHP 8.2 deprecated messages would prevent your wiki from being routable. The wording of the exact message you are receiving suggests that XenForo's router doesn't know what to do with the wiki URL. The most obvious things that could cause this:
- The router file
src/addons/vw/vw/Pub/Router.php is missing or has improper file permissions, preventing the XenForo router from finding the wiki router rules.
- VaultWiki's \vw\vw\Listener::router_public_setup not running. Please check in your AdminCP > Development > Code event listeners (requires you to enable XenForo's development mode in your
src/config.php file):
Code:
$config['development']['enabled'] = true;
(You should only enable this temporarily while looking up this information).
Make sure that VaultWiki has a code event listener for "router_public_setup" and that it is enabled. If the listener is completely missing, then it is likely something went wrong during installation.
* Note: If the listener
file was missing or had improper file permissions, then XenForo should have given you an error during installation, so if the listener is listed and enabled, then the file should be fine.
- If VaultWiki's code event listener is okay, check for code event listeners for "router_public_setup" that are listed under different add-ons. Another add-on's listener that uses "return false" might be preventing VaultWiki's listener from running.
I have traced a few other theories, but they would all result in a different error message than what you are receiving. If the issue is not an incomplete installation of listeners, or another add-on blocking the listener as described above, then we would need to perform further investigation. In that case, you are welcome to file a ticket here:
https://www.vaultwiki.org/members/?do=newticket