Alexander Kellner
Alexander Kellner
@mschwemer Are you interested in running the behaviour tests against this feature?
You could check if parsley allows such an option in a newer version: http://parsleyjs.org/
Please describe exactly how to reproduce the issue (what kind of configuration I have to do to see the same error) that you want to fix with that PR.
plugin.tx_powermail.settings.spamshield.enable=0 in constants will turn it off. But it seems that a functional cookie is set if any spamshield method is active at the moment.
I just tried with a single checkbox, but can't see a problem in the JS validation. What else should I do to reproduce this issue? ![Screenshot 2022-09-09 at 22-41-16 Powermail...
Because we have the same issue for our client, we just use a small workarround by adding [] to the checkboxes name: `
I just tested powermail 7.4.0 (with latest TYPO3 9) and powermail 8.2.4 (with latest TYPO3 10) with this test settings: ``` plugin.tx_powermail.settings.setup.receiver.overwrite.replyToEmail = TEXT plugin.tx_powermail.settings.setup.receiver.overwrite.replyToEmail.value = [email protected] plugin.tx_powermail.settings.setup.receiver.overwrite.replyToName = TEXT...
This is already fixed with commit db3e08e1d6b48dc319d40a114719aec867e949bf - and will be released with the upcoming version.
I just tested on my machine and can't see a problem. Tested on Firefox on Ubuntu. Any hints for me?
Sounds for me like a caching or autoloading issue