---
title: "Configuration"
manual: "Academic Profiles Edit"
version: "3.0"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-persons-edit:configuration@3.0"
source: "Configuration/Index.rst"
rendered: "2026-10-26T17:55:31+00:00"
---

# Configuration {#configuration}

This extension ships its frontend TypoScript and its backend page TSconfig in
two forms: as TYPO3 **site sets**, and as classic **static templates** plus
**page TSconfig files** that are selected on a page. Both forms read the very
same files, so they configure an installation identically.

Pick one of them per site and stay with it — see
[Do not combine both](https://docs.typo3.org/permalink/fgtclb/academic-persons-edit:one-mechanism-per-site@3.0) for what happens otherwise.

## What the sets contain {#configuration-components}

The extension ships the ProfileEditing component and one aggregate set that
keeps the stable extension-level set name.

| Set | Delivers |
| --- | --- |
| `fgtclb/academic-persons-edit-profile-editing` | The assigned-profile list, profile editor, AJAX page type and the page TSconfig that offers ProfileEditing in the backend. |
| `fgtclb/academic-persons-edit` | ProfileEditing under the stable aggregate name. This is the normal set to use. |

Both depend on `fgtclb/academic-base-ctype-group`, the set of
**EXT:academic_base** that labels the content element group all academic
extensions sort their elements into.

The plugin renders partials of **EXT:academic_persons**, but it reads
them from `Resources/`, not from that extension's TypoScript. There is
therefore no set dependency on any `fgtclb/academic-persons-…` set, and none is
needed.

## The content element is hidden by default {#configuration-hidden-by-default}

**EXT:academic_persons_edit** hides the editing content type for the
whole installation and brings ProfileEditing back per component. Whichever of
the two mechanisms below you use, ProfileEditing is the only profile-editing
content element offered in the backend.

## Include the site set {#site-set}

Add the set to the `config.yaml` of the site that should offer the content
element:

**config/sites/my-site/config.yaml (diff)**

```diff
 base: 'https://example.com/'
 rootPageId: 1
+dependencies:
+  - fgtclb/academic-persons-edit
```

See also [TYPO3 Explained, Using a site set as dependency in a site](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/SiteHandling/SiteSets/Index.html#site-sets-usage).

The **View** action in the assigned-profile list uses the same public
detail page as the Academic Persons list plugins. Configure
`plugin.tx_academicpersons.detailPid` in the Academic Persons site settings
or TypoScript constants. ProfileEditing copies that value into its own Extbase
settings and targets the `academicpersons_detail` content element; it does
not require a second page setting in Academic Persons Edit.

## Include static templates {#static-templates}

For an installation that still configures its frontend through
`sys_template` records, the same files are registered as static templates
and as selectable page TSconfig files.

> [!TIP]
> On TYPO3 v13 and v14 we recommend the site set — and if you use it, do not
> press the backend button **Create a root TypoScript record** on that
> site. The `sys_template` record it creates carries the flag
> **Clear** for constants and setup, and that flag discards everything
> the site sets contributed. An installation that is already in that state
> gets its configuration back by selecting the static templates below in that
> very record.

### Include static TypoScript {#static-typoscript}

Edit the `sys_template` record of the site root and add the entry to
**Include static (from extensions)**:

| Entry | Delivers |
| --- | --- |
| **Academic Persons Edit: Profile editing (academic_persons_edit)** | The TypoScript and AJAX page type of ProfileEditing. |
| **Academic Persons Edit: All components (academic_persons_edit)** | Every component this extension ships, in one entry. |
| **Academic Persons Edit: Path up to 2.3 (deprecated, use All components) (academic_persons_edit)** | The same as **All components**, for a record that still stores the path of version 2.3. Deprecated, removed in version 4.0, see [Deprecation: The static template path of version 2.3](https://docs.typo3.org/permalink/fgtclb/academic-persons-edit:deprecation-legacy-static-template-path@3.0). |

### Include static page TSconfig {#static-pagetsconfig}

Edit the page record of the site root, tab **Resources**, field
**Page TSconfig**, and add the entry:

| Entry | Delivers |
| --- | --- |
| **Academic Persons Edit: Profile editing (academic_persons_edit)** | Makes ProfileEditing selectable and configures its wizard entry. |
| **Academic Persons Edit: All components (academic_persons_edit)** | Every component this extension ships, in one entry. |

The setting is inherited by every page below the one it is set on.

## Load the script or bring your own {#configuration-javascript}

The **Profile editing** content element loads the module
`@fgtclb/academic-persons-edit/frontend/profile.js` on the page that shows
the editor of a profile. The list of assigned profiles loads no script.

It is switched off per site, for an installation that brings an editor of its
own:

| Site setting and constant | Default | Off means |
| --- | --- | --- |
| `plugin.tx_academicpersonsedit.assets.js` | `true` | The page does not load the module. |

With the site set, it is a site setting of the component set
`fgtclb/academic-persons-edit-profile-editing`, so a site that names only that
set can set it:

**config/sites/my-site/settings.yaml**

```yaml
plugin.tx_academicpersonsedit.assets.js: false
```

With the static template, it is the TypoScript constant of the same name:

**Constants of the root sys_template record**

```typoscript
plugin.tx_academicpersonsedit.assets.js = 0
```

**The editor does not work without its script.** Every field, button and
dialog of it is driven by the script: it defines the custom element
`<academic-persons-edit-profile-editing>` and the elements below it, reads
their configuration from the `data-*` attributes and sends every change
to the endpoints the template names. Switching the script off therefore means
bringing a complete editor for the same markup and the same endpoints, see
[Templates](https://docs.typo3.org/permalink/fgtclb/academic-persons-edit:templates@3.0). A site that only wants to change how the editor
looks keeps the script, styles the editor in its site package and overrides
partials where the markup has to change.

## Do not combine both {#one-mechanism-per-site}

A site that uses the site set **and** the static template reads the shipped
files twice. The site set is applied before the `sys_template` record, so
the second read happens after the site settings and after
`config/sites/<site>/constants.typoscript` — and it resets every constant
the extension ships a default for back to that default.

Nothing else is damaged: the **Constants** and **Setup** fields
of the `sys_template` record, the page TSconfig of a page and the page
TSconfig files selected on a page are all applied afterwards and still win. Use
one mechanism per site and the question does not arise.

-   [General configuration](https://docs.typo3.org/permalink/fgtclb/academic-persons-edit:general-configuration@3.0)
-   [Profile editor and validation](https://docs.typo3.org/permalink/fgtclb/academic-persons-edit:profile-editor-and-validation@3.0)
-   [Labels](https://docs.typo3.org/permalink/fgtclb/academic-persons-edit:labels@3.0)