I had a razor macro that output a nav list and all was working fine over the last couple of days. Overnight something happened and this morning, instead of rendering the razor, it output the razor code as text... Ticklnig web.config smartened it up.
There were no changes made to the site over the last 24 hours (it's being reviewed by the client), and the error log (we have concierge) didn't reveal anything.
Has anyone else had isues where razor stopped rendering and instead started outputting code?
@Jonathan: I'd recommend that you upgrade to 4.7RC once it's out early next week (easy upgrade!). It contains a whole new and more stable Razor engine. However, like Jonas I haven't encountered the issue either.
Jonas, Niels thanks for your responses. Yes, all Razor scripts (new and old) started to render again, but only after I tickled the web.config (ie recycled app pool)
As for the 4.7 upgrade, yeah, I'm definitely excited to do that! I've been using uComponents extensively for node traversing under razor, and am excited to move all that back into the core (Model.DescendantsAndSelf(), etc)
And while I have the ear of people in the know ;) just how easy of an "easy upgrade". I read elsewhere that the reason this is a 4.7 release (instead of 4.6.2) is because the upgrade path will be a bit tricky...
Upgrades are almost as easy as usual, just overwrite /bin /install /umbraco and /umbraco_client. The "tricky" bit is merging your web.config file and the umbracoSettings.config file. Nothing a little Winmerge won't solve! Besides, the additions in the web.config file are clearly marked as 4.6.2 / 4.7 changes.
razor outputting source instead of rendering
I had a razor macro that output a nav list and all was working fine over the last couple of days. Overnight something happened and this morning, instead of rendering the razor, it output the razor code as text... Ticklnig web.config smartened it up.
There were no changes made to the site over the last 24 hours (it's being reviewed by the client), and the error log (we have concierge) didn't reveal anything.
Has anyone else had isues where razor stopped rendering and instead started outputting code?
Any ideas?
We're running 4.6.2
Cheers
Jonathan
sorry - I meant to say we are running 4.6.1
(tried to edit my post, but got repeated "error parsing xslt file" errors)
I played quite rather much with razor on 4.6.1 but I dont recognize the problem. What happens when you try to add new razor scripts? Do they render?
@Jonathan: I'd recommend that you upgrade to 4.7RC once it's out early next week (easy upgrade!). It contains a whole new and more stable Razor engine. However, like Jonas I haven't encountered the issue either.
Hi guys
Jonas, Niels thanks for your responses. Yes, all Razor scripts (new and old) started to render again, but only after I tickled the web.config (ie recycled app pool)
As for the 4.7 upgrade, yeah, I'm definitely excited to do that! I've been using uComponents extensively for node traversing under razor, and am excited to move all that back into the core (Model.DescendantsAndSelf(), etc)
And while I have the ear of people in the know ;) just how easy of an "easy upgrade". I read elsewhere that the reason this is a 4.7 release (instead of 4.6.2) is because the upgrade path will be a bit tricky...
Cheers
Jonathan
Upgrades are almost as easy as usual, just overwrite /bin /install /umbraco and /umbraco_client. The "tricky" bit is merging your web.config file and the umbracoSettings.config file. Nothing a little Winmerge won't solve! Besides, the additions in the web.config file are clearly marked as 4.6.2 / 4.7 changes.
Oh good - so the wiki posting about upgrade procedure still stands.
Thanks for clarifying
Jonathan
is working on a reply...