03-02-2010 05:13 AM
03-02-2010 06:20 AM
Is this enchancement is only available for Entreprise version ?
If yes : Will this improvement be available in Community version and When (next release, road map) ?
If no : Where this file is located ? How to install correctly this ability ?
03-16-2010 07:21 AM
03-16-2010 08:14 AM
03-19-2010 04:10 AM
<alfresco-config>
<!– Global config section –>
<config replace="true">
<flags>
<!–
Developer debugging setting to turn on DEBUG mode for client scripts in the browser
–>
<client-debug>true</client-debug>
<!–
LOGGING can always be toggled at runtime when in DEBUG mode (Ctrl, Ctrl, Shift, Shift).
This flag automatically activates logging on page load.
–>
<client-debug-autologging>false</client-debug-autologging>
</flags>
</config>
<!– Document Library config section –>
<config evaluator="string-compare" condition="DocumentLibrary" replace="true">
<!–
Whether the folder Tree component should enumerate child folders or not.
This is a relatively expensive operation, so should be set to "false" for Repositories with broad folder structures.
–>
<tree>
<evaluate-child-folders>false</evaluate-child-folders>
</tree>
<!–
Used by the "Manage Aspects" action
For custom aspects, remember to also add the relevant i18n string(s)
cm_myaspect=My Aspect
–>
<aspects>
<!– Aspects that a user can see –>
<visible>
<aspect name="cm:generalclassifiable" />
<aspect name="cm:complianceable" />
<aspect name="cm:dublincore" />
<aspect name="cm:effectivity" />
<aspect name="cm:summarizable" />
<aspect name="cm:versionable" />
<aspect name="cm:templatable" />
<aspect name="cm:emailed" />
<aspect name="emailserver:aliasable" />
<aspect name="cm:taggable" />
<aspect name="app:inlineeditable" />
</visible>
<!– Aspects that a user can add. Same as "visible" if left empty –>
<addable>
</addable>
<!– Aspects that a user can remove. Same as "visible" if left empty –>
<removeable>
</removeable>
</aspects>
<!–
Used by the "Change Type" action
Define valid subtypes using the following example:
<type name="cm:content">
<subtype name="cm:mysubtype" />
</type>
Remember to also add the relevant i18n string(s):
cm_mysubtype=My SubType
–>
<types>
<type name="cm:content">
<subtype name="mz:pcb" />
<subtype name="mz:specialoffer" />
</type>
<!– <type name="cm:folder">
<subtype name="cm:myfoldersubtype" />
</type>–>
</types>
<!–
If set, will present a WebDAV link for the current item on the Document and Folder details pages.
Also used to generate the "View in Alfresco Explorer" action for folders.
–>
<repository-url>http://myIP:8080/alfresco</repository-url>
</config>
<!– Repository Library config section –>
<config evaluator="string-compare" condition="RepositoryLibrary" replace="true">
<!–
Whether the link to the Repository Library appears in the header component or not.
–>
<visible>true</visible>
<!–
Root nodeRef for top-level folder.
–>
<root-node>alfresco://company/home</root-node>
<!–
Whether the folder Tree component should enumerate child folders or not.
This is a relatively expensive operation, so should be set to "false" for Repositories with broad folder structures.
–>
<tree>
<evaluate-child-folders>false</evaluate-child-folders>
</tree>
</config>
</alfresco-config>
07:59:43,122 INFO [org.alfresco.config.JBossEnabledWebApplicationContext] Refreshing org.alfresco.config.JBossEnabledWebApplicationContext@6209fb: display name [Root WebApplicationContext]; startup date [Fri Mar 19 07:59:43 UTC 2010]; root of context hierarchy
07:59:44,109 INFO [org.alfresco.config.JBossEnabledWebApplicationContext] Bean factory for application context [org.alfresco.config.JBossEnabledWebApplicationContext@6209fb]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1c9f71d
07:59:47,801 ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'webframework.manager' defined in class path resource [alfresco/web-framework-application-context.xml]: Invocation of init method failed; nested exception is org.alfresco.config.ConfigException: 02190000 Unable to locate evaluator implementation for 'node-type' for org.alfresco.config.ConfigSectionImpl@1c13a68 (evaluator=node-type condition=cm:content replace=false)
Caused by: org.alfresco.config.ConfigException: 02190000 Unable to locate evaluator implementation for 'node-type' for org.alfresco.config.ConfigSectionImpl@1c13a68 (evaluator=node-type condition=cm:content replace=false)
at org.alfresco.config.BaseConfigService.processSection(BaseConfigService.java:459)
at org.alfresco.config.BaseConfigService.getConfig(BaseConfigService.java:225)
at org.alfresco.config.BaseConfigService.getConfig(BaseConfigService.java:167)
at org.alfresco.web.framework.WebFrameworkManager.init(WebFrameworkManager.java:131)
03-19-2010 06:22 AM
03-19-2010 06:37 AM
Doh!Not very feasible I'm afraid, sorry - it'll be in v3.3 released soon.
Sorry Mike, hadn't noticed the 'Enterprise' qualifier! Is there a way to backport this functionality to 3.2r2?
Cheers,
Eddie
03-19-2010 08:35 AM
03-19-2010 10:48 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.