DEFAULT
Using the default Website Feedback form:
Logged in user - "Sender Name" defaults to logged in 'username' - no field to enter proper name
Non-logged in user - "Sender Name" field is available to enter a proper name.

POSSIBLE SOLUTION
Create a new D8 field so logged in user can now enter their proper name as well as have their 'username' sent through.

RESULTING PROBLEM
Non-logged in user will now have 2x Name fields available to enter their proper name.

PROPOSED SUGGESTED SOLUTION
Have the 'Sender Name' field not default to a username, but allow for both logged in and non-logged in users to enter their Proper Name into an empty field.

NB: As D8 currently defaults, (for a logged-in user) the resulting email to the site admin only has a username delivered to them. i.e kaybee57 sent you a message ...... - no real name is shown. Receiving an email from your website ideally needs a REAL name as part of the message.

CommentFileSizeAuthor
01-Contact-Us-logged-in-user-default.jpg45.66 KBminiwebs2
01a-Contact-Us-logged-in-user-default-resulting-message.jpg24.09 KBminiwebs2
02-Contact-Us-non-logged-in-user-default.jpg28.29 KBminiwebs2
02a-Contact-Us-non-logged-in-user-default-resulting-message.jpg24.44 KBminiwebs2
03-Contact-Us-logged-in-user-new-name-field.jpg35.61 KBminiwebs2
04-Contact-Us-non-logged-in-user-new-name-field.jpg37.15 KBminiwebs2
05-Contact-Us-default-sender-name--field-totally-disabled.jpg52.27 KBminiwebs2
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

divesh.kumar’s picture

divesh.kumar CreditAttribution: divesh.kumar commented

Hi kaybee57,

For logged in user it represents the markup text however wouldn't it be possible if we make that markup an editable textfield with username as default value and in case if user wants to update it with proper name that can be done as well.

Thanks

miniwebs2’s picture

miniwebs2 CreditAttribution: miniwebs2 commented

But in lots of small business cases the receiver of the online enquiry wants to know the 'proper' name of someone sending an enquiry so in my opinion yes, there needs to be a field for a proper name to be entered, as well as a default username field - even if someone is logged in.
D8 yes, you can create that field but as mentioned earlier, the non-logged in user then gets 2 empty fields.

marcingy’s picture

marcingy CreditAttribution: marcingy commented
Category: Bug report » Feature request
marcingy’s picture

marcingy CreditAttribution: marcingy commented
Title: Default Website Feedback Form for LOGGED IN user has no 'Name' field » Allow a logged in user to provide a name on website Feedback Form
andypost’s picture

andypost
he/him
Primary language Russian
CreditAttribution: andypost at Skilld commented
Version: 8.0.x-dev » 8.1.x-dev
Status: Active » Postponed

Suppose any form can be extended with this option in next release

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

ksi’s picture

ksi CreditAttribution: ksi commented

The contact module is without a real name field not usable for our projects.

It is not a good program design to take one field for totally different content, and in addition make it a required field. Since the username field (titled "Sender name") is a required field AND has no default value it can not be ignored this is the worsest combination I could imagine.

Please increase the priority for this request.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.