When something goes wrong
Start here, in this order
- Admin CP, Logs, Server error log. An error names its own file and line. Nine times out of ten it names the answer too.
- Admin CP, Tools, File health check. It compares every shipped file to what it should be. A file reported as having unexpected contents either arrived damaged or was edited.
- Admin CP, Tools, Rebuild caches. Rebuild templates and phrases after any upgrade that looked odd.
- Permissions. A feature that exists but never shows up for your members is almost always a permission, not a bug.
The add-on installed but nothing appears
Check that it is enabled in Admin CP, Add-ons, then check its options and its permissions. Some add-ons deliberately stay dormant until you point them at a node or a user group.
Something looks broken in my theme
Try it on the default XenForo style first. If it behaves there, the theme is overriding something and I can usually work around it. Tell me which theme.
An upgrade lost my change
An upgrade overwrites the files it ships. If you had patched one by hand, that patch is gone. Tell me what the patch did, and it often becomes an option so you never have to do it again.
A page throws an error after an upgrade
Rebuild the master data: Admin CP, Tools, Rebuild caches, then templates and phrases. If it persists, the server error log names the file, and that is what I need to see.
Still stuck
Bring three lines: your XenForo version, your PHP version, and what the server error log says. See Getting support.
Premium XenForo add-ons, built, sold and supported by the developer himself. One-time payments, 12 months of updates, forums that answer back.