Re: QF: setDefaults() weird behaviour

On Fri, 19 Nov 2004 16:23:51 +0100, Toni <toni@pangea.org> wrote: > Hi, > > Yes, the values are really saved, but ... > > I had only tried with firefox (1.0) and didn't work, but now I'm trying > with konkeror (3.3.1) and works fine! > > Someone knows why? > Well, if you're clicking back in your browser then it could just be saving the old page. This is something that changes between browsers. If you navigate back to that page (click on a link to it, don't use back) then is it correct? If it's right when you refresh, then it's probably a caced copy. I would suggest using "no-cache" headers and HTML code to stop the browser from caching old pages. > Thankyou all. > > El vie, 19-11-2004 a las 17:56 +0300, Alexey Borzov escribió: > > > > Hi, > > > > Toni wrote: > > > I have developed an application to maintain a database of educational > > > materials. > > > I have a php file to update the registers in the database, which is a > > > QFC. > > > When I visit the page the form is displayed with the fields filled with > > > data in the db. That's ok. > > > I change the "language" field (select) to a different value > > > [spanish->english] and submit the form. Ok. > > > The process function save the values in the database and show me a link > > > to another page. Ok. > > > I visit again the update form and the selected value in the language > > > field is the old one [spanish]. Not OK! > > > > > > Why get I this value? > > > > No idea, I briefly looked at your code and there are no obvious QFC-related > > problems. Did you check whether the new value is *really* saved to the database? > > > -- Justin Patrin