Hi Lee,

Thanks for your reply, that's clear.

Great package, I use it a lot!

Thanks,

John

Hey JLon,

No news from me, but there is a GitHub repo that has a Courier provider for Nested Content (and DocTypeGridEditor).

https://github.com/display/Umbraco-courier-providers

I haven't tried or tested it though, so I can't vouch for it. If it does work, please do let me know! :-)

I'd still love some community support on this one - it's a pretty heavy burden for a package developer to manage all those scenarios.

Cheers,
- Lee

Hello Lee,

Because of some problems with different assembly versions I copied the code for the NestedContentDataResolverProvider into my project, and had it reference the assemblies I my project. I subsequently had a problem due to DocTypes in the various environments with the same alias but apparently different guids. After changing the code for the DocType lookup to use only the alias it seems to work.

Hi John,

Great to hear that you've got it working! :-)

It think it would be useful for others to post your code-fix somewhere?

Either as a pull-request on their GitHub repo?
https://github.com/display/Umbraco-courier-providers

or if you're unsure about GitHub, etc, then just post it on this thread as a reply?

Cheers,
- Lee

Hey JLon,

I finally got around to trying out the courier resolver for Nested Content earlier this week. I found a couple of issue with it and fixed accordingly (as all good open-source citizens should do) :-D

I made a fork of the original project, the source-code is here:
https://github.com/leekelleher/umbraco-courier-dataresolvers

I haven't made a package for it yet... so will need Visual Studio to build the code.

I hope this helps?

Cheers,
- Lee

Yes, build the VS project, copy the .dll (and .pdb if you want debugging info) into your website's /bin folder... and that's it. Courier will pick it up and do the rest.

which dll?

Hi Mike,

It didn't work, or you think it won't work?

I'm using NCs within DTGEs, which are resolving fine on our environments.

Let me know what's not working, I'm happy to give pointers.

Cheers,
- Lee

Hi Mike,

Do you know if the code was compiled from my repo or Dis/Play's repo?

...and what types of property-editors aren't resolving?

My current project uses some more complex property-editors, which works fine (for us). Of course, I can't offer advice on things I don't know about :-)

Cheers,
- Lee

Textarea inside an NC, yes ... but the question confuses me, as a textarea typically wouldn't need to be resolved by Courier - there are no IDs that need resolving as GUIDs, nor any dependencies (apart from the textarea DataType - if it's a custom one).

What's the exact issue? Isn't the data being transferred or restored? Does the CourierTraceLog.txt give you any clues?

Hi Lee. No - data is not going over.

The main culprits I can see are textarea and multi node tree picker. These are both in scenarios where are using the grid and have a doc type grid editor with a nested content inside the doc type grid editor which has them on.

This is on UaaS though.

I'm trying to figure out if I can notice a pattern and maybe need to run some more tests. Any ideas? It doesn't seem to make much sense.

I'll try and set up a site to demonstrate. You okay if I add you to a dummy UaaS project so you can see what I mean?

Is other content transferring okay? My gut feeling is that something else is at play. We're using this Courier resolver on UaaS and having no issues with DTGE/NC data.

I'd recommend contacting UaaS support on this issue.

Thanks Lee. Will do once I've managed to figure out a repeatable example.

Thanks again! Will have to buy you a drink at ukfest!

OK, cool.

I kept getting that error, where there ShouldRun was throwing an exception because the JObject didn't have a value... I thought it was data from other grid cells, but I couldn't figure out how to code a check against it.

This is the code, I ended up doing the evil try/catch.log anti-pattern around it...

https://github.com/leekelleher/umbraco-courier-dataresolvers/blob/develop/src/Our.Umbraco.Courier.DataResolvers/GridCellDataResolvers/DocTypeGridEditorGridCellResolverProvider.cs#L24-L35

But all the ShouldRun is doing is checking if the data-resolver should process. So if the JObject has "dtgeContentTypeAlias" and "value" properties then it should continue the process, otherwise it wont. Courier should still transfer the un-resolved values (to my knowledge).

The source-code is there, might be better to debug against it directly?

Jumping in here -- I'm getting the same Newton.Json.Linq.JValue error trying to push content from "staging" to "live" on our umbraco sites.

I posted details here and haven't been able to solve the issue.

https://our.umbraco.org/forum/using-umbraco-and-getting-started/80199-error-when-trying-to-transfer-with-courier

Hi Martin,

I haven't offered a binary distribution of the NestedContent Courier data-resolver, as I felt it would bind me to supporting it - which I'm presently not able to do, sorry.

The source-code is available for a developer to compile it themselves, which means they at least have some level of responsibility in making sure the code works correctly for their own clients/solutions.

My advise would be to contact Umbraco Cloud support team, ask them if they can provide a binary copy of the DLL. They are willing to support popular community packages on Umbraco Cloud.

I hope this helps?

Cheers,
- Lee

Hi Martin,

The great news is, since my last reply, Umbraco HQ/Cloud have started a collaboration project to support popular packages...

https://github.com/umbraco/Umbraco.Courier.Contrib

That takes a lot of pressure off me :-)

As for your question about DTGE + NC... that should work (at least I have that scenario working / deploying).

One question is, are you using compositions for the doctypes? As I've heard there might be a bug around that in the resolvers.

Cheers,
- Lee

Is the Media picker the default Umbraco one? That should work.

With the "url picker" one... is that from a separate package? It's worth checking if that has its own Courier resolver.

(Yep, it starts to get into deeper levels of dependency - the kind of stuff I had a headache to support) :-)

It's worth checking your config/courier.config file, to make sure that the property-editor aliases are correct in the <mediaPickers> section.

Cheers,
- Lee