---
title: "Important: The contact inline parent is now workspace aware"
manual: "Academic Contacts for Pages"
version: "main"
source: "Changelog/3.0/Important-ContactInlineParentIsWorkspaceAware.rst"
rendered: "2026-09-18T06:17:05+00:00"
---

# Important: The contact inline parent is now workspace aware {#important-the-contact-inline-parent-is-now-workspace-aware}

## Description {#description}

`tx_academiccontacts4pages_domain_model_contact` has always declared
`'versioningWS' => true`, while the table it is attached to as an inline
child — `tx_academicpersons_domain_model_contract`, extended in
`Configuration/TCA/Overrides/tx_academicpersons_domain_model_contract.php`
\- did not.

That is the direction TYPO3 does not repair.
`TcaMigration::addWorkspaceAwarenessToInlineChildren()` only ever adds the
flag to a *child* whose parent already carries it, and TYPO3 v13 ships no such
migration at all, so a workspace aware child below a live-only parent went
unreported on both supported core versions. The TYPO3 documentation calls the
combination unsupported.

`academic_persons` 3.0 declares all of its record tables workspace aware,
which resolves it: parent and child now agree.

## Impact {#impact}

Nothing changes in this extension itself. Its contact records were already
versionable and keep their `t3ver_*` columns.

What changes is that the parent record can now be versioned as well, so a
contact and the contract it belongs to are drafted and published together
rather than the contact alone being versionable below a record that was not.

The parent table gains four columns and an index in the process. **Run the
database analyzer once after updating** — see *Breaking: Person records are
workspace aware* in the 3.0 changelog of `academic_persons`, which also
documents the SQLite defect that affects the command line path.

> [!NOTE]
> The `contract`, `email_address`, `phone_number` and
> `physical_address` columns of
> `tx_academiccontacts4pages_domain_model_contact` are `select`
> fields with an `itemsProcFunc` and no `foreign_table`, so they
> store bare uids that TYPO3 does not know to be relations.
> `DataHandler` cannot remap them when a record is published out of a
> workspace. Making the tables versionable does not change that, and it is
> tracked separately.

## Affected Installations {#affected-installations}

Every installation of this extension, because it depends on
`academic_persons` and the schema of
`tx_academicpersons_domain_model_contract` changes there.