Support » Plugins » Plug-in fills up “custom fields.”

  • hi!

    Relatively new to wordpress and I’ve become fascinated with plug-ins. I’ve sample about 50 in the last two days!

    One I tried, wp-o-matic, fills my “Custom fields” with numerous keys and values for any new page of post. Can that be avoided? And will such a high content of text ever become a strain on the database and server?

    Oh, and one more question if I could. I’ve noticed I can delete these custom fields and the posts are not affected. Is there a simple way to mass-delete them?


Viewing 3 replies - 1 through 3 (of 3 total)
  • Hello,
    As stated by Scandalous, i get the same thing.
    The thing is when i get in “Write” section of the Dashboard, i get a loop showing heaps of “wpo_campaignid” fields (seems never ends).
    If i dont push “Stop” in Firefox, well it peaks up in memomry and almost freezes up. Is there a way to get rid of this? I’ve looked around in post-new.php and custom-filds.js but i cant get rid of it.
    And BTW the “wpo_campaignid” i get is a deleted campaign.

    Any clue someone help?!?


    O well, not much answers back.
    So finally i got rid of the listing of the Custom-Fields thing.
    I went in edit-form-advanced.php
    and i stripped off the followin code

    <div class=”dbx-b-ox-wrapper”>
    <fieldset id=”postcustom” class=”dbx-box”>
    <div class=”dbx-h-andle-wrapper”>
    <h3 class=”dbx-handle”><?php _e(‘Custom Fields’) ?></h3>
    <div class=”dbx-c-ontent-wrapper”>
    <div id=”postcustomstuff” class=”dbx-content”>
    <table cellpadding=”3″>
    $metadata = has_meta($post_ID);

    and the custom fields stoped showing at all.

    I think the best way to delete them, until the new version is released sometime in the next few weeks hopefully, is to go into your SQL editor eg phpmyadmin. In there go into wp_postmeta and delete all wpo_ entries with postid of “0”. I’ve just done that and it worked for me, I found it easier as you can select 30 or more entries at a time.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plug-in fills up “custom fields.”’ is closed to new replies.