But what .post-meta is, is the Custom Fields area. That red & green font coloring was coded by me in the CSS for any custom fields I might add. So I can't really hide it or else wherever I've used Custom Fields, well, they'll disappear.
I agree, if you want to sue custom fields then hiding this section with CSS is not a real solution.
A db request of the theme fills this list.
Custom Field names and values are stored in the wp_postmeta db table as well as the post specific settings of podPress. The custom field names are
meta_key values and custom field value are
meta_values. podPress saves its post related meta data e.g. with the
meta_key podPressPostSpecific. podPress save also other meta data in the wp_postmeta table and uses 2 other
meta_keys. All of these meta_keys include "podpress" as a sub-string.
So whatever grabs the meta data grabs (nearly) all rows with the sam
post_id. (One _postmeta rows has the columns meta_id, post_id, meta_key_ meta_value.)
Do you use the function
the_meta(); to display the custom fields?
One solution is maybe to use a custom db request which excludes rows with certain
meta_keys. (or if you don't want to use podPress to delete the rows with the podPress
But this problem is probably a problem for all who want to use the_meta(); in there them theme. That is why I will try to find a different solution for the podPress users (maybe meta_keys with an underscore at the begining).
Thanks for making me aware of this issue!