Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...RadEditor custom FoldersRadEditor custom Folders
Previous
 
Next
New Post
7/29/2011 3:07 PM
 
Hi. I have a problem when I upgraded a clients site to 6.0. On 5.X.X I had configured Telerik´s Radeditor to use 4 folders as root for each specific media types (a folder for Images, another for Flash, Media, Docs, etc) and when choosing a particular media type it automatically used the corresponding folder as root.

I am trying to replicate the same config in \Providers\HtmlEditorProviders\Telerik\Config but no avail, <property name="ImagesPaths">. does not work, and the dnn 5 web.config definitions do not work either,

while using: <add name="RadEditorProvider" type="Telerik.DNN.Providers.RadEditorProvider" providerPath="~/DesktopModules/TelerikWebUI" AutoCreatePaths="true" LinksUseTabNames="false" />

To auto create the folders the site breaks.

Does anyone have a suggestion to implement this functionality under the new schema?

Thanks!

Interzoic Media www.interzoic.com
Accord LMS – Affordable, Flexible, Scalable - The Right Choice
 
New Post
7/30/2011 3:39 AM
 
If you have upgraded the site to the new dnn600 DotNetNuke.RadEditor provider - note - you need to manually do this since it is not included in the upgrade.zip package - you can then set the folders to use for each file type using the HTML Editor Manager in the Host menu.  

This module entirely replaces the settings you used to place in the web.config file and those in the old Telerik\Config  with a dynamic config based on the settings in the current HTML Editor Manager template - it does this because the new provider can be configured to use and number of different configurations based on roles or even individual pages within your site.

 Mind though Im not sure if the AutoCreatePaths setting is a current option - maybe something that needs to be added as a feature request.

Oh and just for entertainment - the new provider is NOT installed in the providers folder - instead its installed  in the  \DesktopModules\Admin\RadEditorProvider folder.

Westa




 
New Post
8/1/2011 2:20 PM
 
Thanks for the info Wes, it was indeed most useful. I followed the steps above, installed RadEditorProvider_06.00.00_Install.zip and assigned each folder to its respective Manager ("images" to Image Manager, etc)

However when opening the Image Manager from the Editor, It stills opens at the Portal Root instead of the Folder I did assign as root.

I checked the config File in DesktopModules\Admin\RadEditorProvider\ConfigFile and it looks ok, paths are defined correctly ( images/)

I tried restarting the site and Apppool in IIS and no avail, am I missing anything in the configuration? Thanks!

Interzoic Media www.interzoic.com
Accord LMS – Affordable, Flexible, Scalable - The Right Choice
 
New Post
8/1/2011 7:22 PM
 
Make sure you have changed the provider to DotNetNuke.RadEditor  - inside the HTML Editor Manager
 - by default it may still be set to use the older Telerik.RadEditor provider.

Otherwise it may need to be logged as a possible bug at support.dotnetnuke.com

Cheers

Westa

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...RadEditor custom FoldersRadEditor custom Folders


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out