nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

XSD schemas and UI Control

tonizz

When you want to create a general web content from "Create Web Content" afresco provides you an UI that offers you a rich text editor whith a lot of options: text format, alignment, colors, images, links, tables, styles….

Otherwise if you begin the process of creating a content from a web form, here I have my schema:

<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<!– defines the form for creating a news –>
<xs:element name="content">
    <xs:complexType>
      <xs:sequence>
      <xs:element name="title" type="xs:normalizedString"/>
        <xs:element name="body" type="xs:anyType"/>
      </xs:sequence>
    </xs:complexType>
</xs:element>
</xs:schema>

The documentation explains that the type xs:anyType leads you to a rich text editor, but the editor I get is the minimun one.

Do you know what is the correct type or if the matter is that what I want to do is not possible???

Thanks in advance.

Find more posts tagged with

Comments

mark_smithson

Hi

Try using xs:string rather than xs:anyType

Mark

tonizz

Yes, you are right but in this way you only can use the WCM editor, I would like to use TinyMCE Editor, this is much more complete.

Thanks for your reply.

arielb

they are all tinymce editors other than minimal appearance for xs:string which produces a plaintexteditor. the preferred type to use is xs:string as opposed to xs:anyType. as of 2.1 there is a full appearance defined for this type which will result in more buttons.

<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:alf="http://www.alfresco.org">
<!– defines the form for creating a news –>
<xs:element name="content">
<xs:complexType>
<xs:sequence>
<xs:element name="title" type="xs:normalizedString"/>
<xs:element name="body" type="xs:string">
  <xs:appinfo><xs:annotation><alf:appearance>full</alf:appearance></xs:annotation></xs:appinfo>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

sirclueless

I get the following error if I try to use the webform above :

org.alfresco.web.forms.FormProcessor$ProcessingException: org.alfresco.web.forms.xforms.FormBuilderException: error parsing schema: at line 9 column 18: s4s-elt-must-match.1: The content of 'content' must match (annotation?, (simpleType | complexType)?, (unique | key | keyref)*)). A problem was found starting at: appinfo.

What do I wrong or what is my mistake ??

mark_smithson

sounds like a spelling error on the xs:annotation element - did you copy/paste or type it?

sirclueless

I copy-paste it. Here is my complete webform:

<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:alf="http://www.alfresco.org" elementFormDefault="qualified" attributeFormDefault="unqualified">
   <!– defines the form for creating a company home –>
   <xs:element name="infeurope">
      <xs:complexType>
         <xs:sequence>
            <xs:element name="header" type="xs:normalizedString"/>
            <xs:element name="content" type="xs:string">
               <xs:appinfo><xs:annotation><alf:appearance>full</alf:appearance></xs:annotation></xs:appinfo> 
            </xs:element> 
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I thought that is correct ,or?

tonizz

could be that the xs:string line is not close by "/>"???

sirclueless

I think that`s correct, cause that is in the element-tag and this tag will close later. It`s in the example above the same.

mark_smithson

Ah - should be this

<xs:annotation><xs:appinfo><alf:appearance>full</alf:appearance></xs:appinfo></xs:annotation>

sirclueless

Yes thank you ! That was the mistake. Now it works !!!

tonizz

This option is good. But it would be much better if we could use TinyMCE as editor. Is it possible?

Why if you try to create content without webform you can use TinyMCE and if you start the edition from a webform you have to use this limited editor?

Thanks.

kvc

In 2.1.0, we now support different appearance for the xf:textarea control that we generated from an xs:string defined in your XSD.

By default, xs:string uses the general xf:textarea UI control which implements a limited set of controls in a TinyMCE instance. You can specify a MINIMAL appearance, which will produce a Plain Text Editor (no TinyMCE), a FULL appearance or define any custom appearance type you want (including defining whatever TinyMCE plug-ins you want to enable as well).

You can see the different options you have or the different options you can create in web-client-config-wcm.xml:

           <widget xforms-type="xf:textarea"
                   appearance="minimal"
                   javascript-class-name="alfresco.xforms.PlainTextEditor"/>
           <widget xforms-type="xf:textarea"
                   javascript-class-name="alfresco.xforms.RichTextEditor">
             <param name="theme_advanced_buttons1">bold,italic,underline,separator,forecolor,backcolor,separator,link,unlink,image</param>
           </widget>
           <widget xforms-type="xf:textarea"
                   appearance="full"
                   javascript-class-name="alfresco.xforms.RichTextEditor">
             <param name="theme_advanced_buttons1">bold,italic,underline,strikethrough,separator,fontselect,fontsizeselect</param>
             <param name="theme_advanced_buttons2">link,unlink,image,separator,justifyleft,justifycenter,justifyright,justifyfull,separator,bullist,numlist,separator,undo,redo,separator,forecolor,backcolor</param>
             <param name="height">400</param>
           </widget>
           <!–
               NOTE: only the table tinymce plugin is part of the default alfresco distribution.  
               to enable other tinymce plugins, the plugin code must first be copied into the
               tinymce distribution within the webapp.
             –>
           <widget xforms-type="xf:textarea"
                   appearance="custom"
                   javascript-class-name="alfresco.xforms.RichTextEditor">
             <param name="theme_advanced_buttons1">bold,italic,underline,strikethrough,separator,fontselect,fontsizeselect</param>
             <param name="theme_advanced_buttons2">link,unlink,image,separator,justifyleft,justifycenter,justifyright,justifyfull,separator,bullist,numlist,separator,undo,redo,separator,forecolor,backcolor</param>
             <param name="height">600</param>
             <param name="mode">exact</param>
             <param name="force_p_newlines">true</param>
             <param name="apply_source_formatting">true</param>
             <param name="plugins">table</param>
             <param name="theme_advanced_buttons3">tablecontrols</param>
           </widget>
           <!–
           <widget xforms-type="xf:textarea"
                   appearance="fullscreen"
                   javascript-class-name="alfresco.xforms.RichTextEditor">
             <param name="theme_advanced_buttons1">bold,italic,underline,strikethrough,separator,fontselect,fontsizeselect</param>
             <param name="theme_advanced_buttons2">link,unlink,image,separator,justifyleft,justifycenter,justifyright,justifyfull,separator,bullist,numlist,separator,undo,redo,separator,forecolor,backcolor</param>
             <param name="height">600</param>
             <param name="plugins">fullscreen</param>
             <param name="theme_advanced_buttons3">fullscreen</param>
           </widget>
           –>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Also, for more info on how various XSD types are mapped to XForms controls, you can take a look at the following wiki page:

http://wiki.alfresco.com/wiki/Forms_Developer_Guide#Supported_XML_Schema_structures_and_data_types

Kevin