.. include:: /Includes.rst.txt .. _faq: === FAQ === .. contents:: Table of contents :local: :depth: 2 .. rst-class:: panel panel-default Why is the 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? **Site Set** Is the Frontend Edit site set included in your site configuration? Check the Site Settings to verify the extension is enabled. **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 to :code:`/typo3/ajax/xima-frontend-edit/edit-information` with the information about the editable content elements and the according Edit Menus. .. rst-class:: panel panel-default 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: :code:`forceReturnUrlGeneration`. .. rst-class:: panel panel-default 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 :ref:`redirect ` configuration in the extension settings to open the edit form within the full TYPO3 backend context, which supports the language switch. .. rst-class:: panel panel-default 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 .. rst-class:: panel panel-default 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. .. code-block:: html :caption: DCE Template
Your template goes here...
.. note:: Styling problems may occur with nested content elements. .. rst-class:: panel panel-default 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. .. code-block:: html :caption: Container Template
{record.header}
{record.renderedContent}
Alternatively, you can also use `fluid_styled_content `__ in the templates: .. code-block:: html :caption: Container Template {record.header}
{record.renderedContent}
.. note:: Styling problems may occur with nested content elements.