-
Notifications
You must be signed in to change notification settings - Fork 23
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
Multilanguage Issue with extended powermail classes #53
Comments
I had the same problem with powermail_cond rules in combination with translated forms. Your solution is solving the problem. Would be nice to be fixed officialy, so we don't have to exclude the extension from updates :-) |
TYPO3: 10.4 / Powermail: 8.2.4 / powermail_cond: 8.1.0 |
Same problem here with translated forms. Everything works fine with this solution! |
We had the following use case: TYPO3 10.4.12 and EXT:powermail 8.2.4 and EXT:powermail_cond 8.0.1 (also tried 8.0.3 from github) and subclassed Powermail Domain Model Classes because of extra TCA fields done the following way with XCLASS + registerImplementation() instead of using config.tx_extbase.objects TS (as it is still in the official EXT:powermail documentation btw.):
https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.5/Deprecation-86270-ExtbaseXclassViaTypoScriptSettings.html
This had the side effect that the EXT:powermail_cond rules JSON was only being filled with data in default language, but not in translation languages of the frontend because \In2code\PowermailCond\Controller\ConditionController::buildConditionAction() line 65 returned no Condition Container in translated frontend languages. So a quick and easy solutation was for us to change this line from:
$conditionContainer = $containerRepository->findOneByForm($form);
to
$conditionContainer = $containerRepository->findOneByForm($form->getUid());
Now we have the EXT:powermail_cond rules json data again in all languages. I guess it had to do with $form not being not of class \In2code\Powermail\Domain\Model\Form but in our case of \OURVENDER\Ourextension\Domain\Model\Form. But I'm not exactly sure.
The text was updated successfully, but these errors were encountered: