Create extra field in user profile to display realname

Voila patch. Very easy.

Now with a link to the user profile, if the current user has access to that.

Note to self: don't hack patches.

Attached patch is re-rolled against 1.2.

FFS! Last attempt!

This patch is unsafe. Use #29.

Now it's getting ridiculous....

Views field? How is that related to an extra field in the user profile?

Who's talking about views??

"Extra fields" doesn't mean "more fields". It means extra_fields.

Are you seriously talking about adding a real field to load a real view, to display a logicless name? This is THE reason extra_fields exist.... You don't create a field and a view to display a node title or created date, do you?

Did you see the patch? That's what an extra_field does. No logic, no display settings, no querying, just a simple display.

I have 3 fields that combined are the realname. Sometimes 1 of those 3 fields is shown. I can do that with the normal field display. Other times the full name (realname) is displayed. No addressfield. Realname takes care of the combination logic/pattern. Now I need to display it...

It seems a sensible addition. Whether to add it, is up to you.

@dreamlabs If you've reviewed & tested, change the issue status so the maintainer knows this one's ready to go.

Very true!

#10 is unsafe.

New patch & interdiff. #entity_type was also missing from the fake field.

Realname strips HTML tags during its update process:

  // Perform token replacement on the real name pattern.
  $realname = token_replace($pattern, array('user' => $account), array('clear' => TRUE, 'sanitize' => FALSE));

  // Remove any HTML tags.
  $realname = strip_tags(decode_entities($realname));

  // Remove double spaces (if a token had no value).
  $realname = preg_replace('/ {2,}/', ' ', $realname);

  // The name must be trimmed to 255 characters before inserting into the database.
  $realname = truncate_utf8(trim($realname), 255);

(which is WRONG IMO), so #10 isn't really unsafe, but wrong nonetheless.

Extra fields don't have settings out of the box. They're still very useful to position fields, like in this case. I have a Sandbox I use to add settings to extra fields. https://www.drupal.org/sandbox/rudiedirkx/2501347 I don't think D8 will have this out of the box.

Extra fields with settings?? That would be awesome, but hook_entity_extra_field_info() doesn't mention anything. Neither does EntityFieldManagerInterface::getExtraFields().

Ah yes. It's still TRUE by default in D8, which is still weird, but it's better.

You can explicitly check the display settings for the extra field. If it's not explicitly enabled, it's not user-enabled. A lot of code to check something very simple...

This is what I use in Node Registration, including the comment =)

    // Find which fields to show. Unfortunately this is necessary for new extra fields, which are
    // VISIBLE by default. Crazy Drupal...
    $bundle_settings = field_bundle_settings('node', $entity->type);
    $use_view_mode = !empty($bundle_settings['view_modes'][$view_mode]['custom_settings']) ? $view_mode : 'default';
    $show_field = function($name) use ($bundle_settings, $use_view_mode) {
      return !empty($bundle_settings['extra_fields']['display'][$name][$use_view_mode]['visible']);
    };