Re: HTML_QuickForm upgrade question/story/BC issue

I agree that it was a weird coincidence. The reason I correlate them was that (a, it worked), but b, I went to bed around midnight with things working and woke up with them not. Before I upgraded, I was going to ask the list if there were any server events that could cause this to happen -- maybe that question still holds and I wrote it off too quickly when the upgrade solved things. Meaning, was there anything the administrator could have done in the wee hours to cause this mal-function? The whole thing was definitely weird. To upgrade first I did pear list-upgrades. It showed upgrades as HTML_Quickform, PEAR.php, and a few xml packages, which I'm not using. I tried pear upgrade HTML_QuickForm. This gave me an error, which I forget (sorry). Then I tried pear upgrade-all, which worked, and, as noted also solved the problem. s. Bertrand Mansion wrote: > Sarah Gray wrote: > > >Needless to say, not a happy moment -- I troubleshot a bit and finally > >tried upgrading HTML_QuickForm from 3.2.2 to 3.2.3, which I had been > >going to do anyway. Voila, everything worked swimmingly again (posts, > >errors, db connections all intact). Which is great, I'm set. But -- my > >question is -- why did 3.2.2 stop working as expected? Is that usual > >behaviour when a package upgrades? I would think that existing packages > >shouldn't be affected by a new release. What changed? Did anyone else > >have this experience? > > Your problem is probably not related to the fact there there has been a new > release :) I am glad the upgrade solved the problems (sometimes it is the > opposite) but I think that's a coincidence. > > Just being curious, which command did you use to upgrade QuickForm ? > > Bertrand Mansion > Mamasam