Custom fields import

Date is a timestamp (seconds from timestamp start date), Select a single value (you define it in Types) and Checkboxes a array (storing the option and value)

Do you need more infos?

Thanks for your reply. Can you please give me example for date and checkboxes. Basically what to write in CSV file.

Thanks

Hi Beda

Please help me with this. Please give me sample data.

Thanks

Sample data for date 01/01/2010, 00.00 hrs:
1262304000

Checkboxes require high elaborated Custom Code to import because those are serialized arrays.
Every Serialized array is differently stored in the Database and it is not possible to import with the CSV importer only.

I apologize not having stated this initially.

thank you

Hi Beda

Thanks for your reply.

I have solved the date issue. This may not be the best way but I found a excel formula to convert date to linux date

=(A1-DATE(1970,1,1))*86400

I use the result of this formaula to import the date which works great. So one down one to go.

I tried couple of things with checkboxes and I managed to find there reference in wp_option table in DB and I tried to use those but didn’t work.

I have 3 checkboxes named : Travel, Food & Lifestyle and this is how they are saved in DB when checked / selected.

a:3:{s:64:”wpcf-fields-checkboxes-option-8c118d34a1f3ecf4323f7c164ebc7f60-1″;a:1:{i:0;s:4:”Travel”;}s:64:”wpcf-fields-checkboxes-option-649a1973132a37753189ba22fd2af5f9-1″;a:1:{i:0;s:6:”Food”;}s:64:”wpcf-fields-checkboxes-option-7f10c97b284b890a3dadce48307cc9d5-1″;a:1:{i:0;s:10:”Lifestyle”;}}

Can you help with this?

Checkboxes require high elaborated Custom Code to import because those are serialized arrays.

Every Serialized array is differently stored in the Database and it is not possible to import with the CSV importer only.

I can not help with this.
It will be a tough one anyway, as any Plugin you use, will re-serialize on import.

Every array has a different amount of characters and this is faster to “import” if you just create the Checkboxes and populate them in the Backend, instead of coding each one manually to import via CSV, which will present the issue of re-serialization.

ok thanks

marked as resolved