MailPoet itself requires 6.6 to activate, so the oldest Gutenberg version we could get is 19.6, which is the first that allows WP 6.6 and could be active together with MailPoet. So, we are safe to remove the check for the Gutenberg version for now.
[MAILPOET-6367]
We actually need WP 6.7 and above, no matter what Gutenberg version
is installed. This commit updates the check logic and the warning
message to match this requirement.
[MAILPOET-6367]
Because the group block has deactivated layout settings in the email editor. It is not possible to configure content alignment.
The default value center could break blocks inside the group.
[MAILPOET-6412]
This removes classic.min.css and theme.min.css. Both are loaded only
when a classic theme is active and add additional paddings and margins
that are not reflected in the email renderer.
[MAILPOET-6390]
The condition for top level wrappers was too strong and was
causing that top level blocks in post-content block were also skipped.
It seeks that 0 !== $key is sufficent.
[MAILPOET-6334]
The original workaround was not working for templates that have edits saved in the DB.
The problem was that when the template is saved in the DB the get_block_templates()
returns WP_Block_Template object with post_types as null.
It seems this association is not saved to DB in the core.
[MAILPOET-6334]
The general email template is registered and works with all post types that are
marked as email post types during editor initialization.
[MAILPOET-6356]
The additional templates are registered by integrators.
This way, we will be able to use assets like images from MailPoet's CDN
and also various services from the plugins (e.g. CdnAssetsController)
[MAILPOET-6356]
This commit introduces a new action to trigger registering email templates.
We need a custom action for that because the email editor engine controls
when we register templates and when we don't. Currently, we still skip
registering templates when we detect the site editor page.
[MAILPOET-6356]
We want to use post_type for filtering email templates.
There is a PR that adds this property https://github.com/WordPress/wordpress-develop/pull/7530
but it is not merged.
This commit added the property and also future compatibility check
so that we don't attempt to add it after the PR is merged.
[MAILPOET-6356]
Because Gutenberg RichText component does not render square brackets around the HTML comment.
We need to append those brackets to tag tokens and expected them when we replace tags by their values.
[MAILPOET-6354]
