Ross,

No, I don't think it's related to a regular expression issue either. I'm guessing that you expect that adding a category to a resource will still make the type show up in the default case (throuigh the catch all matcher). However, this is not the case: once you add the news-category to the news resource, that the news type can *only* be created under the folder "/content/documents/njw/news/*/**". So it cannot be created under any other folder from that point on. If you want the news type to show up in the default case, you can achieve that by adding a "default" category to every resource, and returning "default" for the catch all matcher. Something like this:

<match pattern="types:**">
 <!-- inside the types:** matcher, it is not necessary to match for the substring 
"types:" -->

 <!-- Map the news type to anything in njw/news -->
 <map:match pattern="*:/content/documents/njw/news/*/**">
   <location src="news-category"/>
 </map:match>
        
 <!-- "catch all" matcher -->
 <match pattern="**">
   <location src="default"/>
 </match>

</match>


<resource category="news,default" type="news">..</resource>
<resource category="default" type="text">..</resource>
<resource category="faq,default" type="faq">..</resource>

Hope this helps,

Dennis

rossputin wrote:
Hi,

I am still having trouble with this.  My types matchers is as below:

<match pattern="types:**">
<!-- inside the types:** matcher, it is not necessary to match for the
substring "types:" -->

<!-- Map the news type to anything in njw/news -->
<map:match pattern="*:/content/documents/njw/news/*/**">
<location src="news-category"/>
</map:match>
        
<!-- "catch all" matcher -->
<match pattern="**">
<location src=""/>
</match>
</match>

As soon as I add 'category="news-category"' to my news resource in
'types.xml' the news entry disappears from the drop down in the CMS for
document type.

Is this related to a regular expression issue?  Any ideas ?

Thanks for your help in advance,

regards,

Ross




rossputin wrote:
Hi guys,

I seem to have lost my way somewhere between CMS v6.04.x to the latest
version v6.05.03.  Previously I used an entry in locationmap.xml like:

<match pattern="*:/content/documents/njw/news/*/**">
<location src="news-category"/>
</match>

this would lookup a 'category' attribute in my types.xml document with a
value of 'news-category',

therefore when in the CMS if I tried to add a document under
/njw/news/2008/02/02, the only entry in the types drop down would be 'News
Article'.

I see the types.xsd now has no 'category' attribute, and instead, there is
'type' ?

Can someone point me to the documentation detailing how to use the new
setup?

Thanks for your help in advance.

Regards,

Ross.



--
Hippo
[EMAIL PROTECTED]

Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646

www.onehippo.com [EMAIL PROTECTED]

********************************************
Hippocms-dev: Hippo CMS development public mailinglist

Reply via email to