Space specialization problem

[ero]

Hi,


I'm using last 1.3 SVN dev version.

I'm able to create some custom space (e.g. type "A" declared as child of the root cm:folder type) using "Space Wizard". Custom model as wel as web-config-client-custom.xml are OK.
Fine.
Problem is that I'm unable to achieve same result without using "Space Wizard"; i.e. create first standard cm:folder space and then specialize it, applying custom space type "A" (using Run action wizard).
All XML tags like <type name=…> and related to spaces I defined in the <specialise-types> section of the <config evaluator="string-compare" condition="Action Wizards"> section of my web-config-client-custom.xml are systematically ignored (whereas the one related to contents are taken in account and displayed in the dropdown list in the web client UI).

Conclusion:
Results are different according to the way I choose to create a custom space.

Bug ? Missing something ?

Thank's.

[gavinc]

I'm afraid I don't completely understand your question.

I understand you are specialising a 'normal' folder to one of your custom space types and it's not behaving as you would expect.

Which drop down list in the UI are you expecting to see your custom space type in?

[ero]

Hi Gavin,

I defined some custom folder types in custom model.
I'm able to create customs spaces using "Space Wizard".
Conclusion: model as well as web-config-client-custom.xml ("Space Wizards" section) are correct. Fine.

Now, I want to do the same but from a cm:foler (using Run Action).

1. Create standard cm:folder
2. Run action >
    Select an action >
    Specialise the type of an item >
    Set value and Add > …..
    Drop down list in web UI list only document types defined in "Action   Wizard"   <specialise-types> section of my XML file.
Folder types defined in that <specialise-types> section are simply ignored.

Conclusion:
I think it's actually impossible to specialise some folder.
Missing something ?

Regards

[gavinc]

Ahh, OK, I understand now ops:

Yes, this is also a known issue, there are actually a couple of bugs raised about this:

http://www.alfresco.org/jira/browse/AWC-663
http://www.alfresco.org/jira/browse/AR-602

I should be looking at these today.

[gavinc]

The two issues above have been resolved and checked into SVN.

You can now have any sub type of content or folder in the list, but not the content or folder types themselves.