I had posted this problem a few days ago and believed that it was fixed. Sadly, after updating the content it has risen again. I'll paste my previous post here to explain the situation fully.
am running two Umbraco websites, with both being maintained by someone other than me.
Recently, one of them suffered a problem after an unknown change in
the admin panel. Rather than displaying a simple slideshow with rotating
images on the home page an error at the top of the page read.
Error parsing XSLT file: \xslt\SlideshowJS.xslt
>
I have checked both the Slideshow.xslt and the SlideshowJS.xslt files
we currently have and they match the working versions on one of our
other websites, so I can't help but feel that that's not the problem. I
checked the stack trace on the home page and found the following errors:
niceurl No node found at '2739' 0.0469947996183873 0.000797
niceurl No node found at '2744' 0.0471640948779803 0.000169
niceurl No node found at '2740' 0.0475817457246661 0.000418
niceurl No node found at '2741' 0.0477409838401249 0.000159
niceurl No node found at '2745' 0.0478935171928276 0.000153
niceurl No node found at '2750' 0.0480435362594967 0.000150
niceurl No node found at '2751' 0.0482030537400703 0.000160
niceurl No node found at '2913' 0.0484002855111474 0.000197
niceurl No node found at '2749' 0.0488011744509428 0.000401
After toying with the xslt files a bit more I tried to save the SlideshowJS.xslt file, only to be given the following error
System.OverflowException: Value was either too large or too small for an Int32.
at System.Convert.ToInt32(Double value)
at System.Double.System.IConvertible.ToInt32(IFormatProvider provider)
at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at System.Xml.Xsl.Runtime.XmlQueryRuntime.ChangeTypeXsltArgument(XmlQueryType xmlType, Object value, Type destinationType)
at System.Xml.Xsl.Runtime.XmlQueryContext.InvokeXsltLateBoundFunction(String name, String namespaceUri, IList`1[] args)
at (XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime)
at Root(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime)
at Execute(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime)
at System.Xml.Xsl.XmlILCommand.Execute(Object defaultDocument,
XmlResolver dataSources, XsltArgumentList argumentList,
XmlSequenceWriter results)
at System.Xml.Xsl.XmlILCommand.Execute(Object defaultDocument,
XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter
writer, Boolean closeWriter)
at System.Xml.Xsl.XmlILCommand.Execute(IXPathNavigable
contextDocument, XmlResolver dataSources, XsltArgumentList argumentList,
XmlWriter results)
at System.Xml.Xsl.XmlILCommand.Execute(IXPathNavigable
contextDocument, XmlResolver dataSources, XsltArgumentList argumentList,
TextWriter results)
at System.Xml.Xsl.XslCompiledTransform.Transform(IXPathNavigable input, XsltArgumentList arguments, TextWriter results)
at umbraco.presentation.webservices.codeEditorSave.SaveXslt(String
fileName, String oldName, String fileContents, Boolean ignoreDebugging)
Can anyone here see any reasons as to why this is happening? Any help with this would be much appreciated.
I asume you're running Umbraco 4.0 or earlier since your XSLT uses the older xml syntax. If you've upgraded the site to Umbraco 4.5 you'll either need to update the xslt to use the new xml schema or set the config file flag to use the legacy schema.
But assuming you're running 4.0 the problem might be resolved by simply republishing the content. In the CONTENT section of umbraco, right-click the homepage of the site and select the 'Republish' menu. Tick the 'publish children' box and click OK. Repeat this for each of the top-level pages in your site.
Does that resolve it?
If not, right-click on the very top item in the treeview, 'Content' and select the 'Republish entire site'. These two menus do different things despite a similar name.
Error parsing XSLT File for Slideshow script
I had posted this problem a few days ago and believed that it was fixed. Sadly, after updating the content it has risen again. I'll paste my previous post here to explain the situation fully.
The XSLT file in question is here. http://pastebin.com/NaVwD7ku
am running two Umbraco websites, with both being maintained by someone other than me.
Recently, one of them suffered a problem after an unknown change in the admin panel. Rather than displaying a simple slideshow with rotating images on the home page an error at the top of the page read.
>
I have checked both the Slideshow.xslt and the SlideshowJS.xslt files we currently have and they match the working versions on one of our other websites, so I can't help but feel that that's not the problem. I checked the stack trace on the home page and found the following errors:
niceurl No node found at '2739' 0.0469947996183873 0.000797
niceurl No node found at '2744' 0.0471640948779803 0.000169
niceurl No node found at '2740' 0.0475817457246661 0.000418
niceurl No node found at '2741' 0.0477409838401249 0.000159
niceurl No node found at '2745' 0.0478935171928276 0.000153
niceurl No node found at '2750' 0.0480435362594967 0.000150
niceurl No node found at '2751' 0.0482030537400703 0.000160
niceurl No node found at '2913' 0.0484002855111474 0.000197
niceurl No node found at '2749' 0.0488011744509428 0.000401
After toying with the xslt files a bit more I tried to save the SlideshowJS.xslt file, only to be given the following error
System.OverflowException: Value was either too large or too small for an Int32.
at System.Convert.ToInt32(Double value)
at System.Double.System.IConvertible.ToInt32(IFormatProvider provider)
at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at System.Xml.Xsl.Runtime.XmlQueryRuntime.ChangeTypeXsltArgument(XmlQueryType xmlType, Object value, Type destinationType)
at System.Xml.Xsl.Runtime.XmlQueryContext.InvokeXsltLateBoundFunction(String name, String namespaceUri, IList`1[] args)
at (XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime)
at Root(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime)
at Execute(XmlQueryRuntime {urn:schemas-microsoft-com:xslt-debug}runtime)
at System.Xml.Xsl.XmlILCommand.Execute(Object defaultDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlSequenceWriter results)
at System.Xml.Xsl.XmlILCommand.Execute(Object defaultDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter writer, Boolean closeWriter)
at System.Xml.Xsl.XmlILCommand.Execute(IXPathNavigable contextDocument, XmlResolver dataSources, XsltArgumentList argumentList, XmlWriter results)
at System.Xml.Xsl.XmlILCommand.Execute(IXPathNavigable contextDocument, XmlResolver dataSources, XsltArgumentList argumentList, TextWriter results)
at System.Xml.Xsl.XslCompiledTransform.Transform(IXPathNavigable input, XsltArgumentList arguments, TextWriter results)
at umbraco.presentation.webservices.codeEditorSave.SaveXslt(String fileName, String oldName, String fileContents, Boolean ignoreDebugging)
Can anyone here see any reasons as to why this is happening? Any help with this would be much appreciated.
I asume you're running Umbraco 4.0 or earlier since your XSLT uses the older xml syntax. If you've upgraded the site to Umbraco 4.5 you'll either need to update the xslt to use the new xml schema or set the config file flag to use the legacy schema.
But assuming you're running 4.0 the problem might be resolved by simply republishing the content. In the CONTENT section of umbraco, right-click the homepage of the site and select the 'Republish' menu. Tick the 'publish children' box and click OK. Repeat this for each of the top-level pages in your site.
Does that resolve it?
If not, right-click on the very top item in the treeview, 'Content' and select the 'Republish entire site'. These two menus do different things despite a similar name.
If that doesn't resolve it, let us know.
cheers,
doug.
Well, this is strange.
Our windows server received an update today and after installing this update and restarting the server everything seems to be working, again.
Hopefully this time things will be fine. Thanks for the help anyway!
is working on a reply...