[Solved]Custom Spacetype with 'default' icon only

[norgan]

Hi there,
i have some foldertypes defined and included into the Spacewizard .With one type (chk:subfolder), the selection is fine, creation works, but the icon, which was set in web-client-custom-config.xml is ignored. The user does only have the "default" naked icon. Bug or misconfiguration ?

On doing some tests, I observed following behaviour :
a) Create Space -> selected Icon is taken; Assign Aspect A -> Icon is reset to "default naked", but the picklist contains all possible icons.
b) Create Advanced Space Wizard -> In dialog, Icon is still correct. On "details screen" one step further, the icon is reset to "default naked" with picklist of length 1 (default naked)

Any ideas ?

My  wizard definition :

<config evaluator="string-compare" condition="Space Wizards">
      <folder-types>
         <type name="chk:subfolder" icon="/images/icons/space-icon-bc.gif"    description-id="subfolder-desc-ID" display-label-id="subfolder-ID" />
         <type name="chk:basefolder" icon="/images/icons/space-icon-doclib.gif"  description-id="basefolder-desc-ID" display-label-id="basefolder-ID" />
      </folder-types>
   </config>

my type definiton:
      

<type name="chk:basefolder">
         <title>basefolder</title>
         <description>general basefolder</description>
         <parent>cm:folder</parent>
         <properties ></properties>
         <associations>
            <association name="chk:relatedFolder">
               <title>related basefolder</title>
               <source>
                  <mandatory>false</mandatory>
                  <many>true</many>
               </source>
               <target>
                  <class>chk:basefolder</class>
                  <mandatory>false</mandatory>
                  <many>true</many>
               </target>
            </association>
         </associations>
         <mandatory-aspects>
            <aspect>cm:generalclassifiable</aspect>
         </mandatory-aspects>
      </type>
<type name="chk:mainfolder">
         <title>mainfolder</title>
         <description>Container fuer Metadaten, Unterlagen und
Workflowinformationen zu einem Vorgang. </description>
         <parent>chk:basefolder</parent>
         <properties>
            <!– Properties –>
         </properties>
         <associations>
            <!– associations –>
         </associations>
      </type>
<type name="chk:subfolder">
         <title>Chk Ordner</title>
         <description>Container für Chk</description>
         <parent>chk:mainfolder</parent>
         <properties>
            <!– Properties –>
         </properties>
         <associations>
            <!– associations –>
         </associations>
         <mandatory-aspects>
            <aspect>chk:metadataAspect</aspect>
         </mandatory-aspects>
      </type>

the metadataAspect assignes properties only. Presentation int he detail screen consists of properties and separators.

[norgan]

Hi again,
I found out (wish I had read about it somewhere), that you have to define the web-client-config-custom.xml entries for each content-type separately.

So the way to supply cm:folder with new icons is well known.

   <config evaluator="string-compare" condition="cm:folder icons">
      <icons>
         <icon name="space-icon-emailarchive" path="/images/icons/space-icon-emailarchive.gif" />
         <icon name="space-icon-doclib" path="/images/icons/space-icon-doclib.gif" />
      </icons>
   </config>
 ‍‍‍‍‍‍‍‍

I only have to do the same for the subcontent type as well. This way, I can even define an individual set of icons for each foldertype.

<config evaluator="string-compare" condition="chk:subfolder icons">
      <icons>
         <icon name="space-icon-emailarchive" path="/images/icons/space-icon-emailarchive.gif" />
         <icon name="space-icon-doclib" path="/images/icons/space-icon-doclib.gif" />
         <icon name="space-icon-survey" path="/images/icons/space-icon-survey.gif" />
      </icons>
   </config>