optimising dynamic XML datasource
This is an open discussion with 2 replies, filed under Troubleshooting.
Search
How is this possible? A textfield for a small xslt block of code instead of just one expression?
Something I will think about. It certainly wouldn't be a stretch to allow an XSLT block rather than a single xpath. I'll chat to the team about it.
I assume an xslt block will be in the dynamic/external DSes of RC1, so you can combine nodes within one parent. Also it would need a field for excluding namespaces.(the bunch of unused ones you get on each node in for exampel a photofeed. Just like you can declare namespaces, you should be able to leave them out. On a xslt page this would be simple, but since for the DS editor the inner workings are hidden from us, there is no way I can currently achieve this.
Create an account or sign in to comment.
When selecting nodes from a photofeed in the external xml DS you can get rid of a lot of unneeded XML by selecting specific nodes. If you select root only the root will have a bunch of namespaces, however the optimized specific XML has namespaces in each entry, which I find a waste. Since I only use 2 of them. How can I get rid of the unused ones? or even better create a parent node that has them all once (like /)?
Also if you need 2 or 3 nodes per entry spread out accross parents, you need to grab the main parent. I'd rather grab specific child nodes here AND there; I would like to select multiple nodes in the datasource field like;
How is this possible? A textfield for a small xslt block of code instead of just one expression?
resource1 resource2