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 Moodle Authentication | Event Espresso - Staging Server
Part of what Moodle needs to map is a “user name” and “password” field. We would need to make this part of the “checkout” process for any EE event that was an online Moodle class.
I’m not sure how to best add these fields to the EE checkout process. Any suggestions?
You can take a look at the files for the paypal gateway to see how we gather the user’s account information in the settings.php file, we put together the request to paypal in the paypal_vars.php file, and we receive the response from paypal in the paypal_ipn.php file.
Thanks for the info Sidney.
I’d like to make two new fields for each attendee registration – one for user name and one for password. Moodle wants to know table/field name of each of these for lookup (http://prntscr.com/dtuaa). So… how would be the best way to go about adding these two fields to the checkout process, so that they appear in the “wp_events_attendee” table, which would allow me to map them to Moodle?
Thanks,
Isaac
Viewing 2 reply threads
The support post ‘Moodle Authentication’ 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.
This is a meta description test for the WP User integration.