Installation 

Installing the extension is one command. Making it show anything takes four more steps, because it edits records that belong to website users and neither the records nor the users exist yet.

Requirements 

  • TYPO3 v13.4 or v14.3
  • PHP 8.2 up to 8.5
  • A website user login on the site the editing plugin is placed on. This extension ships none — any frontend login solution will do.

No build step is required. The compiled JavaScript and CSS are part of the package.

Install the package 

composer require sbuerk/modern-extbase-frontend-edit
Copied!

Set it up 

  1. Create a storage folder and configure it as the storage page. Profile records are read from it and written next to it. There is no value meaning "every page" — without one, the plugins query page zero and find nothing.
  2. Place the plugins. Profiles: list on a listing page, Profiles: detail on a detail page, Profiles: edit on the page a logged-in user edits their own profile on. Point the settings at the pages holding the detail and edit plugins, otherwise no links to them are rendered.
  3. Create a profile record and assign a website user as its owner. A profile with no owner is visible in the list and the detail view, and can never be edited in the frontend.
  4. Check the upload limits if profile images are wanted. The extension refuses an image above its own limit with a message; a file above the PHP or web server limit never reaches it, and the visitor sees the server's error instead. Keep upload_max_filesize and post_max_size above the extension's limit — see Image upload.

Configuration describes the settings, both spellings of them, and how to override the templates.

Classic mode 

The extension is developed and tested in composer mode. It carries an ext_emconf.php and has no composer-only dependency, so a classic mode installation is expected to work, but it is not part of the test matrix.

Releases are published to the TYPO3 Extension Repository under the extension key modern_extbase_frontend_edit. The archive uploaded there holds the same files as the package composer installs — the developer documentation, the test suites and the build tooling are in neither.