• Custom page fields exist in a single-blog WP 3.0 installation. The calls to update_post_meta send an array, I’m not manually serializing or anything like that.

    When these pages are imported into another WP 3.0 installation (this time, a MU), while the custom fields are saved in the postmeta table, they’re being serialized AGAIN.

    Original, from DB:
    a:2:{s:5:”title”;s:0:””;s:3:”url”;s:0:””;}

    Imported, from DB:
    s:42:”a:2:{s:5:”title”;s:0:””;s:3:”url”;s:0:””;}”;

    https://www.ads-software.com/extend/plugins/wordpress-importer/

Viewing 1 replies (of 1 total)
  • Thread Starter husani

    (@husani)

    FYI, it even does this for wordpress-core records in postmeta:

    _wp_trash_meta_comments_status:

    Original, from DB:
    a:1:{i:1;s:1:”1″;}

    Imported, from DB:
    s:18:”a:1:{i:1;s:1:”1″;}”;

Viewing 1 replies (of 1 total)
  • The topic ‘[Plugin: WordPress Importer] Importer is double-serializing custom fields’ is closed to new replies.