The way I see it - all of my custom xslt and master page types would immediatly break if I did so.
The only way I could think of doing this would be to create a bunch of new templates and create a list of custom xslt macros. But then what happens to all of my blog content?
Can anyone think of a better way?
Any ideas welcome, I'm struggeling to find any information on this.
I'm assuming you mean upgrade to be able to run Blog4Umbraco with the new xslt schema on 4.5? Have you thought about upgrading to 4.5 but using the old schema? (Include the following in your web.config:)
<UseLegacyXmlSchema>true</UseLegacyXmlSchema>
This seems like the simplest way potentially to run the latest version of Umbraco and the blog simultaneously, but not having tried it I can't be sure it would work for reasons other than XSLT. The other options really are only to either wait for a package upgrade, or get down to some coding and work on an upgrade.
I know the core team are busy working on checking all packages' compatability with 4.5. Maybe because it was a core package they might update Blo4Umbraco some time soon, but who knows.
It seems that setting UseLegacyXMLSchema to true is not helping in this case. I still get broken xslt.
"Cannot find a script or an extension object associated with namespace 'urn:tagsLib' is the error I get. Is it possible somehow to use a new namespace?
As mentioned above, upgrading to new package overwrites all tweaks in the xslt.
Upgrading Blog4Umbraco
Hi,
Does anyone know how to upgrade this package.
The way I see it - all of my custom xslt and master page types would immediatly break if I did so.
The only way I could think of doing this would be to create a bunch of new templates and create a list of custom xslt macros. But then what happens to all of my blog content?
Can anyone think of a better way?
Any ideas welcome, I'm struggeling to find any information on this.
Cheers,
Hi,
I'm assuming you mean upgrade to be able to run Blog4Umbraco with the new xslt schema on 4.5? Have you thought about upgrading to 4.5 but using the old schema? (Include the following in your web.config:)
This seems like the simplest way potentially to run the latest version of Umbraco and the blog simultaneously, but not having tried it I can't be sure it would work for reasons other than XSLT. The other options really are only to either wait for a package upgrade, or get down to some coding and work on an upgrade.
I know the core team are busy working on checking all packages' compatability with 4.5. Maybe because it was a core package they might update Blo4Umbraco some time soon, but who knows.
Hope this helps.
A perfectly sound assumption - I actually meant upgradng the blog package itself but your answer does help me on a number of levels.
I didnt know about the <UseLegacyXmlSchema>, thanks.
Greyhound... according to Per's wiki article, the Blog4Umbraco package has been updated to run now on 4.5. Happy days.
it says it's being tested
any estimated date when the package will be updated to 4.5?
Installing Blog4umbraco was breaking Umbraco 4.5
Just found this post which details modifying the path to stop the blog breaking the whole site:
http://our.umbraco.org/forum/core/41-feedback/10203-Blog-for-Umbraco-breaks-XLST-in-Umbraco-45
It seems that setting UseLegacyXMLSchema to true is not helping in this case. I still get broken xslt.
"Cannot find a script or an extension object associated with namespace 'urn:tagsLib' is the error I get. Is it possible somehow to use a new namespace?
As mentioned above, upgrading to new package overwrites all tweaks in the xslt.
Hi Froad,
Did you remember to remove the /bin/ reference from the config file (link in my post above)
This sorted out the issue for me.
XSLT tweaks - this is a pain but I recently developed another site and simply copied and pasted my original tweaks in and went from there.
That did the trick!
Thank you!
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.