GetFileManagerBrowserUrl Replacement in 7?

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

Home / Forums / Legacy forums / Episerver 7 CMS /

GetFileManagerBrowserUrl Replacement in 7?

Mark A

Vote:

expand_less 0 expand_more

Hello,

Does anyone know what should be used in Version 7 to replace EPiServer.Editor.HtmlEditor.GetFileManagerBrowserUrl from Version 6?

I've not found anything obvious yet.

Mark

#69755

Apr 04, 2013 17:17

Mark A

Vote:

expand_less 0 expand_more

Anyone know anything about this?

#69998

Apr 10, 2013 17:37

Per Hemmingson

Vote:

expand_less 0 expand_more

+1.

Any news on this?

#85808

May 06, 2014 10:09

Marija Jemuovic

Vote:

expand_less 0 expand_more

Hey guys, I've just stumbled upon PropertyLinkCollectionEditingControl that uses this method:

    protected string GetFileManagerUrl()
    {
      IContentSource contentSource = this.Page as IContentSource;
      if (contentSource == null || !LegacyResourceableExtensions.IsLegacyResourceable(contentSource.CurrentContent))
        return string.Empty;
      long legcayContentFolderId = LegacyResourceableExtensions.GetLegcayContentFolderID(contentSource.CurrentContent);
      return PropertyLinkCollectionEditControl.GetFileManagerBrowserUrl(contentSource.CurrentContent.ContentLink ?? ContentReference.EmptyReference, contentSource.CurrentContent.ParentLink, legcayContentFolderId);
    }

Not sure if this helps you, but you can check it out with dotPeek or Reflector, might be that you will find something useful for yourselves.

#85834

May 06, 2014 16:40

error This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.