Bob did you ever get this figured out? 

I'm experiencing the same problem. Did you ever find a solution?

Hello,

it's been awhile but I think the following code fixed the issue:

I registered a route in the initialization module of my provider (IInitializableModule.Initialize)

        public void Initialize(InitializationEngine context)
        {
            var settings = context.Locate.Advanced.GetInstance<IBynderSettings>();
            var bynderRoot = EnsureCreateProviderRoot(context, settings);

            EnsureProvider(context, bynderRoot);

            EnsureRoutes(bynderRoot);
        }

        private void EnsureRoutes(IContent bynderRoot)
        {
            // Since we have our structure outside asset root we registera custom route for it
            // and remove the language segment
            // -> disabled for the moment, we want content to be localizable
            //RouteTable.Routes.MapContentRoute(
            //name: "BynderMedia",
            //    url: "bynder/{node}/{partial}/{action}",
            //    defaults: new { action = "index" },
            //    contentRootResolver: (s) => bynderRoot.ContentLink);

            // EPiServer UI needs the language segment
            RouteTable.Routes.MapContentRoute(
                name: "BynderMediaEdit",
                url: CmsHomePath + "bynder/{language}/{medianodeedit}/{partial}/{action}",
                defaults: new { action = "index" },
                contentRootResolver: (s) => bynderRoot.ContentLink);
        }

        private static string CmsHomePath
        {
            get
            {
                var cmsContentPath = VirtualPathUtility.AppendTrailingSlash(EPiServer.Shell.Paths.ToResource("CMS", "Content"));
                return VirtualPathUtilityEx.ToAppRelative(cmsContentPath).Substring(1);
            }
        }

Sorry for the slow response, and not updating my post in the first place...

bob

Thanks for the response Bob!
I tried your solution but didn't get it to work (even though it seems like it should). My solution instead were to change the content provider root from the root folder and instead use the global asset root. The content provider root folder were then visible in the media asset folder structure as well, but that wasn't a big problem for me.

Hi Bob, Drew.

What Bynder package you had implemented?

We use v. 3.0.0 with current CMS 11 and COmmerce 13 implementation.

Now we upgrading to CMS 12 and Commerce 14 and use Bynder package 5.0.1

In both implementation the only issue with Bynder assets we have is in the commerce area in 'assets' for products.

We are missing the thambnail image for assigned bynder asset. Did you have this issue and how did you resolve it?

Thank you for your time.

Irina