Accessing a property from the master document type
Hello, I am trying to figure out the xslt syntax for getting the value of a property that belongs to the master document type of a node. Something like <xsl:value-of select="propName"/> appears to work only for properties that belong to the document type itself, and not the document type I am inheriting from (the master document type).
it *should* work that way. Properties defined on the parent document type should also be available on the child doc, and therefore also in the cached xml using the syntax from your post.
Are you sure prop exists on the parent document type?
I'm not quite sure why your example works unless you're inside some kind of loop (for each og apply-templates). You should include $currentPage as well I think.
I tried some more tests and realised the problem was the font I was using. When I tried @id instead of a property, it worked, so I assumed the problem was the master document type, but infact it was because the font supported numerals (for @id) but not the characters I was using in the custom property.
Accessing a property from the master document type
Hello, I am trying to figure out the xslt syntax for getting the value of a property that belongs to the master document type of a node. Something like <xsl:value-of select="propName"/> appears to work only for properties that belong to the document type itself, and not the document type I am inheriting from (the master document type).
Thank you.
christos,
it *should* work that way. Properties defined on the parent document type should also be available on the child doc, and therefore also in the cached xml using the syntax from your post.
Are you sure prop exists on the parent document type?
Cheers,
/Dirk
Hi Christos
I'm not quite sure why your example works unless you're inside some kind of loop (for each og apply-templates). You should include $currentPage as well I think.
Like this:
Does it help in any way to include the currentPage variable?
/Kim Andersen
I tried some more tests and realised the problem was the font I was using. When I tried @id instead of a property, it worked, so I assumed the problem was the master document type, but infact it was because the font supported numerals (for @id) but not the characters I was using in the custom property.
My apologies, and thank you for your help.
Ahh, weird, but great that you got it solved Christos. I would never have thought of that as the problem :)
/Kim A
is working on a reply...