Update an add-on
The routine
- Grab the new ZIP. Every release is announced in Announcements and listed on the product page with its changelog. Download it from your account, exactly as you did the first time.
- Upgrade. Admin CP, Add-ons, Install/upgrade from archive, pick the ZIP, confirm.
- Read the changelog. Each release says what was added, changed and fixed. New options arrive with sensible defaults, so an upgrade never leaves you with a half-configured feature.
What survives an upgrade
Your settings, your permissions and your data. Database changes run on their own during the upgrade. You never have to export anything first.
The one thing that does not survive is a file you edited yourself. If you patched an add-on by hand, Admin CP, Tools, File health check will name that file after the upgrade, and your change will be gone. Tell me what you needed instead, and it usually becomes an option.
Doing it without the FTP dance
If you own several of my add-ons, updating them one by one gets old. The Emporium Client does it from your own Admin CP, in one click, and tells you when something new is out.
If an update misbehaves
Post in the add-on's forum with the Bug report prefix. Include your XenForo version, your PHP version, and whatever Admin CP, Logs, Server error log says. Those three lines usually answer the question before I have to ask it.
Premium XenForo add-ons, built, sold and supported by the developer himself. One-time payments, 12 months of updates, forums that answer back.