On 7 Oct 2008, at 11:01, sean.radford.tacola.com wrote:
> I require to get some rudimentary WCM running (under 5.1 - I could be
> persuaded to use 5.2, but cannot get the TIP to deploy, see my other
> posts). I haven't come across any functionality to provide WCM  
> directly
> (have I missed something?) and so was thinking how could I get  
> something
> simple working in the short-term.
>
> I was thinking, could I use a Note Document Type to create the main  
> content
> for a page, and then publish that to a section. A section could then  
> have a
> Theme with a Wiew/Widget to display the Note of the Note only
> (un-escaped).[This theme would probably have the usual header bar  
> with logo
> and User Services with the Note Widget below, but different Theme  
> Pages
> would require additional Views]
>
> This would almost work. The issue would be:
>
> You can only define a Theme on a Folder (not a document) in a Section,
> which would cause problems for rendering the Folder itself, and  
> would mean
> all published Note documents within a Folder would use the same  
> Theme (you
> may want different Pages from a Theme for different Note documents).
>
> In my mind, a 'nice' solution would be to define the Theme/Page for  
> a Note
> (more explicitly a new DocumentType extending Note) that would be  
> used for
> rendering once published. Is this possible? How would I go about doing
> that?

The theme tab is just another tab which by default we only display on  
SuperSpaces:

     <action id="TAB_THEME" link="/incl/tabs/document_theme.xhtml"  
enabled="true"
       order="60" label="action.view.theme" icon="/icons/file.gif">
       <category>VIEW_ACTION_LIST</category>
       <filter-id>canChangeTheme</filter-id>
     </action>
...
     <filter id="canChangeTheme">
       <rule grant="true">
         <permission>Manage everything</permission>
         <facet>SuperSpace</facet>
       </rule>
     </filter>

Just change that to have the tab appear where you want.

> On top of all this, there is the question of friendly readable URLs  
> - could
> that be achieved with the REST API code?

You mean use a path instead of a document id? You could write a URL  
codec for that, I don't know if there's documentation on it in the  
book but see
http://doc.nuxeo.org/5.1/components/org.nuxeo.ecm.platform.url.service.DocumentViewCodecService.html
and the provided contrib to that extension point linked from there.  
Have a look at DocumentIdCodec -- not sure replacing codecs is  
allowed. And you'll want to make yours the default so that generated  
URLs use it.

Florent

-- 
Florent Guillaume, Director of R&D, Nuxeo
Open Source Enterprise Content Management (ECM)
http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87

_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm

Reply via email to