# Create subsequent subportal (language)

This article describes how Subportals can be created retrospectively and how they can be activated and linked at all relevant points. This is necessary, for example, if an additional language is to be activated in the event at a later date.&#x20;

This article can also be used as an aid if an event has not been created correctly (e.g. because a required language was not available in the template) and a subportal needs to be “repaired”.&#x20;

## Step 1: Copy tree structure <a href="#schritt-1-baumstruktur-kopieren" id="schritt-1-baumstruktur-kopieren"></a>

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2Fks6x7CfpClf4x7AnxhVR%2F2024-11-12_14h48_30.png?alt=media&#x26;token=fb8c5924-22e5-4b89-a06c-5e353a256ee5" alt=""><figcaption><p>Fig. 1: Creating a new Subportal</p></figcaption></figure>

* Go to the desired VA and select *Current frame*: The existing subportal(s) of the event will be displayed. If this is invisible, deselect the corresponding checkbox *Visible*.&#x20;
* Copy name if necessary
* Create new subportal
* The name of the new subportal is made up of the copied name + new language&#x20;
* Select the desired language&#x20;
* When copying content, select the *Copy tree structure* checkbox and the desired subportal to be copied and create the new subportal (visible)

**Always copy the tree structure of the event to which the new subportal is to be attached**. Otherwise, serious problems may occur when editing linked articles in the page structure (unintentional editing of articles in other events).

## Step 2: Link page templates <a href="#schritt-2-seitentemplates-verknupfen" id="schritt-2-seitentemplates-verknupfen"></a>

* All CMS page templates that are used in the template must also be linked to the new subportal under:

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FZOtZg9NzK7WqVOjDpasO%2F2024-11-12_14h54_47.png?alt=media&#x26;token=4a982845-b571-48bb-b17a-c2531fad1bf4" alt=""><figcaption><p>Abb. 2: Add the required templates to the new subportal</p></figcaption></figure>

## Step 3: Linking to the domain <a href="#schritt-3-verknupfung-mit-der-domain" id="schritt-3-verknupfung-mit-der-domain"></a>

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FwwvtEGWqXrDUs5O8WmYu%2F2024-11-12_14h58_18.png?alt=media&#x26;token=e0642964-9599-4922-814e-5c1d4911ec7d" alt=""><figcaption><p>Fig. 3: Linking the Subportal to the domain</p></figcaption></figure>

Damit das Subportal auch unter der Veranstaltungsdomain, z.B. <https://meine-veranstaltung.de> abrufbar ist, muss es dort noch verknüpft werden.

* Domain der Veranstaltung suchen und bearbeiten ODER wenn es keine separate Veranstaltungsdomain gibt, dann muss die Domain der Installation (z.B. uni-musterstadt.converia.de) zum Bearbeiten geöffnet werden
* Tab *Subportale* und *Eintrag hinzufügen* wählen
* neu angelegtes Subportal anklicken (i.d.R. ganz unten in Liste) und *Auswahl übernehmen*
* wenn es eine separate Veranstaltungsdomain <https://meine-veranstaltung.de> gibt und **zugleich die Primärsprache der Veranstaltung geändert** werden soll (auf das neu angelegte Subportal), dann muss ggf. noch das *Einstiegssubportal* angepasst werden. Das *Einstiegssubportal* ist die Sprache, die zuerst erscheint, wenn die Domain aufgerufen wird (= Primärsprache der Veranstaltung). Es kann nur ein Einstiegssubportal pro Domain geben.

To ensure that the subportal can also be accessed under the event domain, e.g. <https://meine-veranstaltung.de>, it still needs to be linked there.&#x20;

* Search for and edit the domain of the event OR if there is no separate event domain, then the domain of the installation (e.g. uni-musterstadt.converia.de) must be opened for editing&#x20;
* Select the *Subportals* tab and *Add entry*&#x20;
* Click on the newly created subportal (usually at the bottom of the list) and *accept* the selection
* If there is a separate event domain <https://meine-veranstaltung.de> and **the primary language of the event is to be changed at the same time** (to the newly created subportal), then the *Entry subportal* may need to be adjusted. The *Entry subportal* is the language that appears first when the domain is called up (= primary language of the event). There can only be one entry subportal per domain.

## Step 4: Linking to the event <a href="#schritt-4-verknupfung-mit-der-veranstaltung" id="schritt-4-verknupfung-mit-der-veranstaltung"></a>

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FvtXfsx5oGGtyhbeWwprR%2F2024-11-12_15h01_29.png?alt=media&#x26;token=be3ef837-6b67-4c92-a431-681450068a7e" alt=""><figcaption><p>Fig. 4: Linking to the event</p></figcaption></figure>

The newly created subportal must now be linked to the event itself. To do this, call up the *Subportals* tab in the basic settings and *add* the corresponding *entry*.
