Skip to main content
Safe upgrades for EXT:ns_t3af. Always test on staging before production.

​
Before upgrade

  1. Read release notes on the T3Planet product page or in official TYPO3 docs
  2. Backup database and composer.lock
  3. Test the upgrade on staging with the same PHP and TYPO3 version as production

​
Upgrade commands

​
v1 to v2 migration

If you upgrade from v1 with API keys in Extension Configuration:
This moves legacy API keys into the AI Providers table. Then verify providers in AI Providers.

​
Post-upgrade checklist

  • Dashboard loads without errors
  • Provider Test connection returns green
  • MCP shows online (if you use MCP)
  • AI Logs show no new errors after a test request
  • T3Planet Credits still active (if used) — click Activate again if needed

​
Rollback

If the upgrade fails on staging:
  1. Restore composer.lock from backup
  2. Run composer install
  3. Run vendor/bin/typo3 extension:setup -e ns_t3af
  4. Restore database backup if schema changed
Do not rollback production without a maintenance window.

​
When to run full upgrade:run

Always after composer update nitsan/ns-t3af. TYPO3 may register new database fields or wizards. Skipping upgrade:run causes missing columns or broken backend modules.

​
MCP after upgrade

If MCP was enabled before upgrade:
  1. Flush all caches
  2. Re-run health check from MCP Server
  3. Re-authorize OAuth clients if token lifetime changed
See also Update Version for routine updates.