For several reasons it would be helpful if redhen fields, notably the redhen_contact_email field, were available for use on content types, relations, etc.

1. This would minimize the number of fields that must be maintained on a site.
2. If the redhen_contact_email field were used on a blog post, for example, to make it easy for a reader to contact the post author, the line would be current even if the poster changes his/her email address.

But it does not appear to be possible to put that field on a post. You can create a new redhen email field, but its machine name must be field_redhen_contact_email, or some other name beginning with "field_".

Comments

rsbecker’s picture

rsbecker CreditAttribution: rsbecker commented
Version: 7.x-1.7 » 7.x-1.6
gcb’s picture

gcb
he/him
CreditAttribution: gcb commented
Category: Support request » Feature request
levelos’s picture

levelos CreditAttribution: levelos at ThinkShout commented
Status: Active » Closed (works as designed)

That field is locked intentionally.

rsbecker’s picture

rsbecker CreditAttribution: rsbecker commented

The fact that they are locked is besides the point. I don't need to be able to alter their settings.

I want to be able to use the fields in places other than Redhen. By making them unavailable you go back to one of the big problems of D5 & D6. For example, in D6, a profile field could not be used anywhere but by the profile module. One of the big improvements in D7 was that a field is a field, and for the most part, a field can be placed on any entity bundle, i.e. node, user, file, relation, etc.