Skip to content

[BUGFIX] Resolve lazy-loading proxies in the Powermail validator (TYPO3 14) - #65

Closed
dirnbauer wants to merge 1 commit into
studiomitte:mainfrom
dirnbauer:fix/powermail-lazy-proxies
Closed

dirnbauer wants to merge 1 commit into
studiomitte:mainfrom
dirnbauer:fix/powermail-lazy-proxies

Conversation

@dirnbauer

Copy link
Copy Markdown

With powermail on TYPO3 14 the mail's form, pages and fields can be Extbase LazyLoadingProxy instances. isFormWithCaptchaField() iterated them directly and could skip the captcha check. This resolves the proxies, guards the types and widens the validator signatures to mixed to match the parent classes (also satisfies PHPStan).

Extracted from our TYPO3 14 fork, which we are retiring in favour of 2.3.x — thanks for adding v14 support.

🤖 Generated with Claude Code

With powermail on TYPO3 14 the mail's form, pages and fields can arrive as
Extbase LazyLoadingProxy instances; iterating them directly skipped the
captcha check. Resolve the proxies, guard the types and widen the
signatures to mixed to match the parent validators.
@dirnbauer

Copy link
Copy Markdown
Author

Closing — we are keeping this change local instead. Sorry for the noise.

@dirnbauer dirnbauer closed this Sep 12, 2026
@dirnbauer
dirnbauer deleted the fix/powermail-lazy-proxies branch September 12, 2026 16:18
dirnbauer added a commit to dirnbauer/webconsulting-typo3-lab that referenced this pull request Sep 13, 2026
…ings example

The Powermail validator fix from studiomitte/friendlycaptcha-typo3#65 is
applied as a Composer patch once the lab switches to upstream 2.3.x, and
the settings example no longer documents the retired nr_mcp_agent keys.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant