Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Use a mySQL trigger with an EE table? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Use a mySQL trigger with an EE table?

Use a mySQL trigger with an EE table?

Posted: April 6, 2014 at 9:22 pm

Viewing 1 reply thread


joelw

April 6, 2014 at 9:22 pm

Hi – I’m using 3.1.32.2.P and I’d like to create an “Insert into” trigger on the wpattendees table to copy some information about the attendee to a different table used elsewhere in our CRM system. When I attach the trigger I get an error when trying to register an attendee “An error occurred. No attendee was received.”

In trying to troubleshoot, I just want to be sure that this is even possible and that it’s not the addition of the trigger that’s causing the error. If that is allowed, and wouldn’t necessarily cause EE any problems, I’ll assume it’s the trigger itself that is erroring out. Thanks for your help.


Anonymous

April 7, 2014 at 3:52 am

Hi Joelw,

This depends on the ‘trigger’ you are using.

Can you explain a little on what it is you would like to save & how/where you are attempting to this please?
Viewing 1 reply thread

The support post ‘Use a mySQL trigger with an EE table?’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Anonymous 10 years, 9 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server