Re: [WebDNA] fastcgi 7+ & [cart]?

This WebDNA talk-list message is from

2010

It keeps the original formatting. numero = 105498
interpreted = N
texte = In case anyone is wondering why I think it's important.=20Let's say I am deleting a record. I build in a=20confirmation step. So the first round goes like this=20[thisurl]?task=3Dkillrecord&ID=3D[id] which brings up a=20message where I=A0put a "Yes Delete" link which goes like=20this:=A0[thisurl]?task=3Dkillconfirmed&ID=3D[id]So by continually appending the variables messes things up=20with two values of [task]; or if I use different=20variables, say killrecord=3Dt and killconfirmed=3Dt, for the=20action, it would repeat the first step. Also would be=20problematic in the shownext links which would keep piling=20them on.But being able to include them would be helpful in some=20cases.TerryOn Tue, 6 Jul 2010 12:10:34 -0400 christophe.billiottet@webdna.us wrote:> Sounds interesting. OK, we will do this.>=20> - chris>=20> On Jul 6, 2010, at 11:53, Kenneth Grome wrote:>=20>>> In my opinion, the new behaviour could be a "plus" when=20>>>we have to recover variables and it is pretty easy to=20>>>strip the extra data out with a small function, this is=20>>>why i would be inclined towards keeping the new=20>>>behaviour. For instance, and if needed, it will make=20>>>possible to use the "back" button from the browser, or=20>>>not -your choice- while the older behaviour does not.>>=20>> I agree with you Chris when you say that it's nice to=20>>have a tag that includes the variables. After all, it's=20>>a pain in the butt to have to code them in separately.=20>> But having *two tags* that we can choose from seems like=20>>the ideal alternative to me.>>=20>> So here's a thought:>>=20>> Why not keep the old [thisurl] behavior, then add a new=20>>[thisurlplus] tag that contains the variables. This=20>>gives us the best of both worlds -- backward=20>>compatibility as well as a new tag to make including the=20>>variables easier.>>=20>> :)>>=20>> Sincerely,>> Kenneth Grome>>=20>>=20>>=20>> --------------------------------------------------------->> This message is sent to you because you are subscribed=20>>to>> the mailing list .>> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us>=20> ---------------------------------------------------------> This message is sent to you because you are subscribed=20>to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us=A0 Associated Messages, from the most recent to the oldest:

In case anyone is wondering why I think it's important.=20Let's say I am deleting a record. I build in a=20confirmation step. So the first round goes like this=20[thisurl]?task=3Dkillrecord&ID=3D[id] which brings up a=20message where I=A0put a "Yes Delete" link which goes like=20this:=A0[thisurl]?task=3Dkillconfirmed&ID=3D[id]So by continually appending the variables messes things up=20with two values of [task]; or if I use different=20variables, say killrecord=3Dt and killconfirmed=3Dt, for the=20action, it would repeat the first step. Also would be=20problematic in the shownext links which would keep piling=20them on.But being able to include them would be helpful in some=20cases.TerryOn Tue, 6 Jul 2010 12:10:34 -0400 christophe.billiottet@webdna.us wrote:> Sounds interesting. OK, we will do this.>=20> - chris>=20> On Jul 6, 2010, at 11:53, Kenneth Grome wrote:>=20>>> In my opinion, the new behaviour could be a "plus" when=20>>>we have to recover variables and it is pretty easy to=20>>>strip the extra data out with a small function, this is=20>>>why i would be inclined towards keeping the new=20>>>behaviour. For instance, and if needed, it will make=20>>>possible to use the "back" button from the browser, or=20>>>not -your choice- while the older behaviour does not.>>=20>> I agree with you Chris when you say that it's nice to=20>>have a tag that includes the variables. After all, it's=20>>a pain in the butt to have to code them in separately.=20>> But having *two tags* that we can choose from seems like=20>>the ideal alternative to me.>>=20>> So here's a thought:>>=20>> Why not keep the old [thisurl] behavior, then add a new=20>>[thisurlplus] tag that contains the variables. This=20>>gives us the best of both worlds -- backward=20>>compatibility as well as a new tag to make including the=20>>variables easier.>>=20>> :)>>=20>> Sincerely,>> Kenneth Grome>>=20>>=20>>=20>> --------------------------------------------------------->> This message is sent to you because you are subscribed=20>>to>> the mailing list .>> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us>=20> ---------------------------------------------------------> This message is sent to you because you are subscribed=20>to> the mailing list .> To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us> Bug Reporting: support@webdna.us=A0 "Terry Wilson"

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] fastcgi 7+ & [cart]?

2010

Top Articles:

Related Readings: