Browsing records - Variable trouble

dancahill

I know this is a regular topic on the board and I have read through some other posts on the subject but can't work out how to do what I need to do.

I start of with a form whose variables are posted to another page. This page accesses the variables through _POST etc.

I have a funtion on this receiving page to enable results to be browsed - normal sort of stuff incrementing offset values & then printing out a previous & next link at the bottom of the page.

When you click on the NEXT link it goes back to the same page but obviously now as I have the variables accessed by POST, these variables are no longer available the second time round thus giving obvious errors.

I can work out how I would do this if I could encode the variables within the URL link but the query strings are potentially quite long & I prefer not to encode search strings in URLs anyway.

How can I make these variables available to the script second time round, I was thinking of having to register them as session variables but this is not the best way I'm sure.

Anyone that can point me in the right direction - I'll be very happy.

releasedj

The only way you can have a text link send info by POST is to have all your variables in a form, and a text link which uses javascript to submit it, i.e.:

<form method="post" name="prev_link">
<input type="hidden" name="page" value="1">
...... etc.
</form>
<a href="document.prev_link.submit();">Previous</a>

.. and the same for your 'Next' link.

A posibility for passing through all the variable that you want is to:
a. loop through them all, echoing <input type=hidden> for all of them.
b. serialize your array, put the serialized code into a <input> tag and the unserialize when you load the page.

I hope this helps,

Kelvin

[deleted]

and write a simple http post request to post your data
unfortunately i can't find the script i use, but if you can't find something usefull on php.resourceindex.com or hotscripts.com
i'll find it for you 🙂

dancahill

Thanks for your comments guys. In the end I went down the route of checking if their were any POST_VARS & then registering them as session variables and on subsequent browses, called the session variables.

Thanks again,

Dan.