Download the PHP package xima/xima-typo3-frontend-edit without Composer

On this page you can find all versions of the php package xima/xima-typo3-frontend-edit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of xima/xima-typo3-frontend-edit

Informations about the package xima-typo3-frontend-edit

![Extension icon](Resources/Public/Icons/Extension.svg) # TYPO3 extension `xima_typo3_frontend_edit` [![Latest Stable Version](https://typo3-badges.dev/badge/xima_typo3_frontend_edit/version/shields.svg)](https://extensions.typo3.org/extension/xima_typo3_frontend_edit) [![TYPO3 12](https://img.shields.io/badge/TYPO3-12-orange.svg)](https://get.typo3.org/version/12) [![TYPO3 13](https://img.shields.io/badge/TYPO3-13-orange.svg)](https://get.typo3.org/version/13) [![Total Downloads](https://poser.pugx.org/xima/xima-typo3-frontend-edit/d/total)](https://packagist.org/packages/xima/xima-typo3-frontend-edit)

This extension provides an edit button for editors within frontend content elements.

Note

This is not a further development of the "original" extension frontend_editing. It is similar in some ways to the realisation of the feedit extension. This extension is an independent implementation with a different approach.

The extension has been developed to provide a simple and lightweight solution to easily start the editing of content elements from the frontend and thus reduce the gap between frontend and backend. Therefore a simple javascript is injected into the frontend, which generates action links to the TYPO3 backend with the corresponding edit views.

Installation

Composer

TER

TER version

Download the zip file from TYPO3 extension repository (TER).

Configuration

Include the static TypoScript template "Frontend edit" or directly import it in your sitepackage:

Adjust the constants to restrict the usage of the frontend edit:

Backend user can easily disable the whole frontend edit functionality within their user settings.

User Settings > Edit and advanced functions > Disable frontend edit

How it works

On page load a script calls an ajax endpoint, to fetch information about all editable (by the current backend user) content elements on the current page.

The script then injects (if it's possible) an edit menu into the frontend for each editable content element.

This is only possible, if the content element "c-ids" (Content Element IDs) are available in the frontend template, e.g. "c908". By default the fluid styled content elements provide these ids.

The rendered dropdown menu links easily to the corresponding edit views in the TYPO3 backend.

Hint: The script is only injected if the current backend user is logged in.

For an easy edit workflow a "save and close" button is added to the edit form, which redirects the user directly back to the frontend. Disable this function within the extension settings, if you don't want this behaviour.

Extend

Two opportunities exists to extend the dropdown menu with custom entries:

  1. Use an event to modify the menu directly
  2. Use a viewhelper to extend the menu with data entries

Additionally you can provide a custom css file to adjust the styling.

Event

Use the FrontendEditDropdownModifyEvent to modify the edit menu to your needs. You can add, remove or modify buttons for specific content elements. See the example below:

Don't forget to register your event listener via PHP attributes (TYPO3 >= 13):

or register the event listener in your Services.yaml:

Data Attributes

Additionally, there is an option to extend your fluid template to provide data for extra dropdown menu entries, e.g. edit links to all news entries within a list plugin.

This generates a hidden input element with the provided data (only if the frontend edit is enabled). Within the parent content element (e.g. the whole list plugin), a new "data" section will show up on the dropdown menu to list all edit links.

See the DataViewHelper for more information. Keep in mind, that this only works if the parent content element has a c-id and offer one of the following data combinations:

  1. Edit record link (provide uid and table of the desired record, the link to the TYPO3 backend will be generated automatically)
  2. Custom edit url (provide a custom url)

Keep in mind, that this option will add additional html elements to your dom, which can causes style issues.

Custom Styling

The dropdown was styled to not disturb the frontend layout. You can easily adjust the styling by providing an additional css or js file within your ext_localconf.php:

FAQ

Missing frontend edit menu *Why is the frontend edit menu not displayed on my page / for my content element?* There may be a number of reasons for this: 1. __Backend user session__ Are you currently logged into the TYPO3 backend? Otherwise the frontend edit will not working. 2. __Backend user permission__ Does your user have all permissions to edit the page as well as the content elements? 3. __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? 4. __Content Element IDs__ Make sure that the content element "c-ids" (Content Element IDs) are available within your frontend template, e.g. "c908". 5. __Content Element on current Page__ For now only all content elements on the current page are "editable". So if you 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. 6. __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.

License

This project is licensed under GNU General Public License 2.0 (or later).

All versions of xima-typo3-frontend-edit with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
typo3/cms-backend Version ^12.0 || ^13.0
typo3/cms-beuser Version ^12.0 || ^13.0
typo3/cms-core Version ^12.0 || ^13.0
typo3/cms-fluid Version ^12.0 || ^13.0
typo3/cms-frontend Version ^12.0 || ^13.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package xima/xima-typo3-frontend-edit contains the following files

Loading the files please wait ....