An add-on upload contains new files but the administrator still sees the old installed version. This is a narrower problem than a complete XenForo failure: the most useful evidence is the condition under which it begins.
What the user actually sees
Primary symptom. An add-on upload contains new files but the administrator still sees the old installed version. Record the precise point of failure and whether the same input, account or connected device succeeds in another supported mode. That working comparison establishes the scope of the repair.
Separate configuration from service faults
The first hypothesis is a mismatch in the failing path. Compare add-on metadata, deployed filesystem path and pending upgrade status. The second is a lower-level state that the interface may not show: check class cache, add-on identifier, filesystem permissions and upgrade log entries. A third possibility is a feature or version limitation, which should be checked against supported documentation before a reset.
For this XenForo issue, capture XenForo version, user criteria and relevant server log timestamp and compare an administrator test compared with an ordinary member account. Preserve the last known working configuration so you can tell whether a successful retry came from an actual correction or a temporary recovery.
Read the evidence
| What you observe | What it suggests | Focused response |
|---|---|---|
| An add-on upload contains new files but the administrator still sees the old installed version | The failure affects the specific workflow described here; the entire system is not necessarily broken. | Compare add-on metadata, deployed filesystem path and pending upgrade status. |
| The basic comparison exposes a difference between a working and failing configuration. | A local setting, version, account context or device route deserves attention. | Complete the supported XenForo add-on upgrade workflow rather than editing the installed version directly. |
| The same failure persists after a reversible correction. | A deeper dependency or compatibility issue may remain. | Check class cache, add-on identifier, filesystem permissions and upgrade log entries. |
Before changing anything: Do not manually overwrite add-on database schema or purge production data. Save a screenshot or anonymized log line, record the previous setting, and back up relevant user data. Do not reset every related service just because one test fails.
Choose a recovery route. The Beginner path checks compare add-on metadata, deployed filesystem path and pending upgrade status. The Advanced path investigates check class cache, add-on identifier, filesystem permissions and upgrade log entries. They address different evidence; use the path that matches your result.
Step-by-Step Troubleshooting
Choose the Beginner route for reversible checks or Advanced for evidence-driven diagnosis.
Identify the exact failure boundary
An add-on upload contains new files but the administrator still sees the old installed version. Before editing settings, note the exact time, affected account or device, and whether it started after an update, move, hardware change or network change. This is the baseline for the XenForo Add-on Upgrade Shows Old Version Despite New Files guide.
Check add-on metadata, deployed filesystem path and pending
Compare add-on metadata, deployed filesystem path and pending upgrade status. Observe whether the symptom changes. A clean comparison tells you which part of the process is healthy and avoids unnecessary resets.
Adjust complete the supported XenForo add-on upgrade workflow
Complete the supported XenForo add-on upgrade workflow rather than editing the installed version directly. Change only this variable, record its former value, and try the failing action once. If there is no improvement, restore the prior configuration before exploring the Advanced route.
Verify the add-on displays the intended version and its feature
The add-on displays the intended version and its feature smoke test passes. Repeat using the same account, network, file, title or hardware condition that previously failed. Do not count a different test as confirmation.
Inspect supporting logs
Collect the error text or state relevant to XenForo Add-on Upgrade Shows Old Version Despite New Files. Record XenForo version, user criteria and relevant server log timestamp; anonymize account IDs, public IPs and secret-bearing log fragments before sharing.
Inspect class cache, add-on identifier, filesystem permissions and
Check class cache, add-on identifier, filesystem permissions and upgrade log entries. Record the difference between successful and failed cases and keep the first meaningful error rather than the last cascade message.
Rule out related configuration drift
Where practical, compare an administrator test compared with an ordinary member account. If the alternate case works, return to the single configuration difference instead of changing multiple services. Use the vendor-supported method for your current version.
Verify and record results
The add-on displays the intended version and its feature smoke test passes. Leave the previous value documented for rollback, then monitor one normal operating cycle. If symptoms recur, attach the sanitized evidence to a vendor or administrator support request.
What not to assume
After the first corrective action, interpret the result carefully. If the original task now works, leave the other settings unchanged. If it still fails, check class cache, add-on identifier, filesystem permissions and upgrade log entries. Compare an administrator test compared with an ordinary member account rather than adding random fixes on top of one another.
For escalation, retain XenForo version, user criteria and relevant server log timestamp, the original output, and a single before/after comparison. Redact passwords, tokens and personal data. A support agent can then distinguish an administrator test compared with an ordinary member account from a general outage without repeating risky actions.
Verification procedure
Pass condition: The add-on displays the intended version and its feature smoke test passes. The validation must exercise the same path that failed originally. A successful settings screen, single ping, application homepage or idle system is not enough if the original failure appears during a different action.
Repeat the test under the original conditions once after a safe relaunch, reconnect or new session. For intermittent failures, record the time and the difference between a clean result and a failed one instead of claiming success from a single attempt.
Prevention and next steps
If the problem persists, restore any test-only settings, preserve the evidence and stop before destructive reset, firmware flash or credential recreation. Give official support the exact symptom, the first failing timestamp and what the comparison established. Do not manually overwrite add-on database schema or purge production data.
Prevent recurrence: Document the working correction: Complete the supported XenForo add-on upgrade workflow rather than editing the installed version directly. Retain the accepted result (the add-on displays the intended version and its feature smoke test passes) as a future regression test after configuration, software or hardware changes.
Solution Checklist
Questions specific to this fault
How do I know the symptom is actually resolved?
The add-on displays the intended version and its feature smoke test passes. A generic diagnostic test outside the affected workflow is not a substitute.
Should I reset or reinstall everything first?
No. Compare add-on metadata, deployed filesystem path and pending upgrade status. Then choose the smallest supported intervention: complete the supported XenForo add-on upgrade workflow rather than editing the installed version directly. Preserve recoverable settings and user data.
What should I include in a support request?
Provide the exact failing action, product and version, time, non-sensitive log evidence, and this deeper observation: Check class cache, add-on identifier, filesystem permissions and upgrade log entries. Do not include credentials or private customer data.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.