Re: [WebDNA] Triggers not working
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107785
interpreted = N
texte = A new SB with new triggers does not work either. The db is Ok because it can be read and written to. On 09/12/2011, at 9:23 AM, Rob wrote: > The only thing I can think of, other then a corrupted db, which is = more then likely, is a problem with ExecuteURL, User, or Pass.=20 >=20 > When you try to execute does it write anything to WasGood in the = Triggers.db? >=20 > Rob >=20 >=20 > On Dec 8, 2011, at 4:14 PM, Govinda wrote: >=20 >>=20 >>> Govinda >>>=20 >>> Triggers are working at the top admin level, just not at sandbox = level. >>=20 >> The only triggers I am using are on the sandbox level, and they work = since years, so have hope! >>=20 >> One clients tells me that her triggers db "gets corrupted from time = to time".. and that the "host has to rebuild it" (IIRC) ... but I was = not put to that task, so I am unsure what that means. >>=20 >> -G >>=20 >>>=20 >>>=20 >>> On 09/12/2011, at 9:07 AM, Govinda wrote: >>>=20 >>>>=20 >>>>> Any preference files that I should check ? >>>>>=20 >>>>> On 07/12/2011, at 9:41 AM, Stuart Tremain wrote: >>>>>=20 >>>>>> I recently had to move servers due to a hardware issue and now = have a problem that triggers at a SANDBOX level are not working. >>>>>>=20 >>>>>> Triggers at the top admin level work OK. >>>>>>=20 >>>>>> I created a new sandbox and tried the triggers but without = success. >>>>>>=20 >>>>>> The same triggers when added to the admin level work OK. >>>>>>=20 >>>>>> Server is Windows 2003 with WebDNA 6.2 >>>>>>=20 >>>>>> Permissions ? >>>>>>=20 >>>>>> Paths ? >>>>>>=20 >>>>>> I can not find anything in any prefs file that may point me in = the right direction. >>>>>>=20 >>>>>> I have tried turning triggers on and off. >>>>>>=20 >>>>>> Adding new triggers. >>>>>>=20 >>>>>> The triggers.db is loading but they are not firing. >>>>>>=20 >>>>>> Any ideas why they may not be working at SANDBOX = level.--------------------------------------------------------- >>>>=20 >>>> If still no luck with Rob's suggestion, then I would suggest just = seeing if you can get a plain NEW vanilla install to send triggers. I = mean clearly triggers are working on loads of running sites (including = on 2 of mine); just establish that you can make a trigger work *in = general*.. and then somehow it will/can shed light on why your other = particular situation is different (misbehaving). >>>>=20 >>>> -G >>>>=20 >>>>=20 >>>> --------------------------------------------------------- >>>> 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 >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> 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 >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> 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 >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > 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 > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
A new SB with new triggers does not work either. The db is Ok because it can be read and written to. On 09/12/2011, at 9:23 AM, Rob wrote: > The only thing I can think of, other then a corrupted db, which is = more then likely, is a problem with ExecuteURL, User, or Pass.=20 >=20 > When you try to execute does it write anything to WasGood in the = triggers.db? >=20 > Rob >=20 >=20 > On Dec 8, 2011, at 4:14 PM, Govinda wrote: >=20 >>=20 >>> Govinda >>>=20 >>> triggers are working at the top admin level, just not at sandbox = level. >>=20 >> The only triggers I am using are on the sandbox level, and they work = since years, so have hope! >>=20 >> One clients tells me that her triggers db "gets corrupted from time = to time".. and that the "host has to rebuild it" (IIRC) ... but I was = not put to that task, so I am unsure what that means. >>=20 >> -G >>=20 >>>=20 >>>=20 >>> On 09/12/2011, at 9:07 AM, Govinda wrote: >>>=20 >>>>=20 >>>>> Any preference files that I should check ? >>>>>=20 >>>>> On 07/12/2011, at 9:41 AM, Stuart Tremain wrote: >>>>>=20 >>>>>> I recently had to move servers due to a hardware issue and now = have a problem that triggers at a SANDBOX level are not working. >>>>>>=20 >>>>>> triggers at the top admin level work OK. >>>>>>=20 >>>>>> I created a new sandbox and tried the triggers but without = success. >>>>>>=20 >>>>>> The same triggers when added to the admin level work OK. >>>>>>=20 >>>>>> Server is Windows 2003 with WebDNA 6.2 >>>>>>=20 >>>>>> Permissions ? >>>>>>=20 >>>>>> Paths ? >>>>>>=20 >>>>>> I can not find anything in any prefs file that may point me in = the right direction. >>>>>>=20 >>>>>> I have tried turning triggers on and off. >>>>>>=20 >>>>>> Adding new triggers. >>>>>>=20 >>>>>> The triggers.db is loading but they are not firing. >>>>>>=20 >>>>>> Any ideas why they may not be working at SANDBOX = level.--------------------------------------------------------- >>>>=20 >>>> If still no luck with Rob's suggestion, then I would suggest just = seeing if you can get a plain NEW vanilla install to send triggers. I = mean clearly triggers are working on loads of running sites (including = on 2 of mine); just establish that you can make a trigger work *in = general*.. and then somehow it will/can shed light on why your other = particular situation is different (misbehaving). >>>>=20 >>>> -G >>>>=20 >>>>=20 >>>> --------------------------------------------------------- >>>> 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 >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> 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 >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> 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 >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > 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 > Bug Reporting: support@webdna.us
Stuart Tremain
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Variable prices and Formulas.db (1997)
DON'T use old cart file! (1997)
Quick ShowIf question (1997)
RE: Languages (1997)
Pulling Captions from JPGs (2003)
Re:Problem (1997)
[shownext max=?] armed (1997)
searching multiple databases in single search (1997)
View Source from cache (1997)
Searching Relational Databases (2004)
Displaying xx number of characters (1997)
How to verify email address (1997)
Webmerchant confirmation hooks? (1997)
can anyone confirm this behavior? (2003)
[WebDNA] Credit card processing (2012)
Email within tmpl ? (1997)
Here's an example of an applet in a tpl (1997)
[WebDNA] paypal FINALLY!!!! (2009)
Authenticate (1997)
Sku numbers (1997)