Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config.spamProtectEmailAddresses_atSubst is not working if lux is installed #31

Closed
fixpunkt-systeme opened this issue Oct 27, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@fixpunkt-systeme
Copy link

config.spamProtectEmailAddresses_atSubst and config.spamProtectEmailAddresses_lastDotSubst are not working if the extension Lux is installed.
I guess, the Lux Link Listener overwrites the link build by the EmailLinkBuilder in the TYPO3 core.

@einpraegsam
Copy link
Contributor

einpraegsam commented Oct 27, 2022

I can confirm that also

config.spamProtectEmailAddresses = 10
config.spamProtectEmailAddresses_atSubst = @<span hidden>no spam</span>

does not replace the visible email address (the link works as expected), if the address is generated like
<f:link.email email="service@in2code.de"/>
on the latest TYPO3 11 and the latest LUX version.

@einpraegsam einpraegsam added the bug Something isn't working label Oct 27, 2022
@einpraegsam
Copy link
Contributor

einpraegsam commented Oct 27, 2022

I played a bit with it and it seems that this is not an issue of LUX but more in TYPO3 itself. The error is only reproducable in TYPO3 11 (and not in 10).
If the hook is registered (not even used), the email links are broken at once.
Example hook usage:

// hook registration in ext_localconf.php
$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['typoLink_PostProc'][]
            = \In2code\Lux\Hooks\LuxLinkListenerLinkhandler::class . '->postProcessTypoLink';

It makes no difference if the target function simply does nothing with a return

I also searched forge for the problem, and found an existing issue: https://forge.typo3.org/issues/98606 (I also described the problem there)

@einpraegsam
Copy link
Contributor

Should be fixed as far as I see in forge now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants