The Overlay settings for users that have permission to change it, is not possible to rearrange the order of in the Manage Fields setting for user profile. This can have the effect that it can appear almost anywhere, plus that is is not possible to place under a tab using the excellent Field Groups module.

Preferable this should also be backported to Drupal 7.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tsvenson’s picture

Issue tags: +Usability, +D7UX, +d8ux

Setting the right tags.

David_Rothstein’s picture

Title: Make user profile field available in Manage Fields » Make user profile fields available on the Manage Fields page

Yeah, I've noticed that too - it's annoying. Almost a bug report, really.

I think it's not just Overlay module that has this problem. Contact module seems to also, and there may be others. Ideally we just fix all the ones in core at the same time.

(I believe it can be fixed pretty easily by implementing hook_field_extra_fields().)

tsvenson’s picture

Yes, that's what Dave Reid used when fixing it for the XML Sitemap module. See the commit in http://drupal.org/node/1176526#comment-4549402 for how it was done.

I have also filed #1176562: Make all Core fields available in Manage Fields/Display as needed with a list of other Core modules missing this.

ksenzee’s picture

Can we close this issue as a duplicate and fix it all in #1176562: Make all Core fields available in Manage Fields/Display as needed?

tsvenson’s picture

Reason I posted both was that this one is for the overlay module, while the other one is for the user module. I didn't see that as creating dupes.

tsvenson’s picture

Status: Active » Needs review
FileSize
618 bytes

Here is a patch for making the overlay setting available on admin/config/people/accounts/fields rolled agains 7.x.

Drupal 8 requires PHP 5.3.2 and I don't have that installed on my machine, but the patch should work on that too.

tsvenson’s picture

FileSize
618 bytes

Same patch as in #6, but rolled against 8.x. Its untested since my dev environment doesn't have the right PHP version to run Drupal 8.x.

tsvenson’s picture

Status: Needs review » Closed (duplicate)

Turned out fixes for this was hiding in http://drupal.org/node/967566 :(

Marking as dupe...