Tangy
02-16-2009, 11:16 PM
Hi folks - I AIM'd Nick about this earlier but I wanted to share in case anyone is having similar errors.
I set up a new blog today using WordPress 2.7.1 and proceeded to add posts through the CSV "Upload Data to Posts" function as I normally do. I set the posts to make a category based on a column, and to post randomly between January 1 and December 31.
The three errors I noticed:
1) The post template won't save for some reason. It never saves for me, and I've tried about 10-15 times.
2) No "Previous Imports" show up at all. This is after uploading like 5 separate databases. Nothing.
3) No posts scheduled for the future are actually scheduled. The only posts that get loaded up for me in 2.7.1 are those from this second backward - nothing that is scheduled into the future even shows up under "Posts". It's like they're not scheduled at all - even though the correct amount of records/posts is shown when the CSV is finished uploading.
I'm pretty surprised to see this error and I'm hoping it's due to WP 2.7.1 and something easily fixable. Just wanted to pass it along... for now I have no choice but to go back to WP 2.7.
Thanks,
Tangy
I set up a new blog today using WordPress 2.7.1 and proceeded to add posts through the CSV "Upload Data to Posts" function as I normally do. I set the posts to make a category based on a column, and to post randomly between January 1 and December 31.
The three errors I noticed:
1) The post template won't save for some reason. It never saves for me, and I've tried about 10-15 times.
2) No "Previous Imports" show up at all. This is after uploading like 5 separate databases. Nothing.
3) No posts scheduled for the future are actually scheduled. The only posts that get loaded up for me in 2.7.1 are those from this second backward - nothing that is scheduled into the future even shows up under "Posts". It's like they're not scheduled at all - even though the correct amount of records/posts is shown when the CSV is finished uploading.
I'm pretty surprised to see this error and I'm hoping it's due to WP 2.7.1 and something easily fixable. Just wanted to pass it along... for now I have no choice but to go back to WP 2.7.
Thanks,
Tangy