XStandard Pro is required because the editor must use certain API calls that are only available on the Pro version. For example, the InsertXml api call (see http://xstandard.com/en/documentation/xstandard-dev-guide/api/) is necessary to handle image insertion and link insertion from OpenCms.

Best,

Paul

until recently I liked the FCKEditor which comes bundled with OpenCms. But it emerges more and more that the produced code is not XHTML compliant which is really a pity.
So I found your “OpenCms 7 XStandard WYSIWYG Module” quite interesting. It was the first time I heard of XStandard and the feature list on their homepage is quite impressive and promising.
You mentioned under “requirements” for your module the XStandard Pro version is needed and not the lite version. I would not mind spending the money for two or three licenses but I have a problem with the amount of 10 licenses to be bought as a minimum. Why wasn’t it possible to integrate the XStandard Lite version? The lite version would sufficient for my needs.

Regards,
Manfred

would like to say many thanks to you for your great work, you are awesome
I’ve posted a link on OpenCms Goodies Forum about it:

http://www.pomegranate.de:9000/cms/forum/viewthread?thread=139

Best,
Arash