BenReppe
Community Manager
Community Manager

DXM Release Notes – 5 Oct 2022

October 5, 2022

This release allows support for TinyMCE custom plugins and changing versions as well as a number of bug fixes.

3rd Party plugin Support for TinyMCE Wysiwyg Editor

We have added the ability to support custom plugins in our WYSIWYG Editor (TinyMCE). Custom plugins are supported in Tiny MCE 4, 5 and 6. Please contact Support or your TAM to have this enabled.

Support for different versions of TinyMCE

The DXM WYSIWYG can now support different versions of TinyMCE.

Ability to switch versions of TinyMCE

We have added the ability for customers to change from their current version of TinyMCE to a newer version which may offer additional functionality. This means that customers with custom plugins as described above can remain on the current version of TinyMCE, whereas those who prefer to upgrade can do so as well. Adding this support to your CMS instance would need to be requested through Crownpeak Support. This flexibility means more choice for customers.

Setting up Custom Plugins:

Once enabled, to use an external plugin, you will need to add a WysiwygParams property named ExternalPlugins to Input.aspx of a template.

Below is a sample piece of code. First, create a KeyValuePair list object which contains objects having a key as the name of the plugin and value as the hosted URL of the plugin.

List<KeyValuePair<string, string>> externalPluginList = new List<KeyValuePair<string, string>>

{new KeyValuePair<string, string>("pluginNameA", "https://exampleServer.com/development/TinyMCEPluginA/plugin.min.js")

};

wParams.ExternalPlugins = externalPluginList;

Input.ShowWysiwyg("wysiwyg content", "wysiwyg", wParams);

 

Output.aspx should resemble this:

<%@ Page Language="C#" Inherits="CrownPeak.Internal.Debug.OutputInit" %>

<%@ Import Namespace="CrownPeak.CMSAPI" %>

<%@ Import Namespace="CrownPeak.CMSAPI.Services" %>

<!-DO NOT MODIFY CODE ABOVE THIS LINE->

<%@ Import Namespace="CrownPeak.CMSAPI.CustomLibrary" %>

<%@ Import Namespace="Component_Library.Component_Project.Components" %>

<% //MODIFY or ADD Import Statements to Define Namespaces Used by the Template %>

<%//This plugin uses OutputContext as its context class type%>

 

<%= asset["wysiwyg"] %>

DXM Improvements

  • Support for .webp and .svg files: Added support for .webp and .svg files in CMSAPI.IMG including displaying image and metadata. 00149086, ZD69828, 00159741
  • Remove WCO auto beacon: fixed an issue where auto beacon was causing CORB error. ZD 69452
  • UI Not Saving System Variables: fixed an issue where the UI was not saving system variables in the system configuration section. ZD 69080
  • Content in panels duplicated: fixed and issue where some content was being duplicated upon saving. ZD 20201, 71610
  • Route Screen Path Cutoff: Added a tool tip to provide the full path.00156306, 00155780
  • WCO ReCaptcha not working: fixed an issue with ReCaptcha in WCO. 00135360, ZD 19157
  • Branching Job Does not update UI: fixed an issue where the UI was not being updated when using transactional branching
  • New Publishing: fixed an issue where if nav wrapper path is incorrectly set in the template an error is not shown in the CMS.

 

Picture2.png

Labels (1)

Have an idea

Have an idea to improve DXM?

Let us know !

Submit an idea

Can't find what you are looking for?

Find Answers

Search our DXM Forum to find answers to questions asked by other DXM users.

Ask a Question

No luck? Ask a question. Our Product and Support teams are monitoring the Forum and typically respond within 48 hours.

Ask a Question