bvisick

Do you mean 3.6.6? Latest version I can see is 3.6.5, please confirm – thanks.

I have about 2000 posts that I load into a custom type and want each one to have a unique datestamp so that I can navigate by previous/next – I’ve found that if there are duplicate datestamps then WP’s navigation is random and unpredictable. I solved the plugin’s problem by running the following SQL commands:

set @x = ‘2014-09-01 00:00’;
set @s = 52981;
UPDATE wp_posts set post_date = DATE_ADD(@x,INTERVAL id-@s MINUTE),post_date_gmt = DATE_ADD(@x,INTERVAL id-@s MINUTE) where post_type=’MyCustomPostType’;
SELECT id, post_date, post_date_gmt FROM wp_posts WHERE post_type = ‘MyCustomPostType’ order by id;

@x is the datestamp I want for the first post and @s is the post id for the first post in my system – you should change both of these.

The UPDATE command changes both post_date and post_date_gmt to keep them in step. It uses the start datetime (@x) and increments it by the current post id minus the id of the first post (@s) so each post has a datestamp one minute later than the previous one. The final SELECT is just so I can see what’s happened.

I hope this is helpful, it’s a shame the plugin needs this extra step.

Hi vkumar14, I found your report of the problem when it first arose for me, sorry for hijacking the thread! I found a workaround which was to load the data using the plugin, then use PHPMyAdmin to alter the dates in SQL – not very convenient but at least it gets around the bug.

I had already seen the mail, I tried it and I responded already – it doesn’t work! Please see my previous post.

It seems your plugin no longer works on my site. I will have to update the post_date field directly using SQL while I look for another import solution. I’m sorry you can’t fix it but thanks for trying,

Support has responded but they’ve only suggested changing the format back to the one I started with which does not work and which led me to raise this problem in the first place. I’ve asked them to re-read this thread.

To repeat:
Importing post_date in the format YYYY-MM-DD HH:MM causes every record to be set to 1970-01-01 00:00. So does every other format that has been suggested in this thread.

Importing your sample.csv file also sets every post_date to 1970-01-01 00:00

You were able to import some of my data correctly on your test system

There must therefore be some incorrect setting or conflicting code on my WP system. I’ve disabled all other plug-ins, don’t know what else to try.

The problem is NOT resolved and I would very much like your help – thanks.

OK, done.

I’m afraid this is no different – sample import log entry:

Created Post_ID – 53367 – success , Author – not found (assigned to ) , , , Date – 1970-01-01 00:00:00 , , Status – publish , Verify Here – Web View | Admin View

I’m not surprised by this – we had already established that your sample.csv doesn’t import correctly on my system and I’m sure it does on yours, we’ve just confirmed that the problem is at my end which is what I had assumed.

There must be something on my setup that is conflicting with your plugin – where should I look? I’ve just deactivated all the other plugins and tried again, it still doesn’t work. What else can I try? Thanks.

On dropbox at https://www.dropbox.com/s/tg6cncicqq0h31h/sample.csv

OK, header plus three records follow – if you need more please tell me where to upload a file.

The final two fields are both the post_date – I’ve included two different formats to facilitate debugging, I’m just importing one or the other in my tests.

md_TITLE,md_dial_number,md_height,md_CONTENT,md_condition,md_diameter,md_depth,md_mortar_line,md_true_bearing,md_radials,md_analysis,md_location,md_radius,md_date,md_magnetic,md_neg,md_remarks,md_emphasised,md_image,md_church_ref_num,md_ver,md_post_date,post_date_TEXT
2500,1,108,Upside down.The five lines are quite deeply cut especially 100° line.,VF,,F,1,170,35L 65L 90L 100L 135L,”This is a nice Mass dial with an additional line for Nones. It appears to be “”mason-cut”” rather than scratched.”,Over and to the left of the S. porch door.,,1999.04.28,174,10/6,This dial was out of reach so I was unable to measure angles etc. The angles given are derived from the photo but assume inversion. There are several compass exercises and scratchings in the porch which I feel sure were never dials.,0,m2500.jpg,111,0.1,01/09/2014 00:00:00,2014-09-01 00:00:00
2501,2,24,Five lines in lower hemisphere,F,,F,1,178,40L 60L 90L 115L 130L,A Mass dial with much the same angles as dial 1 and once again includes a line for Nones. This dial however is the right way up.,Door jamb quoin at bottom L. of Priest’s doorway.,L3,1999.04.28,182,10/6,There are several compass exercises and scratchings in the porch which I feel sure were never dials.,0,m2501.jpg,111,0.1,01/09/2014 00:01:00,2014-09-01 00:01:00
2502,3,60,”There are five lines in lower hemisphere but the gnomon hole, which is a good one, is removed to the L. of the focal point of the lines. There is a large pock below the lines.”,F,1,1.5,1,178,45L 65L 86L 107L 125L,”A peculiar Mass dial with the gnomon hole displaced from the focus point of the five lines by approx 1″”. The leading edge of the shadow of a gnomon, if placed hard against the top R. side of the hole would have aligned with the dial lines.”,Door jamb quoin R. of the Priest’s doorway.,L2,1999.04.28,182,10/6,There are several compass exercises and scratchings in the porch which I feel sure were never dials. This dial is I believe two dials made at two different times.,0,m2502.jpg,111,0.1,01/09/2014 00:02:00,2014-09-01 00:02:00
2503,1,67,”A 5″” ring with a few faint radial lines .”,P,”F, “,0.2,0,109,,”Its position inside this E.E. porch, its condition and the configuration of the scratching makes it a very unlikely dial – grafitti!”,Inside W. wall of S. porch,R2.5,1999.04.28,113,10/7,This was probably never a dial but I cannot be sure.,0,m2503.jpg,113,0.1,01/09/2014 00:03:00,2014-09-01 00:03:00
2504,2,56,Ten lines in lower hemisphere enclosed by a part rectangle.,F,,F,0,194,0L 40L 55L 70L 90L 107L 120L 135L 148L 173L,”It seems to have been a Mass dial with only some of the lines original and authentic – perhaps those at 40°, 55°, 70°, 90° and maybe 107°.”,Buttress at S.E. corner of the nave.,L2.5,1999.04.28,198,10/7,It looks as if this dial has had lines re-scratched and perhaps some lines in the LRQ added.,0,m2504.jpg,113,0.1,01/09/2014 00:04:00,2014-09-01 00:04:00
2505,1,50,”Consists essentially of 5 concentric rings around a gnomon hole. Rings at 3″”, 2.4″”, 2.2″”, 2″” & 1.3″” radius, some are better quality than others.”,F,0.5,0.5,0,252,70L 90L,It may have been a Mass dial with rings where the point of the gnomon was used to indicate the seasons.,”In S. porch on W. wall, 50″” from corner with S wall of the church.”,R3,1995.10.31,256,5/10,It may be no more than someone playing with dividers or the like.,0,m2505.jpg,55,0.1,01/09/2014 00:05:00,2014-09-01 00:05:00
2506,2,64,This was quite accurately made with straight even lines and remains of a good peripheral ring. Five lines remain in the noon-line area. The gnomon hole is tapered horizontally.,VF,0.5,1,0,162,45LP 63LP 80L 100L 120L,No doubt the remains of a time-keeper of some sort – not enough remains to determine what sort.,On S. face of E. buttress at front of S. porch.,R3.5,1995.10.31,166,5/10,There was probably more of this dial at one time but it is still quite useful.,0,m2506.jpg,55,0.1,01/09/2014 00:06:00,2014-09-01 00:06:00

Same problem with your sample CSV, see following extract of the import log. If it helps, I’m importing a custom post type but your sample CSV fails to import the date whether as a regular post or custom post.

Your Import Is In Progress…
Total no of records – 6.
Total no of mapped fields for single record – 12.
Total no of unmapped fields for a record – 0.
Chosen server request is 6 .

Created Post_ID – 52965 – success , Author – not found (assigned to ) , Category – Pro Plugin | WordPress | CSV Importer , Tags – pro, wp plugin, csv importer ,vasanth , Date – 1970-01-01 00:00:00 , Image -wpcsvimporterpro.png , Status – private , Verify Here – Web View | Admin View

Created Post_ID – 52966 – success , Author – not found (assigned to ) , Category – Open source | Free Plugin | WordPress | CSV Importer , Tags – free, wp plugin, csv importer , Date – 1970-01-01 00:00:00 , Image -wpcsvimporterfree.png , Status – private , Verify Here – Web View | Admin View

I’m afraid that doesn’t fix it. I’ve reinstalled 3.6.4 and tried it with the post_date field in my import data set to:

DD/MM/YY HH:MM
DD/MM/YYYY HH:MM
YYYY-MM-DD HH:MM

I tried all of them with and without :SS on the end of the time and also tried enclosing the field in “”.

In all cases post_date is set to 1970-01-01 00:00 for all records. Help! Thanks.

Hi, I’m having similar problems with importing post_date. I had the date in the format YYYY-MM-DD HH:MM which worked OK in v3.6.1 of the plugin. Upgraded to 3.6.4 and it set every post to 1970-0-0 00:00. I changed the format to DD/MM/YY HH:MM as suggested above, same result. Downgraded to 3.6.1 and dates import OK.

Something seems to have broken between 3.6.1 and 3.6.4 (I didn’t use any of the intermediate releases) – please can you advise? Thanks.