Important: Profile editing is replaced in place
Description
The profile editing frontend is rewritten from the ground up (Breaking: Replaced the profile editing view), but it keeps the identity of the content element it replaces. Nothing in the page tree, in a site configuration or in a deployment has to be renamed:
| What | Value |
|---|---|
Content type (tt_content.CType) | academicpersonsedit_profileediting |
| Extbase plugin | AcademicPersonsEdit / ProfileEditing |
| Request namespace | tx_academicpersonsedit_profileediting |
| Site sets | fgtclb/academic-persons-edit and
fgtclb/academic-persons-edit-profile-editing |
| Static template / page TSconfig | EXT: and
EXT: |
| TypoScript object | plugin.tx_academicpersonsedit |
| Default action | list |
Existing content records keep working after the update. There is no upgrade wizard for the content element and none is needed.
Impact
An update replaces the rendered view and the markup below the plugin, not the record that renders it. What does change is described in Breaking: Replaced the profile editing view; what an integrator has to look at is the list of removed Fluid files, the removed action links and the new page type of the JSON endpoints.
Affected Installations
All installations using the Profile editing content element of
EXT:.