Issue on page /site_ops/install_configure_run_guide/configuration/customize_registration_page.html

[Vishwajit-Herma]

I think there is one issue in this doc, that it doesn't mention that, we also need to add customly created fields name in site config in admin panel in extended_profile_fields array. Am I right?

[sarina]

Hi @Vishwajit-Herma thanks for the report. I don't however have enough detail to reply or tag in another expert - do you think you could provide a longer description? Code/screenshots would be helpful as well.

[Vishwajit-Herma]

Title: [Doc Update] Missing Site Configuration step (extended_profile_fields) for custom fields

Description
The current documentation outlines the process for creating and registering custom fields, but it omits a critical final step required to actually expose these fields to the frontend/API.

Currently, if a developer follows the documentation exactly as written, their custom fields will be successfully created in the backend but will silently fail to appear in the frontend (e.g., the Learner Profile MFE) or API responses.

The Missing Step
To make custom fields visible and editable via the API, their field names must be explicitly whitelisted in the LMS Django Admin Site Configurations.

Specifically, the developer needs to add the custom field names to the extended_profile_fields array within the Site Configuration JSON.

I just want to know that "Am I correct about this?"

[Vishwajit-Herma]

#1429. This pull request also address the same issue.

[sarina]

Hi @Vishwajit-Herma - would you mind having this discussion on the PR you linked? I'm not a site operator, so I don't have the best understanding of this.