views not showing registration field data

should add that i'm getting error "Strict warning: Only variables should be passed by reference in registration_form() (line 31 of /var/www/sites/all/modules/registration/includes/registration.forms.inc)." when registering. not sure if that is a different issue. i am using latest dev version.

scratch that...

with a 'registration' view, i am able to get all the registration data using correct relationships. however, the error above is related. the error line is coming from forms.inc:

  elseif (count($who_options) == 1) {
    $who_default = reset(array_keys($who_options));
  }

when i take this statement out, there are no errors, but some profile data is missing from views.

ok fixed. another post addresses this issue with a patch http://drupal.org/node/1928318#comment-7325568.

well it appeared fixed and then now i am not getting values again.

definitely a problem with the code above and patch.

using Views,
i am either getting user data but missing form data,
or vice versa, getting the form data while missing user data.

something is not functioning right in this code:

  $who_options = registration_access_people($registration);

  // default value for who is registering
  $who_default = NULL;
  if (isset($registration->registration_id)) {
    $who_default = $registration->registrant_type($GLOBALS['user']);
  }
  elseif (count($who_options) == 1) {
    $who_keys = array_keys($who_options);
    $who_default = reset($who_keys);
  }

i should add, admin is still able to see all the data in the View,
but the entity host is missing one or another.

update:

what i figured out so far is that Profile2 fields in the view are modifying the output somehow.

when Profile2 fields are in the view, i lose the form data.
when Profile2 fields are not in the view, form data appears.

update:

i had 2 fields in profile which caused the form data to be blocked.
One was 'Name' using name field, and other was using a taxonomy reference.

For the tax reference, that needs to be uber-specific in the relationship. For example:

Relationships
Registration: User
(User) User: Profile
(Profile) Profile: Location
(term from field_user_location) Taxonomy term: Profile using Location

If not drilled down to term, then adding location field will hold back form data.

Also, the Name.
The only way to get this working properly was by moving the Name field from Profile2 profile into the user account area. Or just remove name from view.

I really don't know if this is a Profile2 or Entity Registration issue. Its just very strange behavior.