Master Detail Pages

in the go to detail page
I have UNCHECK the checkbox with the option:
Pass existing parameters: URL parameters.

And I have CHECKED the checkbox with the option:
FORM parameters.

It works.

I solve one!!! YEAH! :D

Sorry for the joke, I have a special way of doing not funny jokes. :)

I think I shoud have a new post, but once this question is related is better to do it here.

To have the possibility of using the back browser button, I have change all the methods here to $_GET but I cannot get the detail page to work :S

Here is the link:
http://www.cantinho.org/admin/cantinho/encontrar_animal_5.php

This is a case to say: "I don't GET it" :s

Thanks.

Thanks!!! :)

"oicram" <webforumsuser@macromedia.com> wrote in message
news:fcdmim$9oi$1@forums.macromedia.com...
> Was last question and then I close this treat with your answer, is not
> more secure to use $_POST instead of $_GET or its a mith?
>
> thanks

It's a myth, it may seem a little more difficult to craft a tailored
malicious request than changing some parameters in the address bar but in
reality it isn't.
You should never rely on user input for critical variables, do not use
hidden form fields for things like the user_id in a session variable,
because they will be able to change it.

NEVER try to do security trough obscurity
http://en.wikipedia.org/wiki/Security_through_obscurity

Was last question and then I close this threat with your answer, is not more secure to use $_POST instead of $_GET or its a mith?

thanks

"oicram" <webforumsuser@macromedia.com> wrote in message
news:fcdhlj$4os$1@forums.macromedia.com...
> Joris, I have two versions, Sorry for the miss confusion.
>
>
> In the other post, I'm using another approach and I don't need to use the
> back
> button in there as its obvious (I think) for the user that he must click
> on
> show/hide and not (go back).
>
>
>
> In this post, I'm using this approach:
> "the javascript/div approach and use a second
> recordset to display the detail data filtered by an id that you pass via
> the
> "Go to detail page" server behavior as I originally suggested."
>
> And is in this aproach that I'm asking for a functional backbutton.
> Now I get an error page in IE saying:
> "Webpage has expired
>
> Most likely cause:
> The local copy of this webpage is out of date, and the website requires
> that
> you download it again. ..."
>
> and Firefox a warning window.
> The page you are trying to view contains POSTDATA that has expired from
> cache.
> If you resend the data, any action the form carried out will be repeated.
> To resend the data, click, OK. Otherwise, click Cancel.
>
>
> Sorry again, and thanks again for your help.


This is the result of using post variables, since these variables aren't
contained in the url, newer browsers try to warn you before resubmitting.
Using the GET method the sorm-elements will be encoded in the url and that
url can be saved in history. So try switching your form to method
get/default and replacing all $_POST with $_GET.

Joris

Joris, I have two versions, Sorry for the miss confusion.


In the other post, I'm using another approach and I don't need to use the back button in there as its obvious (I think) for the user that he must click on show/hide and not (go back).



In this post, I'm using this approach:
"the javascript/div approach and use a second
recordset to display the detail data filtered by an id that you pass via the
"Go to detail page" server behavior as I originally suggested."

And is in this aproach that I'm asking for a functional backbutton.
Now I get an error page in IE saying:
"Webpage has expired

Most likely cause:
The local copy of this webpage is out of date, and the website requires that you download it again. ..."

and Firefox a warning window.
The page you are trying to view contains POSTDATA that has expired from cache.
If you resend the data, any action the form carried out will be repeated.
To resend the data, click, OK. Otherwise, click Cancel.


Sorry again, and thanks again for your help.

"oicram" <webforumsuser@macromedia.com> wrote in message
news:fccb8e$o0r$1@forums.macromedia.com...
> >You apply a Go to Detail Page serverbehavior to the content from the
> >Master
> >(list) recordset, then you filter the second recordset with the parameter
> >from the Go to Detail Page serverbehavior, and apply a "Show if recordset
> >not empty" to the Detail content
>
> Perfect. Thanks. The only problem with this approach is the use of back
> button, how can we allow the use of the back button in cases like this?
>
> Thanks.

Well.... you don't, as you're not actually navigating to another page, just
showing and hiding certains regions in the same page. That's why the
standard master-detail functionality uses two separate pages.

However you can eliminate the javascript/div approach and use a second
recordset to display the detail data filtered by an id that you pass via the
"Go to detail page" server behavior as I originally suggested.


follow the steps outlined in
Building master and detail pages (all servers)
http://livedocs.adobe.com/en_US/Dreamweaver/9.0/help.html?content=WSc78c5058ca073340dcda9110b1f693f21-79e0.html

but make your master page and detail page the same.

Joris

>You apply a Go to Detail Page serverbehavior to the content from the Master
>(list) recordset, then you filter the second recordset with the parameter
>from the Go to Detail Page serverbehavior, and apply a "Show if recordset
>not empty" to the Detail content

Perfect. Thanks. The only problem with this approach is the use of back button, how can we allow the use of the back button in cases like this?

Thanks.

"oicram" <webforumsuser@macromedia.com> wrote in message
news:fcbq4m$5t3$1@forums.macromedia.com...
> Thanks.
> You are giving me hope. :)
>
> But the link that you have give me talks only in Datasets. I don't have
> any.

That link assumed you wanted to do it all in spry

> Where can I found similar information regarding Recordsets? And the work
> between them?

There is no info about creating recordset based master/detail functionality
in a single page, dreamweaver manuals assume that "master" and "detail" are
separate pages, the process remains the same with the exception of creating
a separate detail page.
> I have know an extension that translates a Recorset into XML, and HAND
> ways to
> do this. But I don't want to translate to XML. I only want to use spry
> effects
> (like show hide) to "play" with my dynamic information bring by the
> recorset.
> I.E. Spry Effects inside a repeat region. Problem: I get only the first
> record
> of the repeat region to work.

It probably has something to do with the code, javascripts tend to use id's
to reference objects in the page, and id's should be unique, so when
repeating content that has id's that are referenced my javascripts you
should make sure you make sure those id's are in fact unique.

> So I think, for now, that they are not friends. And I have no idea if I
> can
> make them friends.

It may be better to repost the spry part of your question in the SPRY group
news://forums.macromedia.com/macromedia.labs.spry_framework_for_ajax_prerelease

please include code as seen by your browser (view source) because spry only
operates on the client-side.

> Thanks for your time once again, hope you can clarify something here.

I think the main confusion is between server-side and client-side code, the
PHP/ASP etc code runs on your webserver and produces HTML output, that code
is never seen or executed by your browser, the javascript (spry) on the
other hand runs only in your browser, not on the server.

Joris