Dennis, yes it work.
Here my test : 1) I can create types associated with the category 'latest_change' in the folder 4-07-2007 2) I create a new folder 5-07-2008. The locationmap change with the most recent folder. 3 ) But I still can create content inside 4-07-2008 and not inside 5-7-2008. It seems that the CMS is looking the old version of the locationmap. But I can clearly see the good version if I directly call the foldermap with the browser. Weird ;-) 2008/7/10 Dennis Dam <[EMAIL PROTECTED]>: > What happens if you statically generate the locationmap in your latest > mail? Can you create types of category "latest_change" in the most recent > folder then? > > Btw, does this matcher work? > > <match pattern="**:/content/website/home/newsletters/4-7-2008*"> > > > you might try > > <match pattern="**:/content/website/home/newsletters/4-7-2008"> > > or > > <match pattern="**:/content/website/home/newsletters/4-7-2008/**"> > > or both.. > > regards, > Dennis > > > > Hippo WCMTech wrote: > >> Ard, >> >> Here is the build : >> >> cms.locationmap.src=cocoon://extensions/locationmap/locationmap.xml >> cms.locationmap.eventCacheable=false >> >> The locationmap is generated and look like this : >> >> <locationmap> >> <components> >> <matchers default="locationmap"> >> <matcher src="nl.hippo.forrest.locationmap.WildcardLocationMapHintMatcher" >> name="locationmap"/> >> </matchers> >> </components> >> <locator> >> <match pattern="types:**"> >> <match >> pattern="*:/content/website/home/reference_tables/reference_table_detail"> >> <location src="reference_table"/> >> </match> >> <match >> >> pattern="*:/content/website/home/reference_tables/reference_table_detail/**"> >> <location src="reference_table"/> >> </match> >> <match >> pattern="*:/content/website/home/transactions/transaction_detail"> >> <location src="transaction"/> >> </match> >> <match pattern="**:/content/website/home/newsletters/4-7-2008*"> >> <location src="latest_change"/> >> </match> >> <match pattern="*:/content/website"> >> <location src="siteweb"/> >> </match> >> <match pattern="*:/content/website/**"> >> <location src="siteweb"/> >> </match> >> <match pattern="**"> >> <location src=""/> >> </match> >> </match> >> <match pattern="preview-url:**"/> >> </locator> >> </locationmap> >> >> Where the value "/content/website/home/newsletters/4-7-2008" is dynamic >> and >> based on the newest* *folder created inside the folder newsletters. So if >> we >> create a new folder 5-7-2009, the different types linked to the category >> "latest_change" will only be possible in this folder. >> >> You will find in attachment the extension in charge of the dynamic >> locationmap and the types.xml used. >> >> I 'm working with hippocms 6.5.2 but I can tell you which version of the >> location map jar. How can I get this information ? From the project.xml ? >> >> Thanks Ard, >> >> 2008/7/10 Ard Schrijvers <[EMAIL PROTECTED]>: >> >> >> >>> Hello, >>> >>> >>> >>>> Do I have to conclude that the locationmap can not be >>>> dynamically generated ? >>>> >>>> >>> It should just work. Locationmap can be dynamic, and event cacheable. >>> Can you mail the configuration you use for this locationmap. Also which >>> version you are using of hippo location map jar. >>> >>> Regards Ard >>> >>> >>> >>>> Thanks a lot, >>>> >>>> >>>> David, >>>> ******************************************** >>>> Hippocms-dev: Hippo CMS development public mailinglist >>>> >>>> Searchable archives can be found at: >>>> MarkMail: http://hippocms-dev.markmail.org >>>> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >>>> >>>> >>>> >>>> >>> ******************************************** >>> Hippocms-dev: Hippo CMS development public mailinglist >>> >>> Searchable archives can be found at: >>> MarkMail: http://hippocms-dev.markmail.org >>> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> ******************************************** >>> Hippocms-dev: Hippo CMS development public mailinglist >>> >>> Searchable archives can be found at: >>> MarkMail: http://hippocms-dev.markmail.org >>> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html >>> >>> > > -- > 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 > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
