Any ETA on when this will be avaible for v12?

[ReneReiterer]

No description provided.

[MattiasNilsson]

@ReneReiterer There is no ETA for TYPO3 v12 support. This will require a complete rewrite as some hooks/events have been removed for editing.

But all contributions are more than welcome!

[MacGeyer]

Any news about v12 support ?
6 years ago integration in TYPO3 core was planned, now a complete rewrite is needed, is this the end of frontend_editing ?

[MattiasNilsson]

@MacGeyer As I stated before there are no plans at the moment for TYPO3 v12 support. But we are more than welcoming contributions to make this happen!

[stigfaerch]

@ReneReiterer There is no ETA for TYPO3 v12 support. This will require a complete rewrite as some hooks/events have been removed for editing.

@MattiasNilsson
Could these hooks/events be reintroduced in the core? Why were they removed?

[MattiasNilsson]

@stigfaerch It is basically the related to this deprecation that have been removed in TYPO3 v12:
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/11.4/Deprecation-94953-EditPanelRelatedFrontendFunctionality.html

And mostly this one: typo3/classes/class.frontendedit.php

[DanYouCan]

If for example an upgrade is imminent and the users already know the frontend, then you are faced with an explanation problem.

It is generally a question of whether this function is a must in TYPO3 or not? I think that if you limit the user rights and functions for content editors to the essentials, you can perhaps do without frontend editing. User rights are a strength of TYPO3.
Of course, it would be all well and good if frontend editing were still available.

[MattiasNilsson]

A new version of the old fe edit is in place for TYPO3 v12: https://github.com/georgringer/feediting

[DanYouCan]

Thanks for the information. Good to know that things are moving forward.

[abvdveen]

Isn't this relatively easy to fix by restoring the removed Typo3 11 code, as seen in this diff: https://forge.typo3.org/projects/typo3cms-core/repository/1749/revisions/f56c5edaa64b30a3ddbe04920b0813fc2b6f6da3/diff, is a separate extension?

[MattiasNilsson]

@abvdveen The link you have sent is broken.

[abvdveen]

@MattiasNilsson Was a markup issue, using the link-button in the comment field. Works now.

[abvdveen]

@MattiasNilsson Actually, it doesn't - only in the preview. So you have to cut and paste the link in your browser.

[MattiasNilsson]

@abvdveen Yeah it may be possible. We are open for all the contributions!

[tomleiter]

any news?

[MattiasNilsson]

@tomleiter None, but we are open for contributions!