Hi we are stack up in this problem of ContentUrl or NavigateUrl on WebDatamenu/ConentUrl on WebDialog.
This two works Ok with Pages that is on Root but it always not working if the pages comes from a folder.
this is my webApp PAges Structure sample.
Root Folder:
Default.aspx ContentUrl="Default.aspx"
PopUp Folder:
Create.aspx ContentUrl="~/PopUp/Create.aspx"
this works on first execution of Default.aspx but when i go click the next webdialog with Create page ,exception says The resource cannot be found /~/PoPup/Create.aspx.. And when i click again the WebDialog with default.aspx it also says: The resource cannot be found. /PopUp/Default.aspx
How To Fix this..?
We Really need your help about this,
Thanks in Regards
----------------------------------------------------------
I already solve my the problem about
Navigation Url of Webdatamenu if Pages are in different fodlers.
I just Add temaple and Hyperlink on WebdatamenuItem.
I tried this also in contentpane but it does not work.
Hi NewbApps,
Can you try setting the Url without the "~/" at the start, for instance "Popup/Create.aspx" to see if this makes a difference. It would also be useful to know which version of .NedAdvantage you are using.
Please let me know if this helps.
Best Regards,
Petar IvanovDeveloper Support EngineerInfragistics, Inc.http://ko.infragistics.com/support
still error occurrs.. I created now a test for webdatamenu
<ig:WebDataMenu ID="WebDataMenu1" runat="server" Width="100%" Height="30px" StyleSetName="Office2010Blue">
<Items>
<ig:DataMenuItem Text="View">
<ig:DataMenuItem Text="Default" NavigateUrl="Default.aspx" Key="Default">
</ig:DataMenuItem>
</Items>
<ig:DataMenuItem Text="Transaction">
<ig:DataMenuItem Text="Create" Key="Create" NavigateUrl="Forms/Create.aspx">
<GroupSettings Orientation="Horizontal" EnableAnimation="False" />
</ig:WebDataMenu>
this is my test series:
test1 : execute menus on first load default and Create aspx - OK
test2: execute menus the second time - failed
Requested URL: /Forms/Default.aspx
Requested URL: /Forms/Forms/Create.aspx
This Example also is the same as ContentUrl on WebDialog.
Try to test it sir.. We are using version 10.3 of Infragistics asp.net control.
Thank you for the sample code.
I tested this scenario and what I can relate is that the navigateURL path is calculated based on the location of the page from which the request is made, i.e. if you have the same menu in Default and Create and you navigate to Create.aspx, the current URL looks something like : YouPage/Forms/Create.aspx. If the same menu is now present in Create.aspx and we try to navigate from this page, the value of NavigateURL is concatenated to the currentURL, hence that would explaing the generation of :
Please let me know if this is helpful.
Oops Sorry ..I forgot to mention that the Webdatamenu is in a Master Page sir.
I believe the issue in this case is caused by assigning relative URLs as opposed to absolute ones to the NavigateURL properties. You can find more information about setting URLs in master pages at:
http://www.asp.net/web-forms/tutorials/master-pages/urls-in-master-pages-vb
In this scenario I would suggest trying to set the NavigateURL properties as such:
NavigateUrl = "/YourPageBaseFolder/Default.aspx" NavigateUrl = "/YourPageBaseFolder/Forms/Create.aspx"
NavigateUrl = "/YourPageBaseFolder/Default.aspx"
NavigateUrl = "/YourPageBaseFolder/Forms/Create.aspx"
Attached is my test sample setup with absolute paths.
Thank you for replying. Please do not hesiatate to contact me with any updates or questions regarding this scenario.
Thanks Again Sir...... I will try lot of test and i will update you if i will be successful. .
When putting / before the page you need to navigate you should also put the alias name with which the site is published. For instance you need to set the navigate URLs to :
"/pageAlias/forms/Create.aspx" and "/pageAlias/Default.aspx"
Please let me know if this resolves the matter.
This one works we just only need is to add / before the page we need to navigate on Debug Mode.
/forms/Create.aspx
/Default.aspx
but when i published it on IIS error still occurs.
Thanks Again for the quick response.