Upgrade Path

7 posts, 0 answers
  1. Joe Reynolds
    Joe Reynolds avatar
    70 posts
    Member since:
    Feb 2006

    Posted 25 Sep 2007 Link to this post

    Is there an upgrade path from Editor 7.1 to Editor Promethus? If so, how much?
  2. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 25 Sep 2007 Link to this post

    1) Change the @Register declaration to use the Telerik.Web.UI namespace instead of the Telerik.WebControls.RadEditor; and you should probably use the telerik: tag prefix instead of radE:
    2) Change anywhere the Html property is used and use the Content property instead
    3) Add the HttpHandler to the web.config for the dialogs
    4) Copy any ConfigFile settings to a .skin file for the theme you are using (ConfigFiles are supposed to still work but don't seem to - it's probably a more "proper" way to use a .skin file anyway).  If using a ToolsFile, you can specify it in the .skin file.
    5) Alot of the server-side API has changed when it comes to programatically using the Image Manager / Document Manager / etc. settings so you'll need to change your code as needed.

    Other than that there isn't too many differences.  The speed increase is worth the update but you may want to wait until SP1 because there are a few bugs in certain scenarios - using within a FormView being one of them.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Valeri Hristov
    Admin
    Valeri Hristov avatar
    2252 posts

    Posted 26 Sep 2007 Link to this post

    Hi guys,

    Regarding the Html property: it was deprecated and should be replaced with Content. If you have some HTML between the RadEditor tags in your pages you will need to enclose it with <content> tags:
    - old
    <rade:radeditor>
    This is my sample content...
    </rade:radeditor>
    - new
    <telerik:radeditor>
        <content>
            This is my sample content...
        </content>
    </telerik:radeditor>

    The ImageManager and the other *Manager dialogs are also configured differently:
    - old
    <rade:radeditor imagespaths="~/images" uploadimagespaths="~/images" deleteimagespaths="~/images" />
    - new
    <telerik:radeditor>
        <imagemanager viewpaths="~/images" deletepaths="~/images" uploadpaths="~/images"  />
    </telerik:radeditor>

    and the code-behind:
    - old
    RadEditor1.ImagesPaths = new string[] { "~/images" };
    - new
    RadEditor1.ImageManager.ViewPaths = new string[] { "~/images" };

    Regarding the tools' configuration - you could use the same toolsfile.xml as RadEditor "Classic", but there will be a slight performance increase if you declare the tools in the control tag, because there will be no need to access the physical file and the whole work will be done by the page parser:
    <telerik:radeditor>
        <tools>
            <telerik:editortoolgroup>
                <telerik:editortool name="Cut" />
                <telerik:editortool name="Copy" />
                <telerik:editortool name="Paste" />
                ...
            </telerik:editortoolgroup>
            ...
        </tools>
    </telerik:radeditor>

    You could use a skin file for the different tool configurations you might have.

    The rest of the toolsfile.xml settings could also be set between the control tags, for example the font names:
    <telerik:radeditor>
        <fontnames>
            <telerik:editorfont value="Arial" />
            <telerik:editorfont value="Verdana" />
            <telerik:editorfont value="Tahoma" />
        </fontnames>
    </telerik:radeditor>

    The HttpHandler declaration is described in the following forum thread:
    http://www.telerik.com/community/forums/thread/b311D-baadth.aspx

    Information about RadSpell could be found here:
    http://www.telerik.com/community/forums/thread/b311D-baabcb.aspx

    Information about the localization:
    http://www.telerik.com/community/forums/thread/b311D-hhmmg.aspx

    Regards,
    Valeri Hristov (Senior Developer, MCSD)
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  5. Joe Reynolds
    Joe Reynolds avatar
    70 posts
    Member since:
    Feb 2006

    Posted 26 Sep 2007 Link to this post

    Thanks. However, is there an upgrade COST or must one purchase a brand new license for Promethus?
  6. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 26 Sep 2007 Link to this post

    Prometheus is currently included with the ASP.NET license.
  7. Joe Reynolds
    Joe Reynolds avatar
    70 posts
    Member since:
    Feb 2006

    Posted 01 Oct 2007 Link to this post

    >>Prometheus is currently included with the ASP.NET license.<<
    What does the above mean?

    I currently have a license for RadEditor 7.2. My question was whether I can purchase an upgrade to RadEditor Promethus, but I can't seem to get an answer.
  8. Valeri Hristov
    Admin
    Valeri Hristov avatar
    2252 posts

    Posted 02 Oct 2007 Link to this post

    Hi guys,

    If you need more details about the licensing of Prometheus I could ask our sales team, but in short (as our site says):
    If you purchase a RadControls for ASP.NET license, or if you have an active subscription for (or one that includes) RadControls for ASP.NET, you will get a matching developer license for RadControls “Prometheus” at no extra charge.

    Since Prometheus contains all controls, obviously one that have only RadEditor cannot have all controls without extra charge. Let me know if you need more information.

    All the best,
    Valeri Hristov (Senior Developer, MCSD)
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017