<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Customizing Alfresco Share: Five things to watch out for</title>
	<atom:link href="http://ecmarchitect.com/archives/2009/04/22/976/feed" rel="self" type="application/rss+xml" />
	<link>http://ecmarchitect.com/archives/2009/04/22/976</link>
	<description>Jeff Potts on ECM, portals, search, collaboration, and a bunch of personal stuff</description>
	<lastBuildDate>Mon, 06 Feb 2012 17:48:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: jpotts</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-48046</link>
		<dc:creator>jpotts</dc:creator>
		<pubDate>Mon, 22 Feb 2010 21:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-48046</guid>
		<description>I&#039;m pretty sure this would require a customization because out-of-the-box, sites are in a flat hierarchy. Every Share site has a corresponding folder in a root folder called &quot;Sites&quot; in the DM repository. My guess is that the easiest route to implement something like this would be to leave the physical storage of the site folders as-is, and then use associations to keep track of the parent child relationships between sites. You&#039;d then only need to enhance the Share UI to let the Site hierarchy be traversed.

You might want to Google around the wiki and the forums to see if this has ever been mentioned as a roadmap item. Seems like it would be a common feature request.

Jeff</description>
		<content:encoded><![CDATA[<p>I&#8217;m pretty sure this would require a customization because out-of-the-box, sites are in a flat hierarchy. Every Share site has a corresponding folder in a root folder called &#8220;Sites&#8221; in the DM repository. My guess is that the easiest route to implement something like this would be to leave the physical storage of the site folders as-is, and then use associations to keep track of the parent child relationships between sites. You&#8217;d then only need to enhance the Share UI to let the Site hierarchy be traversed.</p>
<p>You might want to Google around the wiki and the forums to see if this has ever been mentioned as a roadmap item. Seems like it would be a common feature request.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Varun</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-48042</link>
		<dc:creator>Varun</dc:creator>
		<pubDate>Mon, 22 Feb 2010 18:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-48042</guid>
		<description>Hi Jeff,

I am new to Alfresco Share 3.2. My client requirement is like parent-child site concept.

Example: 

Parent site :A
Child sites : B,C,D
Each child sites contains sub sites like,
B contians B1,B2 sites,C contains C1,C2 etc.

Is it possible to create sub sites under site ?

Can you please explain? 

Thanks in advance

Varun</description>
		<content:encoded><![CDATA[<p>Hi Jeff,</p>
<p>I am new to Alfresco Share 3.2. My client requirement is like parent-child site concept.</p>
<p>Example: </p>
<p>Parent site :A<br />
Child sites : B,C,D<br />
Each child sites contains sub sites like,<br />
B contians B1,B2 sites,C contains C1,C2 etc.</p>
<p>Is it possible to create sub sites under site ?</p>
<p>Can you please explain? </p>
<p>Thanks in advance</p>
<p>Varun</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jpotts</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-42475</link>
		<dc:creator>jpotts</dc:creator>
		<pubDate>Mon, 12 Oct 2009 00:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-42475</guid>
		<description>George,

Yep. I&#039;m not sure why they don&#039;t check that more strictly. It also works with aspects--you can set a property that belongs to an aspect even if the aspect has not been applied. And in both cases, those properties are indexed and searchable by Lucene which I think is even more bizarre. Of course if you do a search based on the type, an ancestor type, or the aspect, you won&#039;t get a hit, but I still agree with you: Alfresco should throw an exception if you&#039;re trying to set a property that&#039;s not defined as the document&#039;s type or in any of its aspects.

Jeff</description>
		<content:encoded><![CDATA[<p>George,</p>
<p>Yep. I&#8217;m not sure why they don&#8217;t check that more strictly. It also works with aspects&#8211;you can set a property that belongs to an aspect even if the aspect has not been applied. And in both cases, those properties are indexed and searchable by Lucene which I think is even more bizarre. Of course if you do a search based on the type, an ancestor type, or the aspect, you won&#8217;t get a hit, but I still agree with you: Alfresco should throw an exception if you&#8217;re trying to set a property that&#8217;s not defined as the document&#8217;s type or in any of its aspects.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-42378</link>
		<dc:creator>George</dc:creator>
		<pubDate>Fri, 09 Oct 2009 00:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-42378</guid>
		<description>Hi Jeff

I think I found an answer to my previous posting in the comments on this blog http://ecmarchitect.com/archives/2007/06/09/756 - in particular your reply to Tony&#039;s posting. 

I am slightly confused however by the inheritance provided by the content model. After reading your reply i wrote a simple script to set the campaign (seeing as it isn&#039;t exposed to the web client) as follows -
 
document.properties[&quot;sc:campaign&quot;] = &quot;Social Shopping&quot;;
document.save();

I executed the script against a Whitepaper content type. I then previewed the item using the doc_info template and the above property was correctly reflected. However I then executed the same script against a Someco Legal Document type expecting some sort of exception, yet the preview revealed that the document quite happily accepted that property. 

This seems to break the inheritance model provided by the content model. Is there nothing to enforce this other than developer discipline?

Thanks
George</description>
		<content:encoded><![CDATA[<p>Hi Jeff</p>
<p>I think I found an answer to my previous posting in the comments on this blog <a href="http://ecmarchitect.com/archives/2007/06/09/756" rel="nofollow">http://ecmarchitect.com/archives/2007/06/09/756</a> &#8211; in particular your reply to Tony&#8217;s posting. </p>
<p>I am slightly confused however by the inheritance provided by the content model. After reading your reply i wrote a simple script to set the campaign (seeing as it isn&#8217;t exposed to the web client) as follows -</p>
<p>document.properties["sc:campaign"] = &#8220;Social Shopping&#8221;;<br />
document.save();</p>
<p>I executed the script against a Whitepaper content type. I then previewed the item using the doc_info template and the above property was correctly reflected. However I then executed the same script against a Someco Legal Document type expecting some sort of exception, yet the preview revealed that the document quite happily accepted that property. </p>
<p>This seems to break the inheritance model provided by the content model. Is there nothing to enforce this other than developer discipline?</p>
<p>Thanks<br />
George</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-42377</link>
		<dc:creator>George</dc:creator>
		<pubDate>Thu, 08 Oct 2009 23:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-42377</guid>
		<description>Hi Jeff

This may not be related to the above discussion but does have to do with customising Alfresco&#039;s content model. 

I was wondering whether you may provide further insight into Chapter 3 of your book Alfresco Developer Guide?

Under the section Properties and Property Types in Chapter 3 you mention that the content type Whitepaper will inherit the campaign property from it&#039;s parent type MarketingDoc. I have downloaded the sample code and extended a fresh install of Alfresco 3.2 with your custom content model. Yet when i add new content of the type Whitepaper, the only property inherited is the association. 

Admittedly i have not tried this in any earlier version. Do you know if Alfresco 3.2 is backwards compatible with the example you have provided?

Thanks in advance 
George</description>
		<content:encoded><![CDATA[<p>Hi Jeff</p>
<p>This may not be related to the above discussion but does have to do with customising Alfresco&#8217;s content model. </p>
<p>I was wondering whether you may provide further insight into Chapter 3 of your book Alfresco Developer Guide?</p>
<p>Under the section Properties and Property Types in Chapter 3 you mention that the content type Whitepaper will inherit the campaign property from it&#8217;s parent type MarketingDoc. I have downloaded the sample code and extended a fresh install of Alfresco 3.2 with your custom content model. Yet when i add new content of the type Whitepaper, the only property inherited is the association. </p>
<p>Admittedly i have not tried this in any earlier version. Do you know if Alfresco 3.2 is backwards compatible with the example you have provided?</p>
<p>Thanks in advance<br />
George</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pratap Maddi</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-41140</link>
		<dc:creator>Pratap Maddi</dc:creator>
		<pubDate>Thu, 10 Sep 2009 14:36:15 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-41140</guid>
		<description>Hi Jeff,

Thanks a lot for providing valuable information on share. This is really useful stuff.

We tried working with blogs and discussions in share. We faced following problem. May be you could give us proper pointers on what we could have missed out.

Following is what we have done.

We created a site by using the admin privileges. Also created couple of users through alfresco web client. We are able to log on to the alfresco share application with those user ids as well. Then we invited couple of users to the site created by admin (with admin login). With admin user id, we also created a blog and a thread.
Then we logged in with these invited user ids and tried to add comments to blog and threads. But, when we click on read of a blog we don&#039;t see the comments text area. In fact there is nothing for the user to add a comment. We tried giving different prvileges (like contributor, collaborator etc) to the invited users, but we are not able to add comments to a blog or create a blog. Same thing with discussions.

Also the create blog and create topic(discussion) links are disabled for these users.

We tried to create the site with these user ids. The user who created the site is having these privileges. But the users that are invited to the site are not able to do the same. 

Are we missing anything? It seems that we have missed some basic configuration as these are basic things. 

Regards,
Pratap</description>
		<content:encoded><![CDATA[<p>Hi Jeff,</p>
<p>Thanks a lot for providing valuable information on share. This is really useful stuff.</p>
<p>We tried working with blogs and discussions in share. We faced following problem. May be you could give us proper pointers on what we could have missed out.</p>
<p>Following is what we have done.</p>
<p>We created a site by using the admin privileges. Also created couple of users through alfresco web client. We are able to log on to the alfresco share application with those user ids as well. Then we invited couple of users to the site created by admin (with admin login). With admin user id, we also created a blog and a thread.<br />
Then we logged in with these invited user ids and tried to add comments to blog and threads. But, when we click on read of a blog we don&#8217;t see the comments text area. In fact there is nothing for the user to add a comment. We tried giving different prvileges (like contributor, collaborator etc) to the invited users, but we are not able to add comments to a blog or create a blog. Same thing with discussions.</p>
<p>Also the create blog and create topic(discussion) links are disabled for these users.</p>
<p>We tried to create the site with these user ids. The user who created the site is having these privileges. But the users that are invited to the site are not able to do the same. </p>
<p>Are we missing anything? It seems that we have missed some basic configuration as these are basic things. </p>
<p>Regards,<br />
Pratap</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Customizing Alfresco Share: Five things to watch out for &#171; Alfresco &#38; Share Blog</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-35133</link>
		<dc:creator>Customizing Alfresco Share: Five things to watch out for &#171; Alfresco &#38; Share Blog</dc:creator>
		<pubDate>Tue, 12 May 2009 20:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-35133</guid>
		<description>[...] to watch out&#160;for  This article is of interest for those who will start customizing Share : see. Please note that it is related to version [...]</description>
		<content:encoded><![CDATA[<p>[...] to watch out&nbsp;for  This article is of interest for those who will start customizing Share : see. Please note that it is related to version [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jpotts</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-35066</link>
		<dc:creator>jpotts</dc:creator>
		<pubDate>Mon, 11 May 2009 15:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-35066</guid>
		<description>Certainly. You would have to decide how you wanted to make those task assignments. Right now the OOTB Review &amp; Approve workflow lets the workflow initiator make one user/group selection on workflow start. If you are going to split the workflow into additional steps, you will either have to modify the model and web client config to allow the initiator to specify a user/group for both the &quot;review&quot; and &quot;approve&quot; steps, or you could let the performer of the review step pick the approver, or you could just hardcode either (or both) into the process definition.

Jeff</description>
		<content:encoded><![CDATA[<p>Certainly. You would have to decide how you wanted to make those task assignments. Right now the OOTB Review &#038; Approve workflow lets the workflow initiator make one user/group selection on workflow start. If you are going to split the workflow into additional steps, you will either have to modify the model and web client config to allow the initiator to specify a user/group for both the &#8220;review&#8221; and &#8220;approve&#8221; steps, or you could let the performer of the review step pick the approver, or you could just hardcode either (or both) into the process definition.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JM Delsaux</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-35064</link>
		<dc:creator>JM Delsaux</dc:creator>
		<pubDate>Mon, 11 May 2009 14:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-35064</guid>
		<description>Hello Jeff.  Nice as usual ;-)
Do you think that it is possible/easy to customize &quot;Review &amp; Approve&quot; workflow to have one person to perform the &quot;Review&quot; and another one to perform the &quot;Approve&quot; ?

Thanks
JMi</description>
		<content:encoded><![CDATA[<p>Hello Jeff.  Nice as usual <img src='http://ecmarchitect.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /><br />
Do you think that it is possible/easy to customize &#8220;Review &amp; Approve&#8221; workflow to have one person to perform the &#8220;Review&#8221; and another one to perform the &#8220;Approve&#8221; ?</p>
<p>Thanks<br />
JMi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Wentworth</title>
		<link>http://ecmarchitect.com/archives/2009/04/22/976/comment-page-1#comment-34342</link>
		<dc:creator>Ed Wentworth</dc:creator>
		<pubDate>Tue, 28 Apr 2009 15:42:56 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=976#comment-34342</guid>
		<description>Thanks Jeff. Once again, you are right on point. We&#039;ve been prototyping a tool by customizing Share, mainly to leverage its collaboration features. Having struggled with modifying document library, for instance, our current approach is to add new components. However, we want to leverage workflows and integrate things like discussions with our own content model. So thanks for the heads up on these challenges. Climbing the YUI, bubbling and other learning curve has been challenging. However, I agree with Mike, the separation of files is sprawling, but appropriate for extensibility. Tools would help. I hope we all continue to Share our learning experiences.</description>
		<content:encoded><![CDATA[<p>Thanks Jeff. Once again, you are right on point. We&#8217;ve been prototyping a tool by customizing Share, mainly to leverage its collaboration features. Having struggled with modifying document library, for instance, our current approach is to add new components. However, we want to leverage workflows and integrate things like discussions with our own content model. So thanks for the heads up on these challenges. Climbing the YUI, bubbling and other learning curve has been challenging. However, I agree with Mike, the separation of files is sprawling, but appropriate for extensibility. Tools would help. I hope we all continue to Share our learning experiences.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

