DEPRECATION WARNING

This documentation is not using the current rendering mechanism and will be deleted by December 31st, 2020. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.

Setting up front-end editing

Only do this if you really trust your users to only enter serious events and no fun or test records.

Front-end users can edit an event either if they are the owner of that event, or if they are a manager for that event (or in the general “managers” front-end user group) and front-end editing is enabled for managers.

  1. Create a system folder where front-end created event records will be stored. If you like, you can also use your existing event records folder for that. Either way, note the PID of this system folder.
  2. Create a front-end user group for the front-end users that are allowed to enter and edit event records in the front end. Write down the UID of that group.
  3. Add all front-end users that should beallowed to enter and edit events to that group.
  4. Create a page “Enter/edit events” and allow access exclusively to users of that front-end user group.
  5. Add a Seminarmanager plug-in to that page and set its type to “Event Editor”.
  6. In the tab “Front-end editing”, select the front-end group that is allowed to edit events. Alternatively, you can set this using the TS setup variable plugin.tx_seminars_pi1.eventEditorFeGroupID.
  7. Select the system folder where the created events will be stored. Alternatively, you can set this using the TS setup variable plugin.tx_seminars_pi1.createEventsPID.
  8. Select the the page that will be shown when an event has been saved. This can be the page with the user-entered events (which we will create in the next page) or a separate thank-you page. Alternatively, you can set this using the TS setup variable plugin.tx_seminars_pi1.eventSuccessfullySavedPID.
  9. Create a page “Events which I have entered” (or “My events”) and allow access exclusively to users of that front-end user group.
  10. Add a Seminarmanager plug-in to that page and set its type to “Events which I have entered”.
  11. In the first tab, select the system folder where front-end-created events are stored as data source from where to fetch the event records.
  12. In the second tab, you probably want to select “all events” as time- frame.
  13. In the tab “Front-end editing”, select the front-end group that is allowed to edit events. Alternatively, you can set this using the TS setup variable plugin.tx_seminars_pi1.eventEditorFeGroupID.
  14. Select the page with the event editor plug-in (that is the page which you have just created). Alternatively, you can set this using the TS setup variable plugin.tx_seminars_pi1.evenEditorPID.
  15. If you need, configure which files may be uploaded by providing a comma-separated list of file-extensions to plugin.tx_seminars_pi1.allowedExtensionsForUpload or the corresponding Flexforms field. By default, many text-, image-, office- and archive- filetypes are allowed (see Reference section).
  16. If needed, the maximum upload file size can be configured in the install tool.Be aware that, if the maximum upload file size in PHP is set to a lower value than the one in TYPO3, the FE editor cannot show an error message if one tries to upload a too large file.