Skip to main content
MindTouch Success Center

Product release 2018-03-08

Known Issues

 

Touchpoints: Zendesk
Currently, users are unable to create new Zendesk integrations. This will not affect existing Zendesk integrations.

 

Fixes

 

Editor:  Ordered List Types
Fixed an issue that caused ordered lists with <ol type="a"> specified to default to numbers

 

Editor: Dekiscript Blocks
Fixed an issue that caused dekiscript blocks to strip HTML on save

 

Editor: Table Columns
Fixed an issue that caused an extra column to be added to a table when text from one cell was pasted into another cell

 

Editor: Table Content
Fixed an issue that caused content to not appear when copied from a table and pasted outside of the table

 

Editor: Save and Cancel
Fixed an issue that caused the editor Save and Cancel buttons to stop working after clicking Source
 

 

Enhancements

 

Improved Editor Widget Display 
We have standardized the appearance of our navigation, content, and script widgets so they are easily recognizable, draggable, and occupy the minimal amount of space without restricting their functionality. In addition, our script widgets have the ability to expand or collapse to make them easier to work with. We hope these changes will improve your editor experience and appreciate any feedback you may have about them. Please contact your Account Manager, or support@mindtouch.com if you would like to turn these on for your site.

editor-widgets-final.png

 

Upcoming Enhancements

 

Consolidating Control Panel Login Pages
In our journey to provide a more unified login experience, on March 15th we will be redirecting the control panel login page to use /Special:UserLogin to authenticate admins. There will be no observable change in functionality and admins will be redirected back to the control panel once they are logged in. If you have further questions please contact support@mindtouch.com.

 

Path and Content ID Enhancement
On March 22nd, Learning Path and Contend ID-associated pages will be loaded from a new endpoint. Paths will load from https://example.com/@go/path/{id} and Content ID associated pages will load from https://example.com/@go/cid/{id}. This change will not affect existing Path or Content ID URLs. The existing Path endpoint, https://example.com/@lp/{id}, and the existing Content ID query parameter, https://example.com/?cid={id}, will continue to function, by redirecting requests to the new endpoint.

 

 

 

  • Was this article helpful?