Upgrade 

Versioning 

Context Reporter follows semantic versioning (MAJOR.MINOR.PATCH). Before version 1.0, a minor version (0.x.0) can contain changes that require action; they are listed in CHANGELOG.md of the repository.

The report document has its own version, schema in the JSON document (currently context-reporter.report.v1). New fields can be added without changing it, so receivers should ignore unknown fields.

Updating the extension 

composer update priebera/typo3-context-reporter
vendor/bin/typo3 extension:setup
vendor/bin/typo3 cache:flush
Copied!

extension:setup adds new database tables and columns. Run it, or Admin Tools > Maintenance > Analyze Database Structure, before the extension is used: until the database is updated, the report dialog and the report history can fail with a database error.

In classic mode, update the extension in Admin Tools > Extensions, then analyze the database structure and flush the caches.

TYPO3 upgrades 

Context Reporter supports TYPO3 13.4 LTS and TYPO3 14.3 with the same package, so an upgrade of TYPO3 from 13.4 to 14.3 needs no other version of the extension. Run the database update after the TYPO3 upgrade, as for every upgrade:

vendor/bin/typo3 extension:setup
Copied!

The database tables of the extension are the same on both TYPO3 versions: stored reports, screenshots, the delivery history and the review state are kept, and the settings stay in the TYPO3 registry.

Differences between TYPO3 13.4 and 14.3 

The extension behaves the same on both branches. Two things look different because TYPO3 changed them, not the extension:

  • Backend modules were renamed in TYPO3 14. Reports name the module the reporter was in, so the same situation reads Web > Page on TYPO3 13.4 and Content > Layout on TYPO3 14.3, likewise Web > List → Content > Records, File > Filelist → Media and Site Management > Sites → Sites > Setup. Reports created before the upgrade keep the labels that were stored with them.
  • The file list actions of TYPO3 14 are split before extensions are asked. options.file_list.primaryActions still decides whether Report problem is a direct action or an entry of the More options menu, and Configuration/user.tsconfig still lists it, but on TYPO3 14 the extension evaluates the option itself. Projects that override the option have to include contextReporterReport on both branches.