Hi Amir

Have DAMP in 6.0.2 Mvc  without problems with razor calls - can you post an example? 

Sure someone will help.

Images will not save from the upload, they must be saved in the media section, well, on my install, as it appears that nobody else in the entire world is having the same saving and publishing issues - check this before you try anything else.

G

There are some problems with DAMP on v6, but you should be able to acces properties via Razor: http://our.umbraco.org/projects/backoffice-extensions/digibiz-advanced-media-picker/digibiz-advanced-media-picker/38209-Editing-crops-from-content-node-pressing-save-button-does-not-save

What errors do you get?

Jeroen

Its this bit of my Razor that's causing issues, if I remove the @media reference everything works fine. Access to the DAMP media in my XSLT is working fine oddly...

dynamic media = childPage.MediaById(childPage.navigationImage);
                      var contentPicker = childPage.NodeById(childPage.navigationImageLink);
                        <ul class="navImage">
                           <li><a href="@contentPicker.Url"><img src="@media.umbracoFile" alt="@childPage.Name" width="440" height="209"></a></li>
                     </ul>

Do you only store the id or the full media xml? Would be really helpful if you could post the actual error you're getting.

Jeroen

Here's the error I'm getting, does this help?

Error Loading Razor Script (file: HCR Nav) Cannot perform runtime binding on a null reference    at CallSite.Target(Closure , CallSite , Object )
  at ASP._Page_macroScripts_HCRNav_cshtml.<>c__DisplayClass53.<RenderPageAnchorWithDrop>b__52(TextWriter __razor_helper_writer) in c:\inetpub\wwwroot\macroScripts\HCRNav.cshtml:line 72
  at ASP._Page_macroScripts_HCRNav_cshtml.Execute() in c:\inetpub\wwwroot\macroScripts\HCRNav.cshtml:line 16
  at System.Web.WebPages.WebPageBase.ExecutePageHierarchy()
  at System.Web.WebPages.WebPage.ExecutePageHierarchy()
  at System.Web.WebPages.WebPageBase.ExecutePageHierarchy(WebPageContext pageContext, TextWriter writer, WebPageRenderingBase startPage)
  at umbraco.MacroEngines.RazorMacroEngine.ExecuteRazor(MacroModel macro, INode currentPage)
  at umbraco.MacroEngines.RazorMacroEngine.Execute(MacroModel macro, INode currentPage)

Hi Jeroen

Thanks for the link - not sure if this is related, but I have an issue in V6. 6.0.1 and 6.0.2. If I have an existing content node, go to properties tab, then hit save and publish, it updates to the previous time I saved and published. If I save and publish again, it updates to current date and time. Ok it is not the same as going to the media section to save - but, it seems that there could be a link as I had no issues prior to V6 with saving either media or content. I came across this when constructing a list on UpdateDate, and of course it was all over the place, double publish overcomes it. 

Hope it may be useful

G

Jeroen, how would I check to see if I'm returning the full media XML?

You can see it on the datatype. First property you can configure.

Jeroen

Okay, I'm only storing the ID. Should I change this?

Looks like any of my Razor scripts that are using the following syntax are broken. Was something changed in 6.0.2 that would effect this?

dynamic media = node.MediaById(node.thumbnailImage);
<img src="@media.umbracoFile" alt="@node.Name" width="354" height="174">

Looks like this is a bug with 6.0.2: http://issues.umbraco.org/issue/U4-1824

Yes, I encountered this bug when I upgraded from 6.0.0 to 6.0.2. As mentioned in the job you linked to I downloaded the latest version, compiled and moved the bin directory across and this has resolved the issue. I imagine there will be a 6.0.3 release packaged shortly...

Hi Paul, I actually upgraded to 6.0.3 when I saw this issue, moved the macroEngines.dll from 6.0 into the 6.0.3 installation and it "sort of" fixed the problem. Things were working fine on the bit of razor I pasted in this thread, but was throwing different errors for other DAMP and non DAMP related code.

Ran into the same issue with DAMP Razor code when upgrading to 6.0.2 (Error loading script). Updated to 6.0.3 build 10 just now and the problem disappeared. Thanks for the prompt attention, should make sure folks skip straight to 6.0.3 if upgrading from anything earlier.

is working on a reply...