BramDHoest-- This is the evil of the "include" mode of LS dynaments.
Dynaments are able to process querystrings as long as the http request is placed directly to the dynaments. Say if you have a temperature.xml dynament that takes a zipcode parameter. If a browser calls directly or via Ajax: /temperature.xml?zipcode=10000 It works fine. You get return and you can xslt the xml string onto the screen. If you attempt to incoprate the return to a div of a html page, like this: <div> <rde-dm:include content="temperature.xml?zipcode=10000" tag="notag" /> </div> Its a no-go. The only way you can get it done, is like this: <rde-dm:attribute mode="write" attribute="zipcode" source="request" value="10000" /> <div> <rde-dm:include content="temperature.xml" tag="notag" /> </div> ========== The App Portal Connector uses the "include" dynament (or a variation of it.) By the time "page 3" is included, querystrings are "sanitized out". Since your pages are not inside LS, bury parameters in request is not an option. The only viable way you can get around, is to write the "zipcode=10000" portion in a client side session cookie on Page 2 submit -- or whatever event trigger you are using, and read the same out from the cookie on Page 3 onload. Now I have to admit that you as the Portal connector users should not be forced to go through such. And somewhere neither of us know may lie a better solution. I will be happy if someone else can come forward with a better explanation or solution. But until then, you might want just take a bite on that good old cookie! Henry Lu On Wed, Oct 15, 2008 at 6:19 AM, BramDHoest <[EMAIL PROTECTED]> wrote: > > Hey, > > I have a problem implementing an external asp.Net application using > the Application Portal Connector in the include mode. > > In one case ( a contact form with a flow between 2 pages) it works > fine. The application uses the POST method to go from page 1 to page > 2. > > In my other case (flow between 3 pages) it doesn't work as expected. > The application uses the POST method to go from page 1 to page 2 AND > the GET method to go from page 2 to page 3. > > The first step works (POST) but going from page 2 to page 3 just shows > page 1 again. In the access.log file i don't see any errors showing > up. I've set the loglevel for the application portal to "DEBUG". > > Nowhere in the manual there is specified that GET method is not > supported by the Portal Connector. > > Does anyone out there has the same problem? And even more important, > found a workaround without have to change the asp.Net application > code? > > Thanks a lot!! > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
