Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
523
BUG.... UploadedFilesDirectory not working with multiview
posted

I'm using version 11.1 with the latest service release(2178) and I have the following scenario:

 

<asp:MultiView ID="MultiView1" runat="server" ActiveViewIndex="0">

        <asp:View ID="View1" runat="server">

            view 1

        </asp:View>        

        <asp:View ID="View2" runat="server">

                <ighedit:WebHtmlEditor ID="WebHtmlEditor1" runat="server" UploadedFilesDirectory="~/Archivos">

................

        </asp:View>

    </asp:MultiView>

 

And when I activate the second view and try to insert an image or anything it shows the same page in the dialog:

When the editor is outside the multiview it works fine.

 

Please I need this very urgent. Thanks in advance for the help.

  • 24497
    Verified Answer
    posted

    Hi Alejandro,

    The upload functionality of WebHtmlEditor uses private asynchronous postbacks. When that private request hits the server, then server generates content/layout which corresponds the initial state of page (the very first load). At this point the WebHtmlEditor should exist on server and it should be able to check parameters of request. If request is recognized as private-upload-request, then WebHtmlEditor supresses default response of server and returns its own response.

    If WebHtmlEditor did not exist on the very first load and it was created conditionally (like change view), then private-upload-request of that WebHtmlEditor never finds its owner and default response of server appears in pop-up window.
    For this specific configuration, application should disable upload functionality and remove corresponding buttons from toolbar of WebHtmlEditor.

    Another approach is to configure application to show WebHtmlEditor on start: set ActiveViewIndex=1 in aspx or move WebHtmlEditor in first view.

  • 37874
    posted

    Hi AlejandroPalacios,

     

    I have investigated your issue, and I have asked our engineering staff to examine this further.  To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 104648. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution.

     

    I will leave this case open and update you with any new information after the review.  You can also continue to send updates to this case at any time.

     

    You can view the status of the development issue connected to this case by selecting the "Development Issues" tab when viewing this case on the web site. 

     

    Please let me know if you need more information.