Suggestion

Shahjahan Jewel The user can change their FluentCommunity Display Name by going to their FluentCommunity “Edit Profile” form and changing their “First Name” and “Last Name” boxes.  These “First Name” and “Last Name” boxes always appear with placeholder text, (which comes from Wordpress’s native database table, not from FluentCommunity’s fcom_xprofile table), so that, even if a user has changed their FluentCommunity Display Name, the placeholder name that appears in the “First Name” and “Last Name” boxes is always whatever Wordpress thinks the user’s first and last name are.

If the user then changes their first and last name within their Wordpress profile (not within their FluentCommunity profile), then the placeholder text in the first and last name boxes on the FluentCommunity Edit Profile form changes—but still they may not match the user’s current FluentCommunity Display Name. 

These changes and differences can be confusing for the user (and they were certainly confusing for this noob developer before she figured them out! :-) ). 

Suggestion: I think FluentCommunity should get the placeholder text from Wordpress initially, but after the initial value of the fcom_xprofile field table’s display_name field has been changed by the user, thereafter the FluentCommunity should get the placeholder text from the fcom_xprofile field table’s display_name field and not from wherever Wordpress stores the first and last name of the user. That way, the placeholder text will match whatever the user's current Display Name is.