JMP User Community Weekly Review - 12DEC2019

Question

Agenda:

* LIngotek connector update scheduled for noon on 13DEC2019. Update is to accommodate versioning.
* Schedule updates to Community on 16DEC2019:* COM-218 - Update to Media 5.2
* COM-315 - Private Groups/Private Support List changes
* COM-311 - Revert to default attachment component
* COM-323 - Utility bar not displayed for groups
* COM-305, COM-306 - Code cleanup
* COM-278 - Incorrect blog labels
* COM-215 - Category subscriptions for Blogs, File Exchange, Discovery Summit, Employee Spaces
* COM-223 (?) - Editor v2 (Two issues reported to Khoros)

* Updates coming to JMP Live Community reports
* Thoughts on metrics for Community Champion
* Discuss Khoros Business Review
* Community newsletter update - metrics, December release
* Early 2020 Goals* Gamification
* Reports
* UI cleanup

Ryan_Gilmore · Answer

The Source Code editor can be invoked by displaying the Developer Tools for the browser and entering the following command in the Console,

for the Body of a message, use

tinyMCE.editors["tinyMceEditor"].execCommand('mceCodeEditor')

for the Teaser of a message, use
tinyMCE.editors["lia-teaserTinyMceEditor"].execCommand('mceCodeEditor')

Ryan_Gilmore · Answer

When inserting JSL code into a blog post, the HTML will need to be modified. The tags will need to be replaced with

 and  tags as shown below:

 

Community_Data:Write Log = Function( {msg},
Logging:Write Log( msg, Community_Data )
);

Community_Data:Initialize();

Ryan_Gilmore · Answer

Translation does work with the code formatting with the new v2 Editor. Here are two screen shots:

The above image shows the use of the JSL code formatter.

The above image shows the default code formatter with C# selected as the language.

The text was written in English for both.