Hi, I am using the following XSLT to output events and group them by month. Now, this produces the exact results that I would expect in my development environment, but in the production site I get no output.
I have checked that my 'eventNodes' in fact return nodes so the data is there. But my first key(...) grouping returns nothing! Doing a copy-of gives me no nodes in produciton. Can anyone think of why this is? I am baffled and have been stuck on this for a couple of hours!
How is the dev made? a copy of the production? Check all properties for typos (especially case typos). Is the xml in sync, try republishing and check the date of the umbraco.config file. Recycle the app pool to get in sync...
Also check the cache options of the macro.
Also check the language settings of the installations (you are using dates...)
Hi Thomas and thanks for the tips...But if it was a cache or data mismatch my $eventNodes would be empty, right? The data seems to be there and the property names all match, but the following
does not return any results! Oh, here is another weird finding....if I run the same XSLT in another part of the site I DO get results back....wtf? I was getting ALL of the events back not just the ones from $eventNodes but when I changes the nested for-each select to include $eventNodes[key(...)] I got only the ones that I expected. So, is my xsl:key match attribute messing me up (since it matches ALL 'node' elements)?
Key grouping producing different results
Hi, I am using the following XSLT to output events and group them by month. Now, this produces the exact results that I would expect in my development environment, but in the production site I get no output.
I have checked that my 'eventNodes' in fact return nodes so the data is there. But my first key(...) grouping returns nothing! Doing a copy-of gives me no nodes in produciton. Can anyone think of why this is? I am baffled and have been stuck on this for a couple of hours!
Thanks,
Nik
Btw, here is the copy-of result from $eventNodes in production:
Thanks.
How is the dev made? a copy of the production? Check all properties for typos (especially case typos). Is the xml in sync, try republishing and check the date of the umbraco.config file. Recycle the app pool to get in sync...
Also check the cache options of the macro.
Also check the language settings of the installations (you are using dates...)
just some shots in the dark...
Hi Thomas and thanks for the tips...But if it was a cache or data mismatch my $eventNodes would be empty, right? The data seems to be there and the property names all match, but the following
$eventNodes[count(. | key('nodesByMMMM', string(umbraco.library:FormatDateTime(data [@alias=$groupByAlias],'MMMM')))[1]) = 1]
does not return any results! Oh, here is another weird finding....if I run the same XSLT in another part of the site I DO get results back....wtf? I was getting ALL of the events back not just the ones from $eventNodes but when I changes the nested for-each select to include $eventNodes[key(...)] I got only the ones that I expected. So, is my xsl:key match attribute messing me up (since it matches ALL 'node' elements)?
Thanks all!
-- Nik
is working on a reply...