• well nice one. updated to latest (0326) wp only to find that i couldn’t insert an export of posts because a new column (gmt) has been added. anyone have any tips for this (i foresee manually editing in timestaps minus 2 hours for 740 odd posts).
    all ideas more gratefully received than you can possibly imagine.
    cheers and thanks in advance – r.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter fatherofpip

    (@fatherofpip)

    Well, I’ve tried it all. different builds of wp, blakey, creating a new table in mysql then importing, then creating new rows for gmt but still no joy…attempted to enter post_date values for the posts in post_date_gmt but my sql skills aren’t up to snuff.
    latest twist is a return to an older version of wp and balkey has left me unable to even insert the old posts in the original posts db.
    Am I banging my head against a brick wall here or is there a way via sql to sort this out?

    fatherofpip: I jsut checked, yes the imports have not yet been updated for the new GMT stuff.
    Here’s what I suggest you try:
    1) Get the 102 Blakely release (save your wp-config.php file)
    2) Clear out your database. Delete all of the table. Start from scratch.
    3) re-upload everything and run the install.
    4) Run the imports at this point.
    5) If all has gone well, and you are feeling a bit saucy, and *really* feel like being on the bleeding edge (be warned that the nightlies are alpha/beta mode and are not recommended for production (non-test) sites) – get the latest nightly, upload it then run upgrade.php found in the wp-admin folder.
    Running the upgrade.php will take care of the necessary housekeeping for gettting the gmt stuff converted right.
    TG

    Thread Starter fatherofpip

    (@fatherofpip)

    hi and thanks for the reply.
    i have tried the blakely, having retired from using the nightlies, but receive an error common to both nightlies and blakely:
    one in the blog header foreach() line 1363 (if i remember rightly) and also foreach() in template-functions-category.php on line 81.
    the sql ipmorts themselves work as long as i create a table based on the old non-gmt systembut throw me an error due to too few column values being inserted if i attempt to import to the newer posts table.
    i’ll wipe the slate clean and do as you suggest and post what i get.
    once again, thanks for the tips – r.

    Thread Starter fatherofpip

    (@fatherofpip)

    ok here we go: got the error messages wrong.
    attempted import into blakey, received error about duplicate (the hello world wp greeting) dleted duplicate and then imported again. received confirmation of successful import but when looking at the edit interface and blog itslef the following error messages are displayed:
    Warning: Invalid argument supplied for foreach() in /data/members/paid/m/g/mgivf.com/htdocs/aboutpip/wp-blog-header.php on line 340
    and
    Warning: Invalid argument supplied for foreach() in /data/members/paid/m/g/mgivf.com/htdocs/aboutpip/wp-includes/template-functions.php on line 1373
    for each post.
    Previous attempts led me to create a user matching the user value in the sql insert and ‘dummy’ categories that would supply available values for the import. Didn’t do that this time though the error messages are the same.
    cheers – r.

    OK, I’ll take a look tonight and see if there is anything I can spot. Do you have a web address I can look at?
    TG

    1. Never use nightlies on production blogs.
    2. Post about nightlies-related issues in the Beta forum.

    At the moment the import tools are not updated to use the nightlies’ database schema, so once you’re done importing you should run upgrade.php to get a working installation.

    Thread Starter fatherofpip

    (@fatherofpip)

    not using a nightly anymore – using blakey – we adress is https://aboutpip.mgivf.com but i’ve cleaned it up – i’ll go in and import the archives to bring up the error messages.
    cheers – r.

    Thread Starter fatherofpip

    (@fatherofpip)

    although – the export via phpmyadmin was from a nightly prior to insertion of gmt for posts.

    Thread Starter fatherofpip

    (@fatherofpip)

    many thanks for the tips, the upgrade took care of all but a few of the imported posts and they i could take care of by reposting after changing the timestamp.
    they had the same error messages as posted previously.
    time to install a nightly build on a sub-domain and see if i can get myself into trouble again ??
    once again – thanks – r.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Can’t import in nightlies’ is closed to new replies.