Additional Custom Fields?

[Greg MacKinnon]

Stephen:

I only noticed this after the March 3rd update, but it could be that it occurred before that.

The drop down list for Custom Fields has a number of new entries that I did not add. The entries are:<br>
text_already_subscribed<br>
text_error<br>
text_invalid_e-mail<br>
text_not_subscribed<br>
text_required_field_missing<br>
text_subscribed<br>
text_unsubscribed

It could be that these are purposefully part of the list to allow custom text, but I did not see any notes regarding that change.

It is also possible that I have inadvertently made some incorrect cross-reference in my site-ultility that is confusing things.

So, I bring it to your attention to decide which. 🙂

Thanks.

[Stephen Harris]

Hi Greg,

The dropdown for meta keys lists meta keys that are already in use by your site – but this could be across all post types (posts, pages, events, etc.). They could have even been created by a plug-in without you releasing it.

So in short, those meta fields have nothing to do with the plug-in, but it isn’t unusual to see fields that haven’t been used for events there. Custom fields is a WordPress core feature, so this behaviour isn’t determined by the plug-in either.

[Stephen Harris]

Hi Greg,

The dropdown for meta keys lists meta keys that are already in use by your site – but this could be across all post types (posts, pages, events, etc.). They could have even been created by a plug-in without you releasing it.

So in short, those meta fields have nothing to do with the plug-in, but it isn’t unusual to see fields that haven’t been used for events there. Custom fields is a WordPress core feature, so this behaviour isn’t determined by the plug-in either.

[Author]

Posts