I have checked that IUSER as well as NETWORK as well as NETWORK SERVICE (since I couldn't recall which needs it) full control permissions and told it to replace all permissions recursively. This didn't solve the issue.
when I go to the Developer section and open one of the XSLT's and try to save it I get the following error:
Notice is has /bin/bin/ in the path. I am sure that's more then likely the issue here, although I don't know how or where to fix this.
Error occuredSystem.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\Users\Kyle\Web Development\Sites\KPJ\bin\bin\umbraco.editorControls.dll' or one of its dependencies. The system cannot find the file specified.
I'm still looking into things with my 4.5 upgrade and haven't had a chance to really understand all the changes, but it looks like you have to modify the XSLT - here's a good post: http://our.umbraco.org/forum/developers/xslt/10125-Porting-dandrayne's-Business-Starter-Pack-to-45-xslt-horrors
I've started making changes to my app and it looks like the XSLT node tree navigation is more straight forward. Here are a few examples:
When using removing the \bin\-folder in config/xsltExtensions.config then the default blog works, but my website gets the path error file:///C:\mypath\wwwroot\..umbraco.editorControls.dll.
But when I update the config/xsltExtensions.config with the \bin\-folder before my umbraco.editorControls and Umlaut.Umb.Blog then my site workds fine but my blog gets the...
Got around the problem by continuing using /bin/-folder and replacing the "macro" statements in blog templates with XsltResult-Package (<%@ Register TagPrefix="XsltResult" Assembly="XsltResult" Namespace="XsltResult" %>).
This made the site kind of work for a while, but this feels like a temporary solution. There seems to be many problems (referenses) linked to having the "wrong" path in the xsltExtensions.config file.
Actually the Blog worked fine post installation, but it had changed the xsltExtensions.config(removed /bin/) which resulted in a File not found error (..\wwwroot\..umbraco.editorControls.dll) on my main site.
I kind of solved it (not realy a solution to the main problem but the site works as it should now) by copying the two dll:s to the root folder and changing the paths in the xsltExtensions to assembly="/umbraco.editorControls" and assembly="/Umlaut.Umb.Blog".
I see this topic is a bit old, but thought I'd try anyway. I'm brand new to Umbraco so please excuse me if I say something silly. I'm using Umbraco v 4.5.2 and I've just installed the Blog4Umbraco_2.0.26_for_4.5.zip package. The installation went fine and I can create a new blog post with no errors, but when I try to preview /blog I get the standard blog skin but with errors:
If I go to the developer section and try to save any of those xslt files I get an error message:
Error occured
System.OverflowException: Value was either too large or too small for an Int32. at System.Convert.ToInt32(Double value) 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 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.XslCompiledTransform.Transform(IXPathNavigable input, XsltArgumentList arguments, TextWriter results) at umbraco.presentation.webservices.codeEditorSave.SaveXslt(String fileName, String oldName, String fileContents, Boolean ignoreDebugging)
As reccommended, I've checked the /config/xsltExtensions.config file and it seems alright:
Unfortunately the Blog 4 Umbraco package is so full of bugs that it neither "rocks" nor is "awesome" (words you will read with disturbing regularity in this forum).
I managed to get the damn thing working eventually on a couple of websites but I still have random error messages appearing when posting. For any new Blogs that I need to install I either write something simple or use either the excellent BlogEngine.Net or Wordpress blogging engines; both of which offer far more functionality, allow you to keep your hair AND actually work out of the box :-)
I've tried uninstalling and reinstalling Blog4Umbraco_2.0.26_for_4.5 again today but same result.
A bit more info, in case it's useful: Here's what the blog page looks like immediately after install: "Error parsing XSLT file: \xslt\BlogCategories.xslt" etc
If I go to one of the blog xslt files and try to save it as-is I get this error: "System.OverflowException: Value was either too large or too small for an Int32." (I've tried ticking "Skip Testing" which saves the file, but the page still doesn't display properly)
In this case, if I hard code the xslt to go straight to the node id of the blog (ie, change "$currentPage/ancestor-or-self::Blog/@id" to "2978") then this gets rid of the error and this particular xslt appears to work.
However I tied going through all the xslt files and making the same change but some of them are a bit more complicated than that. Is this my only option? Has anyone else had the same experience and managed to solve it?
I'm using Umbraco v 4.5.2 Pro with Courier and Contour, I'm running multiple websites on one instance of Umbraco and I'm using Safari v 4.0 as a browser if this makes any difference.
Thanks very much for your reccomendation Kevin. BlogEngine.Net does look really good, I will check it out. It would be preferable to have something that linked directly in to Umbraco, but failing that then just a blog that works would do. :)
To stop the error "System.OverflowException: Value was either too large or too small for an Int32." you need to test the variable. For example, I usually test using an if statement - something like this:
<xsl:if test="$blogRoot > 0">
...
</xsl:if>
Note that your code will work fine if you "Skip testing" (as long as there isn't a real error!) . As you found out, if you hard code the value it doesn't complain.
Also, whilst trying to get the blog to work I found some of the (supposedly) 4.5 updated code still had the old syntax e.g. I think it was in the rss.xslt file there was something like:
$pageId/data [@alias = 'description']
instead of the newer syntax:
$pageId/description
- this didn't throw an error but obviously the rss feed description was empty. I gave up trying to get the blog code to work after that as there had obviously been no testing (they were probably too busy telling each other how "awesome" they were lol :-)
BTW There have been a few attempts to integrate Umbraco and BlogEngine.Net but I'm not sure uf they have succeeded. Try searching and you'll find a few posts detailing some people's attempts.
My blog *seems* to be working now, so I thought I'd share my solution in case it's helpful to anyone else.
I made a few minor changes to the XSLT files (thanks for the advice!) which fixed the XSLT errors on save, but the blog still wans't displaying correctly. As I mentioned, I'm running multiple websites on one instance of Umbraco, using domains to differentiate between them. So I added a new subdomain blog.mywebsite.com and pointed it to my web server, set up the new domain in IIS, then added the new domain in Umbraco by clicking on "Blog" and selecting "Manage Hostnames". Viola! The blog started working straight away.
I feel a bit silly because I really should have figured that out a while ago, but at least it's working now. :) Now I'm off to have a play and see if I can break something else, tee hee. :P Thanks again for your help!!
Fresh Install Blog4Umbraco Errors
just installed Blog4Umbraco and I am getting a serious of errors for each xslt that read something similar to:
Error parsing XSLT file: \xslt\BlogMetaWeblogChannel.xslt
I have checked that IUSER as well as NETWORK as well as NETWORK SERVICE (since I couldn't recall which needs it) full control permissions and told it to replace all permissions recursively. This didn't solve the issue.
when I go to the Developer section and open one of the XSLT's and try to save it I get the following error:
Notice is has /bin/bin/ in the path. I am sure that's more then likely the issue here, although I don't know how or where to fix this.
I had the same problem and solved it by opening config/xsltExtensions.config and updating the assembly attributes for the exts. Previous values were:
assembly="/bin/umbraco.editorControls"
new value:
assembly="umbraco.editorControls"
Seems as though the 4.5 build assumes the assemblies are in the bin, which I suppose they should be ;)
Saxon,
That got rid of the erros when trying to save the XML, however I still get errors when viewing the blog page.
Hi kylepauljohnson,
I'm still looking into things with my 4.5 upgrade and haven't had a chance to really understand all the changes, but it looks like you have to modify the XSLT - here's a good post: http://our.umbraco.org/forum/developers/xslt/10125-Porting-dandrayne's-Business-Starter-Pack-to-45-xslt-horrors
I've started making changes to my app and it looks like the XSLT node tree navigation is more straight forward. Here are a few examples:
Before:
After:
Before:
After:
Before:
After:
Hope that helps!
Saxon.
Finally got a chance to do some reading on the 4.5 release (it's always more fun to shoot first and ask questions later, no?) Here ya go:
http://our.umbraco.org/wiki/reference/xslt/45-xml-schema/xslt-examples-updated-to-new-schema
Having the same problem.
When using removing the \bin\-folder in config/xsltExtensions.config then the default blog works, but my website gets the path error file:///C:\mypath\wwwroot\..umbraco.editorControls.dll.
But when I update the config/xsltExtensions.config with the \bin\-folder before my umbraco.editorControls and Umlaut.Umb.Blog then my site workds fine but my blog gets the...
...on all XSLT:s?
How do I get both to work, any ideas?
Tony H: What version of Umbrao are you running?
kylepauljohnson: I'm using 4.5.1.
Got around the problem by continuing using /bin/-folder and replacing the "macro" statements in blog templates with XsltResult-Package (<%@ Register TagPrefix="XsltResult" Assembly="XsltResult" Namespace="XsltResult" %>).
This made the site kind of work for a while, but this feels like a temporary solution. There seems to be many problems (referenses) linked to having the "wrong" path in the xsltExtensions.config file.
Still looking for a solution...
Did you make sure you installed the version for Umbraco 4.5?
Blog4Umbraco_2.0.26_for_4.5.zip
from http://our.umbraco.org/projects/collaboration/blog-4-umbraco
Regards,
Kevin
Yes, I,m using 2.0.26.
Actually the Blog worked fine post installation, but it had changed the xsltExtensions.config(removed /bin/) which resulted in a File not found error (..\wwwroot\..umbraco.editorControls.dll) on my main site.
I kind of solved it (not realy a solution to the main problem but the site works as it should now) by copying the two dll:s to the root folder and changing the paths in the xsltExtensions to assembly="/umbraco.editorControls" and assembly="/Umlaut.Umb.Blog".
Regards, Tony H
I'm having these issues as well. I've not tried looked at the xslt's yet but my xsltExtensions.config has nothing in it...Guessing that isn't correct.
Also When I try and save a post I just get some generic error in the backoffice. Not sure where to look for that.
I'm new to Umbraco and using 4.5.2 and 2.0.26
Nope, that isn't correct. xsltExtensions should have lines in it, my says:
<ext assembly="/umbraco.editorControls" type="umbraco.editorControls.tags.library" alias="tagsLib"></ext>
<ext assembly="/Umlaut.Umb.Blog" type="Umlaut.Umb.Blog.BlogLibrary" alias="BlogLibrary"></ext>
Then I had to put the dll:s in the root directory (due to the dll-refrense missmatch between the Umbraco and UmbracoBlog).
But I guess you should try to reinstall the blog because there seem to be some fatal issues with your last Blog install.
// T
Thanks Saxon.
That helped me with my tag cloud
assembly="/bin/umbraco.editorControls"
new value:
assembly="umbraco.editorControls"
Hi there,
I see this topic is a bit old, but thought I'd try anyway. I'm brand new to Umbraco so please excuse me if I say something silly. I'm using Umbraco v 4.5.2 and I've just installed the Blog4Umbraco_2.0.26_for_4.5.zip package. The installation went fine and I can create a new blog post with no errors, but when I try to preview /blog I get the standard blog skin but with errors:
Error parsing XSLT file: \xslt\BlogRssFeedLink.xslt
Error parsing XSLT file: \xslt\Blogpages.xslt
Error parsing XSLT file: \xslt\BlogCategories.xslt
Error parsing XSLT file: \xslt\BlogLatestComments.xslt
If I go to the developer section and try to save any of those xslt files I get an error message:
Error occured
System.OverflowException: Value was either too large or too small for an Int32.
at System.Convert.ToInt32(Double value)
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 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.XslCompiledTransform.Transform(IXPathNavigable input, XsltArgumentList arguments, TextWriter results)
at umbraco.presentation.webservices.codeEditorSave.SaveXslt(String fileName, String oldName, String fileContents, Boolean ignoreDebugging)
As reccommended, I've checked the /config/xsltExtensions.config file and it seems alright:
<ext assembly="umbraco.editorControls" type="umbraco.editorControls.tags.library" alias="tagsLib">
</ext>
<ext assembly="Umlaut.Umb.Blog" type="Umlaut.Umb.Blog.BlogLibrary" alias="BlogLibrary">
</ext>
I've compared my xslt files to some of the suggestions people have made, but I seem to have the newest version already, unless I've missed something.
I've tried uninstalling and reinstalling different versions but same problems. Any ideas where to go from here?
Thanks kindly!
Hi Tracey,
Unfortunately the Blog 4 Umbraco package is so full of bugs that it neither "rocks" nor is "awesome" (words you will read with disturbing regularity in this forum).
I managed to get the damn thing working eventually on a couple of websites but I still have random error messages appearing when posting. For any new Blogs that I need to install I either write something simple or use either the excellent BlogEngine.Net or Wordpress blogging engines; both of which offer far more functionality, allow you to keep your hair AND actually work out of the box :-)
I've tried uninstalling and reinstalling Blog4Umbraco_2.0.26_for_4.5 again today but same result.
A bit more info, in case it's useful: Here's what the blog page looks like immediately after install: "Error parsing XSLT file: \xslt\BlogCategories.xslt" etc
If I go to one of the blog xslt files and try to save it as-is I get this error: "System.OverflowException: Value was either too large or too small for an Int32."

(I've tried ticking "Skip Testing" which saves the file, but the page still doesn't display properly)
In this case, if I hard code the xslt to go straight to the node id of the blog (ie, change "$currentPage/ancestor-or-self::Blog/@id" to "2978") then this gets rid of the error and this particular xslt appears to work.
However I tied going through all the xslt files and making the same change but some of them are a bit more complicated than that. Is this my only option? Has anyone else had the same experience and managed to solve it?
I'm using Umbraco v 4.5.2 Pro with Courier and Contour, I'm running multiple websites on one instance of Umbraco and I'm using Safari v 4.0 as a browser if this makes any difference.
Thanks very much for your reccomendation Kevin. BlogEngine.Net does look really good, I will check it out. It would be preferable to have something that linked directly in to Umbraco, but failing that then just a blog that works would do. :)
To stop the error "System.OverflowException: Value was either too large or too small for an Int32." you need to test the variable. For example, I usually test using an if statement - something like this:
</xsl:if>
Note that your code will work fine if you "Skip testing" (as long as there isn't a real error!) . As you found out, if you hard code the value it doesn't complain.
Also, whilst trying to get the blog to work I found some of the (supposedly) 4.5 updated code still had the old syntax e.g. I think it was in the rss.xslt file there was something like:
instead of the newer syntax:
- this didn't throw an error but obviously the rss feed description was empty. I gave up trying to get the blog code to work after that as there had obviously been no testing (they were probably too busy telling each other how "awesome" they were lol :-)
BTW There have been a few attempts to integrate Umbraco and BlogEngine.Net but I'm not sure uf they have succeeded. Try searching and you'll find a few posts detailing some people's attempts.
SUCCESS!
My blog *seems* to be working now, so I thought I'd share my solution in case it's helpful to anyone else.
I made a few minor changes to the XSLT files (thanks for the advice!) which fixed the XSLT errors on save, but the blog still wans't displaying correctly. As I mentioned, I'm running multiple websites on one instance of Umbraco, using domains to differentiate between them. So I added a new subdomain blog.mywebsite.com and pointed it to my web server, set up the new domain in IIS, then added the new domain in Umbraco by clicking on "Blog" and selecting "Manage Hostnames". Viola! The blog started working straight away.
I feel a bit silly because I really should have figured that out a while ago, but at least it's working now. :) Now I'm off to have a play and see if I can break something else, tee hee. :P Thanks again for your help!!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.