iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
I am in the process of upgrading a fairly large application that uses WebCombo 2 to use WebCombo 6. I have a page in my application that contains a WebCombo. It is the Default.aspx page in a sub-folder of the application. I'm seeing a strange behavior. When I explicitly call the page, as in http://localhost/MyApp/MyFolder/Default.aspx, the WebCombo works fine. However, when I call the page by http://localhost/MyApp/MyFolder and allow IIS to use the default page of Default.aspx, I get a script error. If I break in the script debugger, the highlighted line is:
ve4a23.open("POST",v1d568,this.Asynchronous);
The value of ve4a23 is an object with methods: abort, getAllResponseHeaders, getResponseHeader, open, send, setRequestHeader. The value of vld568 is "" and this.Asynchronous is true.
I am running this in IE8 and have tried setting ISNet.WebUI.WebCombo.v6_0_7200.RenderingMode to "Quirks" and "XHTML" without success. When I run the same page in Chrome, I do not have this issue.
After some research and experimentation, I will answer my own question.
Along with upgrading the application to use the newest WebCombo version 6, I am upgrading to using .Net 4.5 and on IIS 7.5. After some research, I came across this article on asp.net. After reading through, I ended up having to use the second workaround which is:
If the problematic HTTP modules have to run for all requests (for static files, for extensionless URLs that resolve to the DefaultDocumentModule object, for managed requests, etc.), modify the affected .aspx pages by explicitly setting the Action property of the page’s System.Web.UI.HtmlControls.HtmlForm control to a non-empty string. For example, if the default document is Default.aspx, modify the page's code to explicitly set the HtmlForm control’s Action property to "Default.aspx".
Default.aspx
Therefore, on my default page, I changed my form tag to include action="Default.aspx" and this appears to have solved the script error. The WebCombo now work whether or not Default.aspx is part of the URL request.
Glad to hear the good news, Keith.
I believe your post will help other member who has similar problem. Should you need further assistance or run into any problems regarding our controls, feel free to post it into our forum.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname
Creating your account...