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 Registration form quetion | Event Espresso - Staging Server
Hello, I am trying to build a custom registration form that integrates well into our conference web site. We would like to have just a “full name” field instead of a first and last name filed. We can parse the data and fill in hidden fields to support the needs of the plugin. Any tips on doing this?
This wont be easy as it is separate in the database and both variables are used throughout the entire plugin.
You could *possibly* do this with javascript, maybe hide the first name and last name fields add in a custom single field and then split the name up between the two hidden fields.
Yes, I was figuring that you were going to say that. I will discuss options with our designer and see if there is flex room in the requirements. If not then I will do a custom page that hides the variables and replaces them with one field. There is a similar desire with the address. That one is easier since we can just leave the address as a single text blob, but having the components broken out has its advantages.
No problem, let me know if you have further questions.
Viewing 3 reply threads
The support post ‘Custom Registration form quetion’ 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.