Don't need AssetPickers.js & HtmlEditor.js on public site

4 posts, 0 answers
  1. Cody
    Cody avatar
    1 posts
    Member since:
    Mar 2009

    Posted 30 Mar 2009 Link to this post

    We have found that on pages containing the RadEditor web part, the page references/loads AssetPickers.js and HtmlEditor.js. On our public site, we do not need these files referenced or loaded because the content will only be viewed and will never be edited, therefore we do not need the editor functionality. (We use content deployment to push content to our live site.)

    In order to reduce weight and page load time, is there a way to prevent HtmlEditor.js and AssetPickers.js from being referenced or loaded on our public facing site?

    Thanks!
  2. Rumen
    Admin
    Rumen avatar
    12851 posts

    Posted 02 Apr 2009 Link to this post

    Hello Cody,

    Unfortunately, it is not possible to exclude the AssetPickers.js and HtmlEditor.js files from the public pages. These js files are loaded automatically by MOSS and we are not aware of a way how to disable this MOSS operation.

    All the best,
    Rumen
    the Telerik team

    Check out Telerik Trainer , the state of the art learning tool for Telerik products.

  3. Declan
    Declan avatar
    1 posts
    Member since:
    Jun 2011

    Posted 29 Jun 2011 Link to this post

    Can you please confirm that it is still impossible to stop htmeditor.js from rendering on pages that are to be used by anonymous users as this creates a big problem for us with page weight?
  4. Stanimir
    Admin
    Stanimir avatar
    1653 posts

    Posted 30 Jun 2011 Link to this post

    Hi Declan,

    Currently the loading of these files is built in the server code of RadEditor for MOSS. If you want to disable the loading of these files you have a couple of options.
    1. Create a custom version of RadEditor for MOSS. In order to do this you need to request the source code in an official support ticket. In it I will explain where the code for the loading of the js files is located.
    2. Check if renaming these files will solve your problem. Most likely they are located in the Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033 folder of your MOSS server. However you should know that this will brake the OOB functionality of your MOSS site.

    Regards,
    Stanimir
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>

Back to Top