I have recreated this event using an extremely simple setup.
A Picture is worth a thousand words
See picture above.
A Picture is worth a thousand words
See picture above.
- Create FolderA and FolderB
- Put Parent page in FolderA
- Put Modal Window page in FolderB
- Evoke a modal window from FolderA - setting the content to a page in FolderB
- Perform a Post submit
404 error occurs saying FolderA\Child.aspx does not exist
8 Answers, 1 is accepted
0
Hi Jeremy,
How have you configured the action HTML attribute of the form inside the Window? I suspect the path is not correct.
Regards,
Dimo
the Telerik team
How have you configured the action HTML attribute of the form inside the Window? I suspect the path is not correct.
Regards,
Dimo
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0

Jeremy
Top achievements
Rank 1
answered on 15 Feb 2012, 07:51 PM
I haven't configured the forms post properties. The pop up is a simple aspx page.
(This answer doesn't seem the correct path. I have never had to configure .aspx page's form post attribute in 8 years of ASP, and I am not even sure how to do that since it's in a masterpage)
The popup's form tag renders as follows:
(This answer doesn't seem the correct path. I have never had to configure .aspx page's form post attribute in 8 years of ASP, and I am not even sure how to do that since it's in a masterpage)
The popup's form tag renders as follows:
<form method="post" action="MoveJob.aspx?jobId=2&_=1329326896692" id="form1">
0

Jeremy
Top achievements
Rank 1
answered on 15 Feb 2012, 11:39 PM
I am attaching a zip file with a very simple Visual Studio Web Project that shows the behavior.
0
Accepted
Hello Jeremy,
First of all, it seems that we are discussing this topic in multiple places. If you need additional information on the matter, please choose only one thread and continue posting there.
The problem is not related to the Window widget. Here are the issues that should be addressed:
1) The Window's content should be a page fragment (user control), not a complete web page with a <head> and <body> sections, etc. Otherwise the markup will become invalid. If you want to have a complete page, you should define the Window's content with a complete URL, including "http://". This will make the widget render an iframe. Currently the Child.aspx markup is injected in the <p id="window"> element.
2) I suppose you are aware that having multiple forms on the same ASP.NET page requires some additional tweaks and is generally avoided in ASP.NET. Consider changing your implementation to support this, or use an iframe, or completely remove the second form.
3) The Window is initialized from a <p> element. Although this is allowed, you will not be able to place any block elements (<div>s, <p>s, <table>s, etc) inside due to XHTML web standard restrictions.
4) The one thing that is related to the Window and should be kept in mind is that upon initialization, it is detached and moved outside the page form, before the closing </body> tag. This is to ensure it is on top of everything else. If you need to submit values from inside the Window (while not using an iframe), you should do that manually with Javascript - on button click, take all Window field values, set them as values to some hidden fields inside the main form and then submit it.
All the best,
Dimo
the Telerik team
First of all, it seems that we are discussing this topic in multiple places. If you need additional information on the matter, please choose only one thread and continue posting there.
The problem is not related to the Window widget. Here are the issues that should be addressed:
1) The Window's content should be a page fragment (user control), not a complete web page with a <head> and <body> sections, etc. Otherwise the markup will become invalid. If you want to have a complete page, you should define the Window's content with a complete URL, including "http://". This will make the widget render an iframe. Currently the Child.aspx markup is injected in the <p id="window"> element.
2) I suppose you are aware that having multiple forms on the same ASP.NET page requires some additional tweaks and is generally avoided in ASP.NET. Consider changing your implementation to support this, or use an iframe, or completely remove the second form.
3) The Window is initialized from a <p> element. Although this is allowed, you will not be able to place any block elements (<div>s, <p>s, <table>s, etc) inside due to XHTML web standard restrictions.
4) The one thing that is related to the Window and should be kept in mind is that upon initialization, it is detached and moved outside the page form, before the closing </body> tag. This is to ensure it is on top of everything else. If you need to submit values from inside the Window (while not using an iframe), you should do that manually with Javascript - on button click, take all Window field values, set them as values to some hidden fields inside the main form and then submit it.
All the best,
Dimo
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0

Jeremy
Top achievements
Rank 1
answered on 16 Feb 2012, 06:39 PM
Yes! You are right on. I did not understand how the ajax load was working. It is putting a fully formed .asx page within the <p> tag location.
OK, so can you please point me to any documentation using a window with the iframe? I have read all of the documentation and I have never seen this mentioned.
OK, so can you please point me to any documentation using a window with the iframe? I have read all of the documentation and I have never seen this mentioned.
0
Hi Jeremy,
With regard to the iframe, you only need to set a full contentUrl including the protocol, that's all.
Regards,
Dimo
the Telerik team
With regard to the iframe, you only need to set a full contentUrl including the protocol, that's all.
Regards,
Dimo
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0

Jeremy
Top achievements
Rank 1
answered on 16 Feb 2012, 08:45 PM
I am asking to learn how to fish. Reply by giving me one fish.
I do appreciate your help Dimo, you are giving me great answers, and set me on the right path. Thank you again. But I asked about documentation. I want to know how I could have known about the iframe ability. It is not mention in the documentation or in the samples.
Perhaps I am missing some documentation, or perhaps I should start looking at the source code to find the answers.
I do appreciate your help Dimo, you are giving me great answers, and set me on the right path. Thank you again. But I asked about documentation. I want to know how I could have known about the iframe ability. It is not mention in the documentation or in the samples.
Perhaps I am missing some documentation, or perhaps I should start looking at the source code to find the answers.
0
Hello Jeremy,
It's not in the documentation, we will add it. That's why I did not point you to any pages.
Greetings,
Dimo
the Telerik team
It's not in the documentation, we will add it. That's why I did not point you to any pages.
Greetings,
Dimo
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!