RocketChat / RocketChat/Rocket.Chat

Custom Account Field Results in Broken Registration Page

Open
#22,739 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

I've added a custom text field in the user account setting, this then modifies the registration page. The new field doesn't follow the style of the other input boxes on the register page, see image attached.

Steps to reproduce:
  1. Add a new field in Administration -> Accounts -> Registration -> "Custom Fields"
    Code Used:
{"Extension": {
	"public": true,
	"type": "text",
	"defaultValue": "x100",
	"minLength": 2,
	"maxLength": 4
}}
  1. Add custom field to Administration -> Accounts -> "Custom Fields to Show in User Info"
    Code used:
[{"Extension": "Extension"}]
  1. Visit the registration link
Expected behavior:

I expect the custom field to match the same style as the other input fields.

Actual behavior:

The custom field box does not match the style as the other input fields.

Server Setup Information:
  • Version of Rocket.Chat Server: Latest
  • Operating System: Linux
  • Deployment Method: Snap
  • Number of Running Instances: 1
  • NodeJS Version: Installed with Snap
  • MongoDB Version: Installed with Snap
Client Setup Information
  • Desktop App or Browser Version: Vivaldi (chromium) but confirmed on Linux Firefox
  • Operating System: Linux
Additional context

custom_field_issue

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by configuring the Extension custom field under Administration → Accounts → Registration → Custom Fields, then opening the registration link. Trace the registration form's custom-field rendering and compare it with the other input fields. Done means the custom field matches the registration page's existing input styling in the reported browsers.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.