I would like to use Blog 4 Umbraco. Upon reading I saw it required umbraco 4. My website was using version 3 and I upgraded the website to version 4 (using the upgrade guide). After installing the package (from the repository) and settings some initial values I tried to visit the page. The blog page shows the following errors (althought you can navigate to Archive, About and Tag Cloud).
I also don't see the tag input control at the bottom of the screen, maybe that's a clue ?
I tried the followings things (that didn't work) to fix the problem: - Republished the Blog node - Reviewed the page trace (with the query string parameter) - Removed the welcome blog entry and added a new one - Reinstalled the package - Created a second umbraco website (with a complete fresh installation / database) - Searched on google / this forum, and tried some solutions
Version information: - Umbraco 4.0.3 - .Net 3.5 - Windows Server 2003 / IIS 6
Well, you could check your permissions, but apparently you can save changes, so they should be fine. Next, have a look in the windows event log to see if any unhandled exceptions appear there (though, they should also show in the trace).
What I usually do is strip everything out of the XSLT and start adding stuff until it breaks, at least then I'd have an idea of where it might be going wrong.
I've debugged some of the scripts, like you described. It seems it couldn't access the xslt extensions (like taglib, etc.). This was due xsltextensions.config wasn't writeable. After enabling this and reinstalling the package everything works fine.
Fantastic! It sounded like a permission problem, just didn't think of that one. Another lesson learned for me as well. Would you be so kind as to mark my answer as correct? Thanks!
Blog 4 Umbraco, XSLT errors
Hello,
I would like to use Blog 4 Umbraco. Upon reading I saw it required umbraco 4. My website was using version 3 and I upgraded the website to version 4 (using the upgrade guide). After installing the package (from the repository) and settings some initial values I tried to visit the page. The blog page shows the following errors (althought you can navigate to Archive, About and Tag Cloud).
Erorr parsing XSLT file: \xslt\BlogListPosts.xslt
Error parsing XSLT file: \xslt\BlogCategories.xslt
Error parsing XSLT file: \xslt\BlogLatestComments.xslt
Error parsing XSLT file: \xslt\BlogGetSkinInfo.xslt
I also don't see the tag input control at the bottom of the screen, maybe that's a clue ?
I tried the followings things (that didn't work) to fix the problem:
- Republished the Blog node
- Reviewed the page trace (with the query string parameter)
- Removed the welcome blog entry and added a new one
- Reinstalled the package
- Created a second umbraco website (with a complete fresh installation / database)
- Searched on google / this forum, and tried some solutions
Version information:
- Umbraco 4.0.3
- .Net 3.5
- Windows Server 2003 / IIS 6
With kinds regards,
Niels Bergsma
What errors did the page trace show? What happens when you go into the backend, open up BlogListPosts.xslt and save it, any error messages there?
Hi Sebastiaan,
I can open the bloglistposts.xslt file (in the backend) and save it, without getting any errors.
The trace shows the following (snippet):
Macro loaded from cache (ID: 57, Blog List Posts)
Rendering started (macro: Blog List Posts, type: 1, cacheRate: 0)
Before adding extensions
Extension added: urn:Exslt.ExsltCommon, ExsltCommon
Extension added: urn:Exslt.ExsltDatesAndTimes, ExsltDatesAndTimes
Extension added: urn:Exslt.ExsltMath, ExsltMath
Extension added: urn:Exslt.ExsltRegularExpressions, ExsltRegularExpressions
Extension added: urn:Exslt.ExsltStrings, ExsltStrings
Extension added: urn:Exslt.ExsltSets, ExsltSets
After adding extensions
Before performing transformation
After performing transformation
Well, you could check your permissions, but apparently you can save changes, so they should be fine. Next, have a look in the windows event log to see if any unhandled exceptions appear there (though, they should also show in the trace).
What I usually do is strip everything out of the XSLT and start adding stuff until it breaks, at least then I'd have an idea of where it might be going wrong.
Hi Sebastiaan,
I've debugged some of the scripts, like you described. It seems it couldn't access the xslt extensions (like taglib, etc.). This was due xsltextensions.config wasn't writeable. After enabling this and reinstalling the package everything works fine.
Thank you for taking the time to help me!
Fantastic! It sounded like a permission problem, just didn't think of that one. Another lesson learned for me as well.
Would you be so kind as to mark my answer as correct? Thanks!
is working on a reply...