Problem With Custom Fields

  • Resolved jmanpa

    (@jmanpa)


    16 years, 7 months ago

    I just successfully migrated a Blogger blog to WordPress but I have a strange side-effect from doing so.

    When I try to “write” a new post, I get 100s of Custom Fields that appear prior to me writing anything. The key of each of these is “blogger_blog” and the value field is “myblogname.blogspot.com”. There are also 200 custom fields with “blogger_permalink” as key and for the value field, the url of each my past posts.

    Needless to say I don’t want a few 100 custom fields pre-populated each time I try to post. It delays the ability post due to the wordpress script for this page spending minutes to populate all the (apparently default) custom fields.

    How do I remove this behavior?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter jmanpa

    (@jmanpa)

    I think I may have resolved it. Someone can tell me if this was a bad thing to do:

    I went into MySQL and executed the following statement:

    DELETE FROM wp_postmeta WHERE meta_key=’blogger_blog’ or meta_key=’blogger_permalink’

    so far I haven’t find any undesirable effects and the “write” page is now devoid of the offending custom field defaults.

    I have this same problem. Is there any way anyone could verify that this is a good fix?

    I just tried this and it worked for a day or so but now I’m back to having the same problem. Now not only do I need to fix the problem but I am also worried that I did something bad in the db if deleting those tables didn’t do it…

    I had this same problem after upgrading to 2.6 and importing two WP blogs into a third one, so maybe it’s a migration issue? Export and import worked fine, better than they have on earlier versions in fact, I have all the posts and comments. But custom fields in write > post were insane. Custom enclosure fields were generated for every mp3 file linked to in the imported blog – about 60 or so in all – they just appeared and I couldn’t delete them.

    All fixed now and this is a quick thumbs up on the MySql statement from jmanpa! I executed the statement changing ‘blogger_blog’ to ‘enclosure’ and meta_key= to ‘enclosure_permalink’. I wasn’t really sure whether that last command was necessary or what it would do, but nothing ventured, etc… And it didn’t break the blog. It worked.

    Same problem here. jmanpa works.

    Thank you so much! You just resolved the nightmare of importing a 30+ author site and discovering a million (only slight exaggeration) custom fields for each new post. Add that to the fact that I have to teach the authors how to use custom fields in the first place.

    I had to also add:

    or meta_key=’blogger_author’

    could someone please give more detailed instructions for this fix?

    Thanks.

    It worked perfectly for me.

    Go to phpMyAdmin and run the sql query:

    DELETE FROM wp_postmeta WHERE meta_key = ‘blogger_blog’ OR meta_key = ‘blogger_permalink’ OR meta_key = ‘blogger_author’

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Problem With Custom Fields’ is closed to new replies.