addedValues Plugin

...Powerful Free! Database Expansion for Manila

(1 or more words)

Get tropes here!
Click to see internals
Report bug


Viewable with Any Browser

Join Now

WYSIWYG HTML editing in AddedValues

Addedvalues makes use of an advanced open source javascript editor called HTMLArea which is an improvment over the HTML editor shipped with Manila. Most notably it works on browsers other than Microsoft Internet Explorer running under Windows; additionally its menu bar can be configured, new features can added as new buttons in the menu bar and it is said to be faster. You need a recent browser to run it on, the Gecko engine in Mozilla browsers after 1.3.1 is fine as are recent versions of Internet Explorer.

However HTMLarea is still under development by its creators, Interactive Tools, and it's currently difficult to obtain a copy of the latest version unless you are used to working with the CVS system at I checked out a version on June 25th and will make that version available for download here. I will not actively update this version unless there is a good reason to do so. The original alpha version released by Interactive Tools is also available for your convenience.

Before WYSIWYG editing can be enabled , addedValues must know the location of the folder and a functional url for HTMLArea directory of files. The server administrator must copy the htmlarea folder into folder configured as "Folder for Static Rendering" in the admin site; Settings menu, Static files page. Click on the 2 pictures below to view these settings

HTMLArea Admin site settings: HTMLArea Static Files settings:

If your folder name and the url correspond correctly, browsing to the url

<http://... url for static rendering ... /htmlarea/example.html>

should return a page like this

Now go to the addedValues preference page in your site, in the forms section you see 2 lines that relate to WYSIWYG editing

WYSIWYG Preferences settings:

The menu will cater for future different possible htmlEditors or versions, at the moment there are no other choices. The radio buttons determine whether the checkbox for each form element is checked by default in the form rendering page, click this thumbnail for an example

WYSIWYG rendering Checkbox:

If you want to use this flavour of WYSIWYG, you MUST turn off the Manila wysiwyg in the Prefs for Editors - setting it to none.

WYSIWYG Manila None:

b298 - a new preference, "Manila ETP defaults to.." , visible only when a WYSIG editor is selected on the preferences page, causes addedValues to default a manila ETP form using the selected editor for creating and editing messages and stories. No other configuration is required, the configure messages value should be Standard Manila. Three predefined forms , whose names begin with default_ and are consequently usually invisible, are used for this purpose. They are open to modification, for layout purposes, if the default layout isn't adequate, though they should not be otherwise extended.

b298 - if the debug option is set, forms whose names start with default_ become visible and available to for editing. Normally they are invisible.

b298 - support has been added for version 2.2 of the FCKeditor (see However its use in Mania is limited because it will always convert a " character to " and there sees to be no way to disable that behaviour.

b298 - support has been added for version 2..0.5 of the tinyMCE HTML editor (see However its use in Mania is limited because it will always convert a " character to ". It is possible to alter this behavior using a tinyMCE save callback.

b300 - the tinyMCE wysiwyg spell checker plugin uses AJAX techniques to connect to a PHP CGI. When the site is being served by Frontier, only Frontier sees any http POSTs to the domain, so the spell checker was rendered incommunicado. Now addedValues will act as a proxy server to an external PHP server , if that servers url is specified by a shortcut named tinyMCESpellCheckerPHP in the website. The tinyMCE configuration of the plugin must be done from the addedValues preferences page