Page Variable in HTML page

[Leonw43]

Hi, I am trying to display some data in an iFrame that I've passed through a URL (e.g. www.website.com?service={service}) - in a .a5w page, the data is stored in the variables within the URL, but I can't seem to get the variables to display the data in the a5w page. EDIT: Can get the variables to display, but the placeholders "{ }" don't seem to work on the iFrame URL property in my Dialog2. Is there any way to do this?

Thanks,
Leon.

[satyanarayana]

Re: Page Variable in HTML page

In xbasic
======
service=Extract_String(Request.Query_String, "service=","&")


In URL
=====
www.website.com?service={service}&


In javascript write xbasic variable..
===========================
var service='<%a5 ?service%>';

[Leonw43]

Re: Page Variable in HTML page

Thanks for the help - your code works but the result is just "{service}" appearing on the page, instead of the actual value. Perhaps the Dialog2 iFrame URL property doesn't support placeholders or something?

[Peter.Greulich]

Re: Page Variable in HTML page

Session Variables
Session variables can only be strings (type "C"). While this limitation has always been implied, it has not always been strictly enforced, so legacy code may store other data types as session variables. Going forward, this will not be possible, as it will break session persistence.

Session Variables cannot be created directly from a request query string or POST body. This negates the need to use "protected" session variables, as all session variables are now effectively "protected". In order to create a session variable, you must execute A5W code to read the request variable and create or set the session variable. A request for a URL such as http://localhost/index.a5w?session.name=John (external link) will not create a session variable session.name as it previously would have. Instead, it will create a request variable which may be accessed as Request.Variables.session.name during the lifetime of that request only.

See http://wiki.alphasoftware.com/Applic...hanges+for+V11

[Steve Wood]

Re: Page Variable in HTML page

Leon,

I confirmed that the dialog2 IFrame URL field does not support parameters. Otherwise, what you tried in your first post is the right way to do it.

However, it is easy to do what you want.

First, delete your IFrame control and add a Static Text control. Leave the Static text value empty. Instead, enter something in the Calculated Field Expression property similar to this:

'<iframe src="http://www.alphatogo.com/test.a5w?test='+emailAddress+'"></iframe>'

This example will put alphatogo.com in an IFrame pointing to the page named test.a5w with a parameter named "test" and a value populated by a dialog control named emailaddress. EmailAddress MUST have a value when the dialog is initiated.

One reason this was hard to figure out is that everyone forgets that all of this is just HTML and Javascript working in a browser. Alpha provides an IFrame control, but it is just as easy to create on in a static text field.

[kkfin]

Re: Page Variable in HTML page

There is an interesting little detail using parameters in Url.

When you write parameters like this: http://mydomain.com?value=1 there in fact happens redirecting to the default index page (configured in Was).
(syntax similar like Leons example in post #1

Same happens if you use parameters like this: http://mydomain.com/test?value=1. Was redirects to the default index page located in test sub folder (configured in Was)

Using this syntax at the moment means that parameters are not seen by the post/get page.

This behavior has been changed in future build of Was

This means these two syntax are handled same way.

http://mydomain.com/test?value=1 is equal with this syntax http://mydomain.com/test/?value=1

[Steve Wood]

Re: Page Variable in HTML page

This syntax works in the current version of V11:

http://mydomain.com/test?value=1

This creates a page variable named test with a value of 1 on index.a5w, my default page.

[kkfin]

Re: Page Variable in HTML page

I have different results.

What is the latest build you use for testing?

Is it possible that you are in fact testing syntax: http://mydomain.com/test/?value=1