1) The javascript still remains, I've just decided to alter it, so it would fit the namingconvention of the checkboxes, which is needed, in order to access them as an array instead of single variables for each chekbox, since we have no idear how many will be checked, or how many will be provided from how many items there resides in the database, thats why it's easier to use an array structure for this.
2) The ID I'm refering to, is the uniq ID which the "categories" database-table has, which is the indent of which the checkboxes are collected into. And the uniq ID which the "items" database-table has, which is the value of the checckbox, so when the submit button get's pressed I know which category the checked checkboxes resides within, since thats the indent of the returned checkboxes array which holds any values, and I know exactly which items, since the said value it will hold is the uniq ID of the said item. So it's just a matter of fetching that item with a match in ID from the database and I have every bit of info stored according to that item, and the only parsed value is it's ID, whic is exactly what a checkbox would be able to hold as a value.
Quote:
|
I assume you are calling the "checkbox page" what I call my Order page.
|
You can call it whatever you like, My page resides in one single file, the info provided from it will dynamicaly change according to it beeing fetched without any submit button pressed, or it containing the form submission result, if it was called with a press of the submit button.
Thats the beauty of PHP, you can make the pages display different contence dictated by the way it is called.
Quote:
enter 001 into the value box in the checkbox properties on the Order page.
That way when the checkbox is checked it will be passed to the Confirmation page which will make a query based on all checkboxes that are checked and return those values?
|
It seems as if you're getting the picture, the info parsed between your "Order page" and "Confirmation page" is something which is uniq, therefor you will be able to query the database once more, with that uniq request, and expect to get exactly what the viewer wanted in return, since the "Order page" was orriginaly build with that uniq info in mind.