Viktor, thanks for your reply ! 

Viktor Snezhko"]this.WebHtmlEditor1.Toolbar.Items.RemoveAt(1);
BaseChildControl button = this.WebHtmlEditor1.FindByKeyOrAction("Bold");
if(button != null)
   this.WebHtmlEditor1.Toolbar.Items.Remove(button);

 This made the trick.

Viktor Snezhko"]Note: any uploaded functionality (images, media, flash, etc.) is available only when editor is created on initial load of page (like aspx), otherwise, while upload request, the instance of control will not be found and server may generate response with default page. So, situation when editor is created on a specific event (like button click, wizard-view event, etc) will destroy upload functionality. No fix is possible.

I'm hiding and showing the WebHtmlEditor using a MultiView control, so every time it shows a popup it will show the current page. Now, If I get the WebHtmlEditor control out of the MultiView it will work fine.......

 It is disappointing no to be able to use the WebHtmlEditor in a MultiView control, or WizardControl. So (correct me if I'm wrong) it looks like you need to dedicate an entire page to the WebHtmlEditor control so it can work properly, since you cannot hide it and show it dynamically and expect the multimedia functionality to work.

 Is this "Note" somewhere on the documentation? or on a KB article? I guess I missed it. I kept trying to make it work assuming it was a bug-free control.

Again, thanks for your reply.

As I said, the condition for upload is create and show editor (Visible != false) on initial load (this.IsPostBack == false). So, if WebHtmlEditor raises its async request for upload data, the server should be able to recreate instance of editor. Later on, if view/wizard hides/shows editor, then it should be ok, but on the very first load, editor should be visible. If for your application it means a "stand alone dedicated page", then yes,- it is prerequisite for upload functionality.

Regards,
Viktor
Infragistics web team

Viktor Snezhko"]

As I said, the condition for upload is create and show editor (Visible != false) on initial load (this.IsPostBack == false). So, if WebHtmlEditor raises its async request for upload data, the server should be able to recreate instance of editor. Later on, if view/wizard hides/shows editor, then it should be ok, but on the very first load, editor should be visible.

Is there a workaround to use the WebHtmlEditor in FormView / MultiView Etc ? Why is it that the instance can't be recreated if put in a FormView ?

I really would like to use it WebHtmlEdit as a control instead of dedicating a page to it.

Thanks in advance

To get upload image the WebHtmlEditor uses its own internal async postback. When server gets that request, then it has state similar to the very first load of page. If WebHtmlEditor is found (and created), then WebHtmlEditor supresses default response of server and creates its own special response stream which can be interpret on client by WebHtmlEditor. Otherwise, server generates its default response stream and image-upload fails. There is no work around to get around that limitation.

Some users ask for a workaround to use the image insert in a wizard. This worked for me. I hope there is an easier way. I had the htmleditor on the second step of my wizard.

in the Page_Load of my page:

if

 (!IsPostBack) { .....

// Load form for second step and move directly to second step

LoadCourseSlideForm();

wzdCourseBuilder.MoveTo(wzdCourseBuilderStep2);

On the user control of my second step, which hosts the html editor:

protected void Page_Load(object sender, EventArgs e){

String.Format("/TiresCourseFiles/CourseFiles/CourseId_{0}"

, _psCourseId);}

if (!IsPostBack){

// So the webHtmlEditor's insertImage button will work

if (!txtCourseSlideHtml.IsPostbackFromUpload){

// Call  public method on the page that will move back to step 1

.Page)).MoveToStepOne();