in2code-de/powermail_cond

Add conditions (via AJAX) to TYPO3 powermail forms for fields and pages

TYPO3 Extension powermail_cond

Conditions for TYPO3 extension powermail. While a user fills out a form, some fields should disappear, while others should be visible.

⚠️ TYPO3 12 compatibility
See EAP page (DE) or EAP page (EN) for more information how to get access to a TYPO3 12 version

Screenshots

List of Conditions you can apply on the powermail form fields

• is set
• is not set
• contains value
• contains value not
• is
• is not
• is greater than (numbers only)
• is less than (numbers only)
• contains value from field
• contains not value from field

Quick installation

Quick guide:

• Just install this extension - e.g. composer require in2code/powermail_cond
• Clear caches
• Add a powermail form to any page
• Add a new record from type "condition container" to a sysfolder and configure it
• Don't forget to include the static template from powermail_cond
• Don't forget to add jQuery to your frontend (if not yet installed)

Example routing configuration for TypeNum 3132:

...
rootPageId: 1
routes:
  -
    route: robots.txt
    type: staticText
    content: "Disallow: /typo3/\r\n"
routeEnhancers:
  PageTypeSuffix:
    type: PageType
    default: /
    index: ''
    suffix: /
    map:
      condition.json: 3132
...

Local Development and Contribution

There is a docker based local development environment available. See Readme.md for more information.

Early Access Programm (EAP)

You can support the development via our EAP on https://www.in2code.de/en/agency/typo3-extensions/early-access-program/ Also official (fee-based) support is possible within the EAP.

This is the current status of the EAP features:

Version	TYPO3	PHP	Support/Development	Status
10	11 LTS	7.4, 8.0, 8.1	Support for TYPO3 11 and Powermail 10	available
11	12 LTS	8.0, 8.1	Support for TYPO3 12 and Powermail 11 / 12	available

Changelog

Version	Date	State	Description
11.1.0	2023-10-16	Feature	Support Powermail 11 & 12
11.0.0	2023-07-05	Feature	Support Powermail 11
10.1.1	2023-03-23	Bugfix	Fix possible undefined array key error
10.1.0	2023-03-14	Task	Support all kind of powermail fields as with jQuery before (e.g. submit, text, etc...)
10.0.0	2022-10-10	Feature	Support for Powermail 10 and remove of jQuery support
9.0.4	2022-10-10	Bugfix	Allow multilanguage conditions
9.0.3	2022-07-05	Bugfix	Fix ext_emconf.php for TER upload via REST API (another change)
9.0.2	2022-07-05	Bugfix	Fix ext_emconf.php for TER upload via REST API
9.0.1	2022-07-04	Bugfix	Fix page fieldset conditions not being applied correctly
9.0.0	2022-02-23	Feature	Support for TYPO3 11 and Powermail 9
8.2.2	2021-11-22	Bugfix	Reverted type change for field condition.target_field and updated index configuration for this field
8.2.1	2021-11-22	Bugfix	Use integer field for condition.target_field
8.2.0	2021-11-22	Task	Add mysql indices, hide children tables in list view, add code linting tests
8.1.1	2021-08-04	Task	Simplify TCA to also fix the start/endtime bug in TYPO3 (last regression)
8.1.0	2021-03-18	Feature	Add TER autodeployment, add extension key to composer.json, small doc fix
8.0.3	2020-04-30	Bugfix	Enforce content-type in TypoScript
8.0.2	2020-04-30	Bugfix	Also support checkboxes (array values) in powermail 8
8.0.1	2020-04-29	Task	Add useless dependency to TYPO3 for TER upload
8.0.0	2020-04-29	Task	Update extension for powermail 8 and TYPO3 10.4
7.0.0	2018-11-16	Task	Update dependencies for powermail 7
6.1.0	2018-10-21	Task	Remove deprecation warnings in TYPO3 9.5
6.0.0	2018-10-16	Task	Support powermail 6.1
5.0.0	2018-05-24	Task	Support powermail 6.0
4.1.1	2018-03-28	Bugfix	Prevent exceptions in log
4.1.0	2018-01-29	Task	Remove dependencies for TYPO3 7.6
4.0.0	2018-01-15	Task	Update dependencies for powermail 5.0
3.5.2	2017-12-05	Bugfix	Turn of ConditionAwareValitor on fields without page relations
3.5.1	2017-12-13	Bugfix	Prevent exceptions in backend for MySQL strict mode
3.5.0	2017-11-13	Task	Update dependencies for powermail 4.x
3.4.0	2017-08-14	Feature	Allow all fieldtypes for target, add JS compression
3.3.4	2017-07-25	Bugfix	Reduce unneeded calls in frontend
3.3.3	2017-06-12	Bugfix	Small change for MySQL strict mode
3.3.2	2017-05-20	Bugfix	TCA update for TYPO3 8.7
3.3.1	2017-04-25	Bugfix	Fix package name in composer.json
3.3.0	2017-04-23	Task	Move ext to github, make it fit for TYPO3 8.7 LTS

More to come soon?

• Use vanilla JS instead of jQuery

Conflicts

• It's not possible to use powermail multistep forms with powermail_cond

powermail_cond's Issues

?type=3132 Error

Hello,
i use TYPO3 9.5.5, Powermail 7.3.0 and Powermail Conditions 7.0.0.

I can't get Powermail Conditions to work.
I have a request form and some fields should pop up when the condition is met. But the fields are always showing and it isn't just working

The console throws me the following error:
POST https://URL/index.php?id=3?type=3132 500 (Internal Server Error)

and the error in TYPO3:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: Argument 1 passed to In2code\PowermailCond\Controller\ConditionController::setTextFields() must be an instance of In2code\Powermail\Domain\Model\Form, null given, called in /www/htdocs/URL/typo3conf/ext/powermail_cond/Classes/Controller/ConditionController.php on line 53 | TypeError thrown in file /www/URL/typo3conf/ext/powermail_cond/Classes/Controller/ConditionController.php in line 69. Requested URL: https://URL/index.php?id=3?type=3132

The Submit Button also doesn't work when Powermail Conditions is enabled.
If I disable Powermail Conditions, Powermail works just fine.

Could somebody help me to fix this problem?
Thanks

Multilanguage Issue with extended powermail classes

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.

"invalid integer value" on creating new rule

Due to the new strict mode, there is this error thrown.

Copying forms together with condition containers breaks field relations

Given the case I have a standard Typo3 folder page type with one form and and a handful of condition records applied to the form. After copying the complete folder which means the form and all related records are copied, as also the condition container with its related records, the field relations inside the condition records are broken. They still point to the original form by uid. Even though I understand this behaviour and could imagine that it is not trivial for Typo3 to handle such relations, it would be really wonderful and an important improvement when these field relations would be set properly. Properly means that the field relations of the condition records point to the respective fields of the new copy of the original form. Thereby it would be very easy to duplicate a given form-condition pairing.

Conditions on multi page forms?

Conditions only work on the first page on a multi page form.

Is there any chance in the near future to get this implemented on every page of the form?

Best regards,
Jürgen

Condition not working when ratio button is set to "Ja | 1 | *"

Hi Alex,
ok, at least I decided to make my form not on a multi step form because of powermail_cond.

But I found now, that the condition is not working when I did set a ratiobutton like

Ja | 1
Nein | 2

i need the value set to 1 or 2 for further purposes, but doing like this the condition is not working anymore.
Only when the ratio button is simply set to
Ja
Nein

Can you please check this.

Thanks and best regards,
Jürgen

Failed to load resource in Safari 11.1 using file input field in form

With the latest Safari Version 11.1 Powermail Condition throws an error "Failed to load resource: The operation couldn’t be completed. Protocol error" when using a file input field. The conitions don't apply and all fields are visible. Removing the file field then the error disappears and the form works fine.

Call to a member function exec_SELECTquery() on null

Hi there,

i installed powermail_cond and got the following error after trying to active a new record in a sys folder:

(1/1) Error
Call to a member function exec_SELECTquery() on null

Typo3 Version: 9.5.0
Powermail Version: 6.1.0
Powermail_cond Version: latest (6.0.0)

clear/reset input value on hiding field

In case a dependent mandatory field was filled and then hidden by the user via condition, the value remains when submitting and the form cannot be submitted.
It is necessary to delete/reset the entries/selections when hiding fields by condition.

Version compatible with Powermail ^10

Hi,

I wanted to update powermail_cond on a TYPO3 v11. Here is also already powermail v10 installed. But it seems that the maximum supported version is 9.9.99.
Is this something that slipped through or is the current version not yet compatible with powermail v10?

Error Log:
Problem 1
- in2code/powermail_cond[9.0.0, ..., 9.0.3] require in2code/powermail ^9.0 -> found in2code/powermail[9.0.0, 9.0.1, 9.0.2] but it conflicts with your root composer.json require (^10.0).
- Root composer.json requires in2code/powermail_cond 9.0.* -> satisfiable by in2code/powermail_cond[9.0.0, 9.0.1, 9.0.2, 9.0.3].

Thanks for your support,

Maximilian Schweiger

Version compatible with TYPO3 V11

Hi,

Is there any plan to upgrade this extension to TYPO3 V11 ?

Thanks for your work.
Florian

TCA definition of tx_powermailcond_domain_model_condition.l18n_parent

The foreign_table leads to old non existing tables.

SQL error: SQLSTATE[22007]

Whenever I want to create a rule I get the following error:

2: SQL error: 'SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect integer value: '' for column my_database.tx_powermailcond_domain_model_rule.equal_field at row 1' (tx_powermailcond_domain_model_rule:NEW5edd12ff6203e885562589)

Environment:
TYPO3 10.4.3
PHP 7.3.8
MariaDB: 10.3.16

Will condition testing in future be in frontend?

Hi Alex,

I have a question:

we encountered that if a form has a powermail condition (or more)
that an ajax request is sent for every field in the form when focusout or change event takes place.
This results in a high server load (even until collapsing) if a lot of users are using this form parallely, for example after a newsletter with a link to the form has been sent out and e.g. 6000 users are visiting the form. My question now is, if it is planned to do the condition testing only in the frontend or do we have to create something by ourselves for such purposes?

Thank you for your answer in advance :)

Cheers
Christian

[BUG] Servier-Side Validation is not disabled on hidden by condition field.

Caused by
2f4d0d3#diff-70a09ddce344d5780d1e799fa2eb26f7R64

        $formUid = $form->getUid();
        $pageUid = $parentPage->getUid();
        $marker = $field->getMarker();
        
        if (ConfigurationUtility::isReplaceIrreWithElementBrowserActive()) {
            /** @var Page $page */
            foreach ($form->getPages() as $page) {
                /** @var Field $field */
                foreach ($page->getFields() as $field) {
                    if (!empty($arguments[$formUid][$pageUid][$marker][Condition::INDEX_ACTION])) {
                        if ($arguments[$formUid][$pageUid][$marker][Condition::INDEX_ACTION] ===
                            Condition::ACTION_HIDE_STRING) {
                            return;
                        }
                    }
                }
            }

the array keys in each loop are the same

AJAX loader icon

Hi there,

is it be possible to integrate a simple loader icon for the ajax request?

I think that some users won't be aware of the moment when two overlapping fields have been toggled – steered by a hide/unhide condition.

Maybe a .loader class could be shown initially and hides when ajax succeeds?

Many thx in advance and best regards
Martin



powermail_cond & powermail 7.x.x

Hello Alex,

will there be a version for powermail 7.x.x?
or is this version working with powermail 7.x.x?

currently it depends on powermail 6.1.0

best regards

Why sent file uploads to the backend for evaluation?

Since only fields of the types

• input
• textarea
• select
• radio
• check

can be selected as start_field why sent all inputs to the backend for evaluation purposes? In #59 we've created a way to exclude certain types from being submitted to the condition.json route. But now I'm thinking about whether it might be even better to exclude file fields per default when they can't be used in conditions anyway. @einpraegsam, what's your opinion on this?

Textarea mandatory

Hi all,
I use powermail 3.17.0 and powermail_cond 3.2.1. I've created condition for textarea:
if some checkbox is checked, then unhide textarea
This textarea is mandatory and when I check the checkbox textarea's attribute "disabled" changes to "required". And it looks fine.
When I don't check the checkbox the textarea is hidden, but after click "Send" I've got powermail validation error ABOVE form: "Textarea is mandatory" generated by:
<f:render partial="Misc/FormError" arguments="{_all}" />
The question is, why powermail don't let to send form when textarea is hidden and disabled and has no "required" attribute in source (checkbox is not checked)?

Powermail 9.x compatibility

Are there any current plans to update powermail_cond for Powermail 9.x?
Possibly a "beta" as with the Powermail 9 update?

unable to load powermail form

we use version 3.5.2, but it looks this may happen on 6.1 as well.
in some rare cases powermail_cond is not able to fetch a form object and generates an exception

Uncaught TYPO3 Exception: Argument 1 passed to In2code\PowermailCond\Controller\ConditionController::setTextFields() must be an instance of In2code\Powermail\Domain\Model\Form, null given, called in /typo3conf/ext/powermail_cond/Classes/Controller/ConditionController.php on line 60 | TypeError thrown in file /typo3conf/ext/powermail_cond/Classes/Controller/ConditionController.php in line 77.
Requested URL: ...../online-antrag/?type=3132

one work around could be (in version 3.5.2)
In2code\PowermailCond\Controller\ConditionController starting at line 59

        $form = $formRepository->findByIdentifier($this->powermailArguments['mail']['form']);
        $this->setTextFields($form);

to

        $form = $formRepository->findByIdentifier($this->powermailArguments['mail']['form']);
        if (is_null($form)) return null;
        $this->setTextFields($form);

Form not submitted with powermail 6.1.0

Hi Alex,

I today deployed powermail 6.1.0 and discvored that there is a bug with powermail_cond 5.0.0.
I use both extensions on TYPO3 8.7.17.

The bug is:
If the user submits the form it gets the server validated messages that some of the fields (the undisplayed ones by conditions) have not been filled out.

I switched then back to powermail 6.0.0 and after this the form was successfully submitted.

Thank you for checking this out :)

Best regards
Christian

Call of reInitializeParsleyValidation should be reduced

After every call of derequireField or rerequireField the method reInitializeParsleyValidation gets called. This results in a lot destroy and initialize of parsely. The the form contains a lot of fields this sums up to a lot of processing time.

If the call is only done once after the form was processed this would speed up the validation a lot.

[solution] powermail_cond at multiple language

I have the same form at 4 languages.

At the default it works, the other not.

For it to work i changed this Line:
In2code\PowermailCond\Controller\ConditionController : Line 56
$conditionContainer = $containerRepository->findOneByForm($form);
to
$conditionContainer = $containerRepository->findOneByForm($this->powermailArguments['mail']['form']);

SendMailService needs SignalSlot to overwrite variables in latest step

We have a lot of signal slots in the extension, but no way to overwrite the mail data in the latest part of the SendMailService before the real mail is send.

Scenario:
A customer fills the input field for email in the frontend form. The email should not trigger a real mail transport, because it is an test email address. (Frontend testing)

It must be possible to step into the sendmailservice with in signal hook, to overwrite or reset the senderEmail, receiverEmail, subject, etc.

Needs:

• Original Mail object with emailadress from the form field (email)
• Receiver/sender and subject data

A better solution is probably overriding the TypoScript settings (this-> settings ['receiver'] ['enable'] = 0). Overwriting the "$ this->settings" must then be possible via a signal slot in the FormController::createAction() based on the submitted form data (email input field).

powermail_cond breaks the confirmation function if ajaxSubmit is enabled

The form submit does not work if ajaxSubmit and the confirmation page is enabled and the user goes back to the form from the confirmation page. The form cannot be sent to the confirmation page again. Without powermail_cond or deactivated ajaxSubmit everything is fine.

It seems that the with powermail_cond hidden fields are required but are hidden to the user if he comes back from the confirmation page. So the form can not be submitted again.

TYPO3 8.7.24
powermail 7.2.0
powermail_cond 7.0.0
PHP 7.3
composer mode

Version compatible with TYPO3 v9 and v10

Hi, we love this extension!

Is there a plan to upgrade it to be compatible with TYPO3 v9 and v10 - and with that also to Powermail v8?

If not: why? If yes: any way we could support you on that?

Package from packagist.org installs to wrong directory

Package installs to "powermail-cond" instead of "powermail_cond"

Exception "No powermail parameters are given" on translated pages

On pages with translations and Powermail forms (powermail_cond active), I get the following error message:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: No powermail parameters are given - e.g. &tx_powermail_pi1[mail][form]=123 | Exception thrown in file /var/www/vhosts/my-domain/typo3conf/ext/powermail_cond/Classes/Controller/ConditionController.php in line 47. Requested URL: http://my-domain/en/page-with-form/

The error is not shown, when I open the page with a click on the "view webpage" button in the backend. Then it opens with no speaking URL (http://my-domain/index.php?id=251&L=1). Maybe it has something to do with realurl?

A tip or solution would be great!

Best regards
Clemens

Compatibillity with powermail > 9.99.99

The current version of powemail_cond (9.0.3) is marked to be only compatible with powermail 8.3.2 - 9.99.99.

Therefore it is currently not possible to use the latest powermail version 10.4.1.

Is it really incompatible or is just the definition of the restriction/requirement wrong?

Field selection

When adding a new codition all fields of all forms are shown. Only after saving the condtion the field list ist reduced to fields of the selected form are shown. It would be nice that after adding a rule only the fields of the selected form are shown in the field select.
Version 5.0.0 T3 8.7.x

parsley error messages disappear after every ajax call

Error messages, which are shown before the powermail_condition ajax call is fired, immediatly disappear with the ajax call.

For usabilty reasons this not acceptable for the user.

powermail 5.6
powermail_cond 4.1.1
TYPO3 8.7.13

Condition takes long with filled upload field

PHP: 7.2.x
TYPO3: 8.7.18
powermail: 6.0.0
powermail_cond: 5.0.0
Browser: Latest Firefox, Chrome or Edge

Hi Alex,

I have a multi-language form (DE and EN) with three conditions on radio elements and three upload fields. If the upload fields are empty the conditions work fast (i. e. the field(s) to be displayed appear quite immediately), but if one of the fields is filled with a file then it takes at least one minute until the field(s) to be displayed appear).

While investigating this I also found in the TYPO3 protocol that I got a warning about the function setTextFields in In2code\PowermailCond\Controller\ConditionController in case the argument to the function is null. After changing the type hint to "?Form" it seems to be fixed.

Maybe I can get back to this topic and send you a pull request if I think that I have a solution.

Cheers
Christian

Take few seconds to react

TYPO3: 8.7.27
powermail: 7.3.1
powermail_cond: 7.0.0

Hello,
I'm using powermail_cond to display some parts of the form after choosing an answer from a select. But, it takes few seconds to react, even to prepare the form before interaction. It's worse in a second language, it's take more than 5 seconds. Is it possible to reduce reaction time? Thanks!

Christiane

[BUG] powermail_cond not compatible with powermail 6.0.0

Please allow powermail >=6.0.0 in the package requirements. Thanks

TYPO3 v11 dependency

The ext_emconf.php still depends on older Powermail.

 'depends' => [
            'powermail' => '8.3.2-9.99.99',

Shouldn't this be something like this?

 'depends' => [
            'powermail' => '9.0.0-10.99.99',

Powermail Fieldwrap Elements not hidden by powermail_cond

Hi all,

i have updated a TYPO3 Instance and now i a'm facing the problem that powermail_cond is not hiding fields. Input fields are correctly disabled but css style ="display:hidden" is not set to these fieldwraps as it should be.

I checked the network stream and all is working fine. The page call of type=3132 is giving right fields with #action : "hide". But fields are visible.

Powermail_cond is working, cos when the condition switches the input disabled property to enabled.

Any hint for this problem? Can there be a conflict with other js code?

TYPO3 8.7.4
Powermail 3.22.1
Powermail_cond 3.4

Dependency in version 9.0.3 is wrong

Hello
In the ext_emconf the dependency for powermail is wrong, because it only includes versions up to 9.99.99, but powermail is currently at 10.4.2, so it could only be installed from TER if the risk exception is accepted.
No functional problems only an installation issue

[FEATURE REQUEST] additional action "derequire only" without hiding field

In a current project, at least phone or email should be specified in the form. I have declared both fields as mandatory. If only one is filled, then the other must become optional.
In this case the field may only be derequired derequireField($field); but not deactivated $field.prop('disabled', true); in hideField = function(fieldMarker, $form)
For this purpose, there should be an additional action "derequire only" in addition to the existing actions "show" and "hide".

Conditions with "unhide" rule always visible on iOS 11.3

Hi there,
I'm using Powermail v5.5.0 with Powermail Conditions v4.1.1 in Typo3 8.7.11.
On iOS 11.3 display: none; isn't applied anymore to fields that should be hidden by default and only be opened with the unhide-condition.
It's still working as expected in iOS 11.2.5.
Anyone else fighting this bug, any suggestions what to do?

Multilingual Conditions possible?

Hey there, is it possible to have multilingual conditions? At the moment I struggle a little bit with a form in several languages. When I have a condition with 2 or more rules with AND conjunction, I have not found a way to have this condition applied to several languages. It feels like they keep overriding each other.

It seems like I have to try to rebuild the complete form in order to somehow avoid conditions with more than 1 rule.

Bug Workspace/ PowermailCond

Hi,

PowermailCond and Workspaces seem to not work together.
We have a powermail form with PowerMail Cond conditions.
The conditions work correctly on this form.
But, if you switch to worspace mode, any conditions work.

We are using TYPO3 9.5.20 and powermailCond 7.0.0

Anyone have an idea?

Powermail opt-in confirmation breaks for cross browser functionality

Hi @einpraegsam,

we got some struggle with cross browser functionality and opt-in confirmation because sometimes $arguments were null inside ConditionAwareValidator.

We could reproduce this with the following setup:

1. Create a form with some mandatory fields
2. Create a condition to make one of these mandatory fields optional
3. Submit the form (e.g. with Chrome)
4. Confirm the opt-in email with another browser (e.g. with Firefox), maybe private mode will work as well here

After clicking the confirmation link the error message:

Validation failed while trying to call In2code\Powermail\Controller\FormController->createAction()

will be triggered, because $arguments were null and the validator will complain about a mandatory field that is not set because the powermail_cond-Session is missing. To fix this issue we have added the following condition to ConditionAwareValidator:

if ($arguments === null) {
    return;
}

What do you think about it?

All powermail forms throw TYPO3 Exception with powermail_cond installed

Just encountered a problem on a large multilanguage multi-domain installation. Even without using a condition, just by having powermail_cond installed i get the following error on all pages with powermail forms when i submit:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getForms() on null | Error thrown in file /var/www/servers/mydomain/html/typo3conf/ext/powermail_cond/Classes/Domain/Validator/ConditionAwareValidator.php in line 54. Requested URL: https://www.mydomain.com/en/contact/?tx_powermail_pi1%5Baction%5D=create&tx_powermail_pi1%5Bcontroller%5D=Form&cHash=a2d59893a4d0f551dc4a063bc57d61eb

Additionally Chrome shows a ERR_BLOCKED_BY_XSS_AUDITOR page. If I disable powermail_cond, everything is fine. Unsure how to debug this or if this is even an issue with the extension or my configuration. Updated to most recent powermail and powermail_cond but no change.
Any ideas?

Deprecated keys in 'ext_emconf.php'

Hi Alex,
I just saw that you use some deprecated keys in ext_emconf.php in powermail_cond 7.0.0.
They are 'shy','dependencies', 'conflicts', 'priority','loadOrder','modify_tables','lockType','CGLcompliance' and 'CGLcompliance_note'

Maybe you remove them in the next version.

Cheers
Christian

TYPO3 v11 Support?

Hello,
Thank you for your great extension.
are there already plans to get powermail_cond compatible for TYPO3 v11?

Powermail 10.x compatibility

Could you release a new version in a timely manner in which Powermail 10.x. is allowed in the Composer.json.
Thanks again for the great work

condition can not be triggered by checkbox (?type=3132 Error)

Typo3 10.4.2, powermail 8.2.4. powermail_cond 8.0.1

it is not possible to show/hide any field by clicking a checkbox. This will cause same result as in #39 (....?type=3132 500 (Internal Server Error))
It does not matter if the rule is checks the checkbox value for notEmpty, 1 or a specific value, it all returns the same error. The error occurs also independently from any route enhancer settings.

Powermail_conditions not working in "edit"-mode?

Hello,

I got powermail_cond working for powermail (_pi1). However, it does not work for powermail_frontend (_pi2).
Is this supposed to work? Any reason why it does not?

Thanks in advance for any help on this.

TYPO3 9 LTS: Browser blocks mixed content: proposal how to solve it

TYPO3: 9.5.8
powermail: 7.3.1
powermail_cond: 7.0.0

Hello,

I just discovered that powermail_cond does not work in browsers blocking mixed content on a TYPO3 9 LTS installation : for example in Firefox 68. Here my situation:

I use a powermail form together with a simple powermail_cond condition on a https site.
Investigating the console tab revealed me that the generated absolute ajax url from powermail_cond uses http.

Investigating further I could find the following solution:

If you replace in the typolink declaration of the page property 3132 the value for "forceAbsoluteUrl" by 0
the generated ajax url is relative and hence called via https and the condition works.

Side note: This change is not necessary in TYPO3 8 LTS as there the generated ajax url contains https.
I think the different behaviour of url generation has to do with the site configuration introduced in TYPO3 9.

Cheers
Christian