Automattic / Automattic/jetpack

Comments Form: Allow Hiding Website Field

Open
#16,837 7 comments 1 reaction 0 assignees View on GitHub
[Feature] Comments [Pri] Low Customer Report [LEGACY] Enhancement
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

#### Is your feature request related to a problem? Please describe.

A lot of readers today won't have a website, and so displaying a "Website" field can provide some confusion; I often get people entering my own website link into the field, especially as there's no indication that it's optional. It would be preferential if an option could be provided to hide it, since it's never really been useful for me and is just causing confusion.

#### Describe the solution you'd like

Since the form is an iframe, I think that changes will need to be made outside the Jetpack plugin.

https://github.com/Automattic/jetpack/blob/98d6422c8504d1e22e0f1a52c816ea7f5da36336/modules/comments/comments.php#L337

Ideally, an option or filter to hide the Website field could be provided. Alternatively, the ability to add emphasis that fields are optional may alleviate confusion.

#### Describe alternatives you've considered

If I recall correct, before my site became an Atomic one, I was able to use some styling to tweak the form since there was no iframe. As there is now, the alternatives are limited.

#### Additional context

Note that it's unclear that the field is optional, leading to a lot of commenters entering my own site's URL. It'd be much easier to hide it.

Screenshot 2020-08-14 at 14 38 23
Theme in screenshot: Ashe

Contributor guide

Open the contributing guide

Research direction

Start with the comments form entry point linked in modules/comments/comments.php around line 337, then trace how the iframe form is assembled outside the plugin. The work is complete when site owners have a documented option or filter to hide the Website field, with the resulting comments form behavior verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.