Upgrading from 2.3 to 2.4 

Before you start 

Version 2.4 runs on TYPO3 12.4 from 12.4.22 on and on TYPO3 13.4, with PHP 8.1 or later. That is the same as for 2.3, so the TYPO3 core does not have to change for this upgrade.

academic_persons_edit 2.4 declares no new dependency of its own. It needs these packages. Upgrade them first or in the same deployment, in this order:

• fgtclb/environment-state-manager 1.x, new in 2.4, which academic_base 2.4 and academic_persons 2.4 require. Composer installs it on its own. A classic installation installs environment_state_manager before it activates either of them.
• fgtclb/academic-base 2.4, the same release as this extension.
• fgtclb/academic-persons 2.4, the same release as this extension. Its upgrade chapter has steps of its own, and its database update and its upgrade wizard are due in the same deployment.

academic_persons_sync 2.4 requires this extension and follows it in the same deployment, where installed.

Update the package 

composer require -W \
    'fgtclb/academic-base':'~2.4.0' \
    'fgtclb/academic-persons':'~2.4.0' \
    'fgtclb/academic-persons-edit':'~2.4.0'

A project that requires branch 2 as 2.x-dev keeps an inline alias such as 2.x-dev as 2.4.x-dev working, see Important: The development branch installs as 2.4.x-dev.

On a classic installation, install environment_state_manager 1.x from the TER in Admin Tools > Extensions first, then update academic_base, academic_persons and academic_persons_edit there, in this order. Run the commands of this page with typo3/sysext/core/bin/typo3 instead of vendor/bin/typo3 .

vendor/bin/typo3 cache:flush

Update the database 

vendor/bin/typo3 extension:setup

In the backend the same is Admin Tools > Maintenance > Analyze Database Structure. Version 2.4 of this extension changes no table. Run the update all the same, academic_persons 2.4 adds a column, and the upgrade wizard of the next step requires an up to date schema.

Run the upgrade wizards 

vendor/bin/typo3 upgrade:run academicPersonsEdit_removeProfileSwitcherContent

The wizard Remove content elements of the removed academic_persons_edit profile switcher plugin, academicPersonsEdit_removeProfileSwitcherContent, is new in 2.4. The profile switcher has rendered nothing since version 2.1, which replaced it, but its content type stayed registered. Version 2.4 removes the content type, and the wizard sets every content element of it to deleted, in both shapes it can have: with the CType academicpersonsedit_profileswitcher, and as a legacy plugin with the list_type of that name. The records stay restorable from the recycler. See Breaking: Removed the profile switcher plugin, which also has the queries to look at the affected records first.

The wizard can run in any order with the other wizards. academicPersonsEdit_pluginContent, which shipped with 2.3 already, no longer moves a profile switcher onto its own content type, so whether it ran before does not matter. An installation that never used the profile switcher gets nothing to do from the wizard.

Once TYPO3 has recorded a wizard as done, it is offered again only after it is marked undone. TYPO3 13 marks a wizard undone with vendor/bin/typo3 upgrade:mark:undone academicPersonsEdit_removeProfileSwitcherContent. TYPO3 12 has no such command: open Admin Tools > Upgrade > Upgrade Wizard, find the wizard under Wizards marked as done and choose Mark undone.

Adapt the configuration 

plugin.tx_academicpersonsedit.renderContentElementHeader = 1

plugin.tx_academicpersonsedit.settings.editForm.profileImage.validation.allowedMimeTypes =

Adapt templates and assets 

An override keeps its own copy and does not receive a change of the shipped file. Version 2.4 changes 35 of the Fluid files of the plugin, and nearly all of them translate their labels with the extension name AcademicPersonsEdit now instead of academic_persons_edit , which moves the path of a label override, see Labels. Re-apply each override on top of the 2.4 file. Breaking: Adapted frontend editing Fluid files lists every change, and Overriding templates describes how the overrides are set up.

The changes beyond the label path follow. The paths below are relative to Resources/Private/:

One asset moved. The editor configuration is compiled from TypeScript now:

A template copy or a site package that references the old path loads a missing file, and the rich text fields fall back to plain text areas. See Breaking: The editor configuration moved. A site package that shipped an editor configuration of its own only to get a link button can drop it, the shipped one has one now, see Important: Links and readable markup in the frontend editor.

Adapt your code 

The form data transformation now writes only the properties a form submitted. Code that extends or replaces the internal form data classes or their factories, and sets a property the form did not submit, registers the value with AbstractFormData::setPropertyOverride() , otherwise it is not applied. See Important: Form data transformation only maps submitted fields.

Check the result 

1. The new content element wizard offers Profiles: Profile Editing on the pages that should have it, and an existing profile editing content element opens in the backend with its own type.
2. No profile switcher content element is left, and the page module shows no element with an invalid type in its place.
3. The header of a profile editing content element appears once.
4. The rich text fields of the profile form and of the contract forms start the editor, and the editor offers links.
5. A frontend user can edit each of its profiles. The editor accepts only profiles the frontend user is linked to in the default language of the profile, a link set only on a translation is ignored. See Important: The editor is limited to own profiles.
6. A rejected form shows the message at the rejected field.
7. A profile image of an accepted media type uploads, and the profile view of the plugin renders it.