Height and Width property in macro disappers in xml
Hi all,
I have tried to find a solution for this problem but think it has something to do with the umbraco code.
Try make a clean macro - make a Height and Width property ( number )
Go to a template and insert the macro. Have the xslt to do a <xsl:copy-of select="/macro" /> and look in the html. The parameters isent in the output. Try rename them to Height2 and Width2 ( both macro and in template ) and now it works fine.
The weird think is that when you insert it through the wysiwyg editor it works fine. Anybody have an idea?
I'd assume that these are reserved words, probably due to the fact that when you drop your macro on your template, you do so as a .NET user control, all of which have a height and width property already defined on them. My guess would be that these are getting consumed by .NET and so aren't getting passed through.
Height and Width property in macro disappers in xml
Hi all,
I have tried to find a solution for this problem but think it has something to do with the umbraco code.
Try make a clean macro - make a Height and Width property ( number )
Go to a template and insert the macro. Have the xslt to do a <xsl:copy-of select="/macro" /> and look in the html. The parameters isent in the output. Try rename them to Height2 and Width2 ( both macro and in template ) and now it works fine.
The weird think is that when you insert it through the wysiwyg editor it works fine. Anybody have an idea?
I'd assume that these are reserved words, probably due to the fact that when you drop your macro on your template, you do so as a .NET user control, all of which have a height and width property already defined on them. My guess would be that these are getting consumed by .NET and so aren't getting passed through.
Matt
Of course @Matt is one of the first ones to help - this is for your great help til the umbraco community - H5YR!!
And now to the question again :) That sounds as a reason for the properties to be eaten in the template.
is working on a reply...