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
A Couple CSV Import Headers Not Working | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › A Couple CSV Import Headers Not Working

A Couple CSV Import Headers Not Working

Posted: October 11, 2013 at 3:37 pm

Viewing 5 reply threads


Deborah Walden

October 11, 2013 at 3:37 pm

Hi Guys, I’m getting a ton done with your plugin. Im at the end phase of the dev right now and going through with the client on how to import using the CSV. We noticed that the allow_multiple, registration_start and registration_end are not importing any values that we enter into the CSV, yet the other fields seems to work.

Also, is it okay to leave the event_identifier field blank?


Dean

  • Support Staff

    •

October 14, 2013 at 3:23 am

Hi Deborah,

The “allow_multiple” was working for me, it requires a capital Y or N in the cell. It changes the “Allow group registration setting”.

I do concur that the “registration_start ” and “registration_end” are not functioning correctly. I will get a developer ticket raised to look into this.


Deborah Walden

October 14, 2013 at 2:31 pm

Hi Dean,

Also, it looks like my conf_mail header isn’t sending the right data. It sends a “Y” into the system where in the csv I have this:

***This is an automated response – Do Not Reply***
Thank you [fname] [lname] for registering for [event].
We hope that you will find this info session both informative and enjoyable.
Should have any questions, please contact [contact].

Thank You.


Sidney Harrell

  • Support Staff

    •

October 14, 2013 at 3:48 pm

It sounds like your columns might be off and it is seeing the “Y” from the column before the conf_email column. Also, the date format in the events.csv sample file is wrong. The dates should be in Y-m-d format, 4 digit year, 2 digit month, 2 digit day, seperated by dashes.


Deborah Walden

October 14, 2013 at 5:50 pm

Hi Sidney, ill check the data formats for the event.csv. I dont know if i mentioned that im using version 3.1.36 ALPHA so I can get categories in. Is there a best way to send you an example of one of my import .csv’s?

PS. still cant get allow_multiple to work, always defaults to Yes when I enter in a N for that field.


Sidney Harrell

  • Support Staff

    •

October 15, 2013 at 9:37 am

You can email a copy to support at eventespresso.com
Viewing 5 reply threads

The support post ‘A Couple CSV Import Headers Not Working’ 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 Sidney Harrell 11 years, 3 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server