Re: [WebDNA] [replacefounditems] fails

This WebDNA talk-list message is from

2009

It keeps the original formatting. numero = 104141
interpreted = N
texte = Ken, you know the drill ;-),Post your exact code (with sample values)Also, post your specs...D===================d.brooke - mobilewww.euca.us===================On Dec 9, 2009, at 11:52 PM, Kenneth Grome wrote:> I think there's some kind of bug in replacefounditems, I couldn't > get it to replace both of the values I was trying to replace, it > would only replace one -- the same one each time -- even when I > switched their positions inside the replacefounditems context.>> At first I thought it might be a problem with their positions, > that's why I switched them, but it didn't matter because only one > would get replaced and the other was ignored consistently. Then I > thought it might be a db format issue but that wasn't it either.>> Then I thought that because one of the field names was "cookie" that > might be the problem so I changed it to kookie but that still didn't > help. I checked my formvariables and all the values were being > passed as expected, the only problem was that the replacefounditems > was only replacing one of the two values it contained.>> Both values were URLed and I did not try NOT URLing them so maybe > that's the problem. I spent close to 2 hours on this just trying to > figure out what was wrong with my code, when all the time there was > nothing wrong with my code at all. It was just a screw-up in the > replacefounditems context that was causing the problem -- and I'm > sure of this because when I eventually decided to use a [replace] > context I used the exact same parameter string inside the replace > that I was using in the replacefounditems ... and both values were > replaced properly the very first time I tried it.>> Very strange. This is the first time I've seen such behavior, but > it makes me distrust using replacefounditems now.>> It would be interesting to hear if anyone else has seen > replacefounditems fail when more than one value is being replaced, > and/or if anyone has seen strange behavior like this when the values > are URLed. I just don't get it, but it leaves me thinking that this > may really be a bug in the software.>> Sincerely,> Kenneth Grome> www.KenGrome.com> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> old archives: http://dev.webdna.us/TalkListArchive/> Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 Associated Messages, from the most recent to the oldest:

Re: [WebDNA] [replacefounditems] fails (Govinda 2009)
Re: [WebDNA] [replacefounditems] fails (Bob Minor 2009)
Re: [WebDNA] [replacefounditems] fails (Kenneth Grome 2009)
Re: [WebDNA] [replacefounditems] fails (Bob Minor 2009)
Re: [WebDNA] [replacefounditems] fails (Kenneth Grome 2009)
Re: [WebDNA] [replacefounditems] fails (Donovan 2009)
[WebDNA] [replacefounditems] fails (Kenneth Grome 2009)

Ken, you know the drill ;-),Post your exact code (with sample values)Also, post your specs...D===================d.brooke - mobilewww.euca.us===================On Dec 9, 2009, at 11:52 PM, Kenneth Grome wrote:> I think there's some kind of bug in replacefounditems, I couldn't > get it to replace both of the values I was trying to replace, it > would only replace one -- the same one each time -- even when I > switched their positions inside the replacefounditems context.>> At first I thought it might be a problem with their positions, > that's why I switched them, but it didn't matter because only one > would get replaced and the other was ignored consistently. Then I > thought it might be a db format issue but that wasn't it either.>> Then I thought that because one of the field names was "cookie" that > might be the problem so I changed it to kookie but that still didn't > help. I checked my formvariables and all the values were being > passed as expected, the only problem was that the replacefounditems > was only replacing one of the two values it contained.>> Both values were URLed and I did not try NOT URLing them so maybe > that's the problem. I spent close to 2 hours on this just trying to > figure out what was wrong with my code, when all the time there was > nothing wrong with my code at all. It was just a screw-up in the > replacefounditems context that was causing the problem -- and I'm > sure of this because when I eventually decided to use a [replace] > context I used the exact same parameter string inside the replace > that I was using in the replacefounditems ... and both values were > replaced properly the very first time I tried it.>> Very strange. This is the first time I've seen such behavior, but > it makes me distrust using replacefounditems now.>> It would be interesting to hear if anyone else has seen > replacefounditems fail when more than one value is being replaced, > and/or if anyone has seen strange behavior like this when the values > are URLed. I just don't get it, but it leaves me thinking that this > may really be a bug in the software.>> Sincerely,> Kenneth Grome> www.KenGrome.com> ---------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> old archives: http://dev.webdna.us/TalkListArchive/> Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 Donovan

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] [replacefounditems] fails

2009

Top Articles:

Related Readings: