For Umbraco 14
14.0.2
Patch release that fixes a rendering issue where the head element sometimes would not be rendered correctly and minor bugs in the email editor.
14.0.1
Hotfix for v14 fixing some bugs found after initial release.
14.0.0
First stable release for Umbraco 14, check the release candidate below for details about breaking changes.
14.0.0-rc1
This is the first release for Umbraco 14, it contains a totally re-written UI but should work almost identical to previous versions. Because this is a re-write and since this is a major release we it does contain a number of breaking changes.
Issue with RTE styles and non-admins in Umbraco < 14.4.0. This is a Umbraco issue: https://github.com/umbraco/Umbraco-CMS/issues/17084 that has been fixed https://github.com/umbraco/Umbraco-CMS/pull/17442 for 14.4.0.
TinyMCE, add this to "wwwroot/css/Newsletter-Studio.css":
a {
pointer-events: none;
cursor: text;
}
EmailControlTypeBase removed properties ViewEdit and ViewRender, use backoffice extension points with matching control type alias to configure views. Backoffice extensions must be used, see documentation.
Recipient Providers has a new required property called DisplayNameLocalizationKey that is used during backoffice rendering. Localizations for frontend rendering must be provided by the site implementor
MailAddressCollection has been refactored to use our own type EmailAddressCollection
NewsletterStudioService.ContentAppDocumentTypeAliases has been renamed to DocumentCampaignDocumentTypeAliases since "ContentApp" is not a thing anymore.
E-mail sending-related methods onIEmailServiceProvider has been made async.
E-mail sending-related methods on INewsletterStudioService has been made async
The configuration for background processing of ISendTransactionalEmailRequestFluent has been renamed from NotAsync to NotInBackground and the SendAsync property on SendTransactionalEmailRequest has been renamed to SendInBackground
IRecipientListProvider has two new method: ReportHardBounce and ReportSoftBounce
MergeField, removed the TranslateTextValues since localization is moved to the frontend.
ITranslationService was made internal since translations should be done on the frontend