Torben Hansen

I would also say this is a bug. At least it leads to problem when you with with strict types and expect `render()` to return a string. See: https://github.com/einpraegsam/powermail/pull/641

I also created a core patch (see https://review.typo3.org/c/Packages/TYPO3.CMS/+/75448) to prevent the PHP warning, since there is also a problem with content elements that have no FlexForm fields. The patch in...

The problem is, that the current value is invalid and resulting in an error in WCAG tests. TYPO3 core ext:form has those settings (see https://forge.typo3.org/projects/typo3cms-core/repository/revisions/090a852fd0d8b5e1b6062614a4197dbcb6d06a92/diff), which I believe may not...

I adapted the PR, so the autocomplete field can still contain an invalid value, but screenreaders will ignore the honeypot field (added `aria-hidden="true"`). Note, that I also added the form...

> The prefix "new-" must be still at the beginning. Could you change it to `autocomplete: 'new-powermail-hp-{form.uid}'`? Done

Similar problem here in one project. It seems, that calling Fluid ViewHelpers like `

Hm, never thought about this scenario. But yes, this is totally valid and currently not really supported. I could catch the Payment Redirect when the registration is on the waitlist...

Thanks for your PR. I will need to review it carefully (which will take some time) and have some doubt about if all code is really required (e.g. the `Content`...

Thanks a lot for your contribution! I'm currently planning some more features (e.g. partial migration of pagetree), so I will try to merge some of the work on this issue...

See: http://www.derhansen.de/2015/11/typo3-using-fluid-standaloneview-to.html