When one enters text into the "Page Title" field in the Profiles module, it causes a display error in the output listing from the Members module.

For example, a line in the members list should look like this:
Name
Jane

But if one enters the text "First Name" into the "Page Title" field of the Profiles module, the output changes to;
Name
< a

If one sets the "Truncated Field Length" field in the Members Module to zero, the output looks like this:
Name
< a href="/profile/profile_firstname/Jane">Jane

The fix for now is to not use the "Page Title" feature in the Profiles module

This may be the same bug reported under the title "Members list double encoding"

Comments

wmostrey’s picture

wmostrey commented
Assigned: Unassigned » wmostrey
Priority: Normal » Critical
modctek’s picture

modctek commented

I can confirm this, but it only seems to affect certain profile fields. I'm using Profile Page Titles for other profile fields like Phone #, State, etc. that do not bug the display, but if I add a Page Title to either profile fields named profile_lname or profile_fname, it causes the bugged output. Perhaps tied to the profile field name actually containing the letters "lname" or "fname"?

I tried creating another profile field called profile_testname and even though I did *not* specify a Page Title for that particular Profile field, Members still displayed that profile field contents as a link to edit the user profile. When I changed the profile field to "profile_testnme" it was no longer displayed as a link to edit the user.

I'm guessing that the author has embedded some function that looks specifically for the text "name" in the field title/name and makes an assumption that whatever content therein should be clickable, regardless of the Profile Page Title setting. I'll guess that the bug is somewhere near there.

wmostrey’s picture

wmostrey commented
Status: Active » Closed (won't fix)