Plain Text Editor in LibGuides

Many of you have come to rely on the LibGuides Rich Text Editor for entering content into your guides. The rich text editor is neat because it provides an easy way for non-techie people to create beautiful html text that looks really nice on your guides.

However, some of our power users have experienced a few issues with the rich text editor in that they find the editor sometimes changes some of their manually entered html tags and javascript code. Namely, the text editor “cleans up” the code, i.e. it makes sure that the code and tags entered are standards-compliant html. For all practical purposes this is a good thing because your html code should be standards compliant and have proper attributes, as defined by the W3C consortium.  But, sometimes, in order to make scripts work right (especially for javascript and forms) you don’t want LibGuides rich text editor correcting your code. Plain Text Editor to the rescue!

When you want to enter the html code/forms/javascript yourself and don’t need the rich text editor, click on the “switch to plain text editor” link which is now part of the rich text editor popup. See the screenshot below.

Plain Text Editor

One comment

  1. admin says:

    Hi, there may be something wrong with the widget, if it can’t even be posted on this wordpress blog. Could you please send us the code via email to support {at} springshare dot com and we’ll take a look at the code. Thanks.

Leave a Reply

Your email address will not be published. Required fields are marked *

Confirm you aren't spamming: * Time limit is exhausted. Please reload the CAPTCHA.

%d bloggers like this: