Skip to content

[FEATURE] Add fields in mail for double opt-in - #1412

Open
sypets wants to merge 2 commits into
in2code-de:typo3-v13from
sypets:add-db-fields-in-mail-for-optin
Open

sypets wants to merge 2 commits into
in2code-de:typo3-v13from
sypets:add-db-fields-in-mail-for-optin

Conversation

@sypets

@sypets sypets commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

Two fields are added in the tx_powermail_domain_model_mail table:

  • optin_needed : is set to true, if double opt-in was required when the form was submitted
  • optin_completed : is set to true, when email is confirmed

Due to these fields, it is now possible to determine if a hidden answer is hidden due to not being confirmed via email yet or has for example been set to hidden by an editor.

Resolves: #1411

Two fields are added in the tx_powermail_domain_model_mail table:

- optin_needed : is set to true, if double opt-in was required when
  the form was submitted
- optin_completed : is set to true, when email is confirmed

Due to these fields, it is now possible to determine if a hidden
answer is hidden due to not being confirmed via email yet or has
for example been set to hidden by an editor.

Resolves: in2code-de#1411
@sypets
sypets force-pushed the add-db-fields-in-mail-for-optin branch from 3654938 to 3451e15 Compare October 10, 2026 18:43
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.

[FEATURE] Be able to differentiate between standard hidden mails and unconfirmed double opt-in mails in database

1 participant