Daniel Siepmann

I'd like to use https://github.com/FriendsOfTYPO3/tea/issues/859 as a base and add a test for this. But I've never done a frontend user login / authentication / simulation yet. That would be...

I opened an issue on TYPO3 as Extbase does not support 201 with location header yet: https://forge.typo3.org/issues/102529 But Browsers (tested with Firefox) also do not support 201 with location header....

@lukaszuznanski do you still know what this was about? The extension is currently published to docs.typo3.org: https://docs.typo3.org/p/ttn/tea/main/en-us/ The local rendering is documented at https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/WritingDocsOfficial/LocalEditing.html (https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/RenderingDocs/Quickstart.html#render-documenation-with-docker, https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/RenderingDocs/RenderWithDockerCompose.html#render-with-docker-compose)

No longer needed as TYPO3 v13 will auto add the wizard entries. I'll therefore close this based on @linawolf feedback.

You can add your own DataProcessor before or after the `content-blocks` processor and adjust the variables. But I'm also curious about the concrete example/use case.

`_processed` should contain all fields that are defined via the content block. Also processed, e.g. resolved values for relations if any processing is necessary. `_raw` contains the raw record as...

That feature can be abstracted and combined with existing operating system feature. Instead of adding detection over detection, combined with dedicated database fields, here is another approach: Use tags. Integrators...

Blocks proper tests for this: https://github.com/TYPO3/testing-framework/issues/256

Already worked on this, see commits and Branch feature/46-add-flags-feature (as well as first attempt in branch feature/bot-support which won't make it due to more flexible approach in new branch). Blocker...

I've integrated https://packagist.org/packages/matomo/device-detector within the feature branch already. There is currently no plan to add it to the expression language, as the concept will change. All requests will be tragged...