Anyway, the resulting .dll is 50k smaller than the one in the release build, it also throws a warning Master template is the same as the current template. It would course an endless loop! it seems the release build is different than the source it is tagged with on codeplex?
Cannot get Razor to work in 4.6
I create a new Razor scripting file. Just just a test string in there (no actual razor code), then put the macro in a template and it displays:
Error loading MacroEngine script (file: test.razor)
Nothing else in the log table.. etc.
Hi Chad
I'm getting the same problem. If you look at the trace (?umbDebugShowTrace=true) the actual error message is;
Only happens when using a scripting file/macro combination. If you put the code directly into a template like;
Everything works fine.
Regards
Evan
The file extension is not being passed, so it doesn't know what Macro engine to use to perform the rendering. (macro.cs line 356)
ConvertToMacroModel method does not set the 'ScriptLanguage' property, there is then (marco.cs - line 1059):
ScriptLanguage property is null - so the system doesn't know what Macro engine to use.
I'd throw up a patch but this is my first dabble with the source, I've no idea what I might break!
Can either of you log it as a bug on codeplex please
Done
http://umbraco.codeplex.com/workitem/29858
In ConvertToMacroModel I've thrown a quick check in place to see if it's null and if we can derive it from the ScriptFile:
Argh, editing seems broken.
Anyway, the resulting .dll is 50k smaller than the one in the release build, it also throws a warning Master template is the same as the current template. It would course an endless loop! it seems the release build is different than the source it is tagged with on codeplex?
Nevermind, found the extra 50k, the umbraco.dll in the 4.6 download has been compiled in debug mode :/
We believe we've fixed all the bugs reported since the release. Could you help us test with this nightly build: http://bit.ly/gtoyV1
wow, thanks for your work. 4.6.* must be a very stable and classic version.
Confirmed now working fine
is working on a reply...