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
Custom Fields are not clearly Visible on Event Registration Forms | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Custom Fields are not clearly Visible on Event Registration Forms

Custom Fields are not clearly Visible on Event Registration Forms

Posted: June 28, 2012 at 5:23 pm

Viewing 1 reply thread


Shea Butter

June 28, 2012 at 5:23 pm

The Event registration form custom fields are not visible to my customers. I’ve attempted several different template style sheets and none of them are working.

The form is visible on the front page but on the second page (Registration confirmation) and payment screen, the form is not visible.

http://www.internationalsheaconvention.com/espresso/event-registration/?regevent_action=register&event_id=7

Please help.

  • This topic was modified 12 years, 6 months ago by Shea Butter.
  • This topic was modified 12 years, 6 months ago by Josh.


Josh

June 29, 2012 at 7:46 am

Hi Shea,

I looks like the page settings are not set up correctly.

Make sure that the page with the [ESPRESSO_EVENTS] shortcode is set to be the main registration page in Event Espresso>General Settngs>Page Settings.

See this guide for more info:
http://staging.eventespresso.com/wiki/setting-up-event-espresso/#page
Viewing 1 reply thread

The support post ‘Custom Fields are not clearly Visible on Event Registration Forms’ 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 Josh 12 years, 6 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server