| 1. |
Solve : How to kill perpetual perameters following in URL? |
|
Answer» I have a page (let's call this, Page 1) that lists all the records of a particular table of a database. From each row, you can select to either edit or delete the record on that line. When I select edit, I go to another page (page 2) with a form that is dynamically filled with the content from the row I selected earlier on page 1 (parameters were PASSED in the URL to the edit page --page 2-- to load the correct record for editing). On Page 2 you make the necessary CHANGES, then press update to save them. The fields of the table are then sent to the database and they update the record. You are also sent back to the initial Page 1 to see the updated record in a new refreshed list. The problem is that the parameters that were passed initially to the edit page (page 2) are still showing and are now appended to the URL of the new page 1 (the page that I return to after the update takes place). Thus, the URL is now littered with more parameters than I need, and they are keeping the records from showing in the list as they did initially. How do I tell the edit page (page 2) to pass the necessary codes on to the database, but don't send the parameters on to the next page...sort of clean things up, so to speak? |
|