FAQ 

Why is the frontend edit menu not displayed on my page / for my content element? 

There may be a number of reasons for this:

Backend user session

Are you currently logged into the TYPO3 backend? Otherwise the frontend edit will not working.

Backend user permission

Does your user have all permissions to edit the page as well as the content elements?

TypoScript

Is the TypoScript template "Frontend edit" included in your sitepackage? Do you have declared the constants to restrict the usage of the frontend edit?

Content Element IDs

Make sure that the content element "c-ids" (Content Element IDs) are available within your frontend template, e.g. "c908".

Content Element on current Page

For now only all content elements on the current page are "editable". So if you're using some kind of inheritance, e.g. for your footer, this content can't be edited. Maybe I will find a smarter solution for this in the future.

Debug

Check the network tab for the initial ajax call (something like /?type=1729341864 with the information about the editable content elements and the according dropdown menus.

After closing the edit form will I redirected to the wrong frontend location, e.g. to the root page 

This could be caused by a strict referer header in your request. If the return url could not be determined correctly, you can force the url generation by pid and language in the extension setting: forceReturnUrlGeneration.

I can't change the language within a content element. 

This is a TYPO3 backend limitation. The reduced edit form frame does not support the language switch. Use the redirect configuration in the extension settings to open the edit form within the full TYPO3 backend context, which supports the language switch.

The edit button is not displayed for a different (sub)domain. 

The frontend edit needs an active backend user session to work. If you are using a different (sub)domain, the session cookie is only valid for the TYPO3 backend domain and is not available for the frontend edit.

You can have a look at the cookieDomain setting to set a more flexible domain configuration. This allows the session cookie to be shared between different (sub)domains, enabling the frontend edit functionality to work across different domains.

See https://docs.typo3.org/m/typo3/reference-coreapi/13.4/en-us/Configuration/Typo3ConfVars/SYS.html#confval-globals-typo3-conf-vars-sys-cookiedomain

The edit button is not displayed with DCE extension content elements. 

Dynamic content elements do not provide the required "c-id" (Content Element ID) in their default templates. You need to customize the DCE templates to include the "c-id" in the HTML output.

<div class="dce" id="c{contentObject.uid}">
    Your template goes here...
</div>

The edit button is not displayed with container extension content elements. 

Container content elements do not provide the required "c-id" (Content Element ID) in their default templates. You need to customize the container templates to include the "c-id" in the HTML output.

<div id="c{data.uid}">
   <f:for each="{children_200}" as="record">
       {record.header} <br>
       <f:format.raw>
           {record.renderedContent}
       </f:format.raw>
   </f:for>
</div>

Alternatively, you can also use fluid_styled_content in the templates:

<f:layout name="Default" />

<f:section name="Main">
  <f:for each="{children_200}" as="record">
      {record.header} <br>
      <f:format.raw>
          {record.renderedContent}
      </f:format.raw>
  </f:for>
</f:section>