---
title: "FAQ"
manual: "Frontend Edit"
version: "2.6"
source: "FAQ/Index.rst"
rendered: "2026-10-01T07:11:45+00:00"
---

# FAQ {#faq}

Answers to the problems reported most often. If none of these help, please
[open an issue on GitHub](https://github.com/xima-media/xima-typo3-frontend-edit/issues).

## Nothing appears in the frontend {#faq-no-menu}

**Why is the Edit Menu not displayed at all?**

Work through this checklist — the cause is almost always one of these
six points.

-   **Backend user session**

    Are you logged into the TYPO3 backend? Without an active backend
    session nothing is injected into the frontend.

-   **Backend user permissions**

    Does your user have permission to edit both the page and the
    content elements on it?

-   **Site set**

    Is the Frontend Edit site set included in your site configuration?
    See [Installation](../Installation/Index.html#installation).

-   **Frontend editing switched off**

    Check whether [frontendEdit.enabled](../Configuration/SiteSettings.html#confval-frontendedit-enabled) is `true`, whether
    the page is excluded via [frontendEdit.filter.ignorePids](../Configuration/SiteSettings.html#confval-frontendedit-filter-ignorepids),
    and whether the toggle in the [toolbar](../Usage/Toolbar.html#toolbar) is switched
    off for your user. It can also be disabled administratively via
    [UserTSconfig](../Configuration/UserTSconfig.html#user-tsconfig).

-   **Content element IDs**

    The rendered HTML must expose a "c-id" per element, e.g.
    `id="c908"` \- or use the `data-frontend-edit` attribute instead.
    Without template changes, the experimental
    [render markers](../Integration/TemplateRequirements.html#render-markers) are an alternative.
    See [How it works](../DeveloperCorner/Architecture.html#how-it-works) and [Setup requirements & limits](../Configuration/SetupRequirementsAndLimits.html#setup-requirements-and-limits) (headless/SPA frontends are an
    explicit non-goal, for the same reason).

-   **Content element on the current page**

    Only elements belonging to the current page are editable. Inherited
    content (e.g. a shared footer) cannot be edited from the inheriting
    page.

> [!TIP]
> Check the network tab for the initial AJAX call to
> `/typo3/ajax/xima-frontend-edit/edit-information`. Its
> response lists every element the extension considers editable.
> Enabling [Frontend Debug Mode](../Configuration/ExtensionConfiguration.html#extconf-frontendDebugMode)
> adds detailed console logging.

**The edit button is missing on a different (sub)domain**

Frontend editing needs an active backend user session. On a different
(sub)domain the session cookie is only valid for the backend domain and
is therefore not available to the frontend.

Two ways out:

-   Configure a broader
    [cookieDomain](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Configuration/Typo3ConfVars/SYS.html#confval-globals-typo3-conf-vars-sys-cookiedomain)
    so the session cookie is shared between the domains.
-   Use the
    [multisite_belogin](https://extensions.typo3.org/extension/multisite_belogin)
    extension, which provides backend login across multiple domains
    without a shared cookie domain.

> [!WARNING]
> A broader `cookieDomain` shares the backend session cookie with
> **every** matching subdomain of that deployment — restrict it to
> trusted subdomains served over HTTPS. It cannot bridge unrelated
> domains (a session is tied to a single TYPO3 instance); use
> `multisite_belogin` where a shared cookie is unsuitable.

A cross-domain setup can also cause a `returnUrl` to be
rejected with an HTTP 400 error instead of silently redirecting to
the root page: the extension only accepts a `returnUrl` whose
host matches the current request or one of the site's configured
base URLs (including per-language bases). A rejected return url is a
sign to check your site configuration's base URLs rather than a bug
— see [Setup requirements & limits](../Configuration/SetupRequirementsAndLimits.html#setup-requirements-and-limits) for the full picture.

**The edit button is missing on EXT:container or EXT:dce elements**

Neither [container](https://extensions.typo3.org/extension/container/)
nor [DCE](https://extensions.typo3.org/extension/dce) render the
required content element ID in their default templates — you have to add
it.

[Template requirements](../Integration/TemplateRequirements.html#template-requirements) has a ready-to-copy snippet for both,
including a `fluid_styled_content`-based alternative for containers.

> [!NOTE]
> Styling problems may occur with nested content elements.

Alternatively, add the `data-frontend-edit` attribute instead (see
[How it works](../DeveloperCorner/Architecture.html#how-it-works)) - it avoids the "c-id" naming collision risk
entirely and needs no sibling resolution:

**DCE Template**

```html
{namespace xfe=Xima\XimaTypo3FrontendEdit\ViewHelpers}

<div class="dce"{xfe:editable(uid: contentObject.uid)}>
    Your template goes here...
</div>
```

**The menu is missing on inherited content (e.g. a shared footer)**

Only content elements belonging to the **current page** are editable.
Content pulled in from another page cannot be edited from the inheriting
page — the record simply does not live there.

Use the [toolbar](../Usage/Toolbar.html#toolbar) to navigate to the page that owns the
record and edit it there.

## Problems with the edit form {#faq-edit-form}

**After saving I end up on the wrong page (e.g. the root page)**

This is usually caused by a strict referer header. If the return URL
cannot be determined from the request, force it to be generated from
page ID and language via the
[Return URL generation](../Configuration/ExtensionConfiguration.html#extconf-forceReturnUrlGeneration)
extension setting.

See [Setup requirements & limits](../Configuration/SetupRequirementsAndLimits.html#setup-requirements-and-limits)
for the full picture of multi-domain setups, including `SameSite`
and `returnUrl` behavior.

**I cannot change the language inside a content element**

This is a TYPO3 backend limitation: the reduced edit form frame does not
include the language switch.

Use the [Redirect](../Configuration/ExtensionConfiguration.html#extconf-useRedirect) extension setting to open
the edit form in the full TYPO3 backend, which does provide the language
switch.

> [!NOTE]
> In connected mode the edit link already targets the *translated*
> record, so a manual language switch is usually unnecessary. See
> [Languages](../DeveloperCorner/Languages.html#languages).