I'm leaving these strings untranslated for now because I'm not sure that
we'll want all of them as-is, and I don't want to have our translators
translate strings we might not even need.
[MAILPOET-4191]
Having separate objects for validation results is unnecessary and overly
complicated at this point, and we should wait to introduce that kind of
complexity only when/if it's clearly needed.
[MAILPOET-4191]
Segment and Subscriber subjects can be stateful, with specific segments
and subscribers loaded into them, so we should probably get separate
instances of them instead of sharing that state and potentially getting
unexpected behavior.
[MAILPOET-4191]
We need to be able to validate an action in a workflow in the UI,
outside the context of a specific workflow run, so the validation can't
check things like the specific entities loaded in a subject.
[MAILPOET-4191]
This makes the subscriber factory match
\MailPoet\Subscribers\SubscriberSegmentRepository::createOrUpdate. Prior
to this change, calling $subscriber->getSegments() after using this
factory would always return an empty collection, even after using the
withSegments method.
[MAILPOET-4191]
The cookie is not set on wp-activate.php page because on the page
plugins are not loaded (or are loaded only when the plugin is
network active).
See https://core.trac.wordpress.org/ticket/23197
[MAILPOET-4249]
I found that container used for WordPress site in acceptance test environment
is not configured to send emails to MailHog and that caused that WP transactional emails were not caught by MailHog.
In this commit I switched sending transaction emails via MailPoet plugin as a workaround.
[MAILPOET-4249]
In a case when translation is not set correctly in a template
(e.g. 'helpTooltipSendPreview': helpTooltipSendPreview)
it's value might be evaluated as null and trigger a deprecation warning on PHP8.1.
[MAILPOET-4243]
