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 Gravity Forms and EE Events | Event Espresso - Staging Server
hello i’m trying to setup a Front End Event submission page. Im using gravity forms successfully to map to Custom Post Type fields, but i cant see the fields for the event creation but only for the Custom Post Type feature in EE. Any way i can create an event via GForms ?
Currently there is no formal integration with Gravity Forms and Event Espresso doesnt use custom post types for the registration process currently (4.0 will use custom post types).
You may want to check out our Front-end Event Manager form that will allow logged in users the ability to create basic events.
ok even with no integration from GF can you tell me if there is a way to map the fields in the current state of EE ADD AN EVENT admin area. Or to put it another way if they are not custom post types then what are they?
Current EE is a database driven system, in that most of the data is in the database rather than available in custom meta fields.
As such if the data isn’t available to you initially, you would need to use a function to grab the data either from the database or potentially from one of the available globals.
EE 4.0 will be based on true custom post types so integrations like this will be much easier.
Viewing 3 reply threads
The support post ‘Gravity Forms and EE Events’ 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.