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 Odd Personal Information/Invoice Behavior | Event Espresso - Staging Server
A user of a site that I maintain added several questions to the Personal Information group:
Hospital
Address
City
Zip
Phone
When Event Espresso generates an invoice, it tacks the Hospital field onto the City field, and I don’t really see how to change the invoice template to fix this.
I thought perhaps that I could remove those fields from the Personal Information group and start over, but it appears that I can’t do that, either. It seems to me that you should be able to remove added fields from the Personal Information group.
So, any idea how I can fix the invoice and/or remove those fields from the Personal Information question group?
If I uncheck them, they do not appear in the group, but rather in the “Add further questions to the group” box. If I remove them, they do not appear on the event signup form. So, that works just fine.
When I add the City field back to the form, though, I still get the Hospital field attached to the City data. Thinking that perhaps I’d messed up the invoice template (I deleted the lines that printed the “Pay Online” message), I copied over a fresh copy of template.php from /plugins to /uploads. That had no effect.
It looks like the Address2 question was edited to make the Hospital question. The 10 ‘system’ questions have corresponding database fields, so they should not be edited. Change the Hospital question back to Address2, and create a new question called Hospital.
The user changed the name, but failed to tell me that. Now all is well.
Viewing 4 reply threads
The support post ‘Odd Personal Information/Invoice Behavior’ 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.