- Issue created by @santosh_verma
- Assigned to ebrahimjmi
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 11:21am 18 May 2023 - Assigned to santosh_verma
- Issue was unassigned.
- Status changed to Needs work
almost 2 years ago 9:15am 23 May 2023 - 🇮🇳India santosh_verma Faridabad
Hi @ebrahimjmi, I did a little mistake while creating the issue. It was actually supposed to be for Claro theme and the patch provided doesn't apply to Claro. Attaching Screenshots and also added more details in the Issue summery
- Assigned to ebrahimjmi
- last update
almost 2 years ago Patch Failed to Apply - Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 10:07am 24 May 2023 - Assigned to ebrahimjmi
- Status changed to Needs work
almost 2 years ago 11:34am 24 May 2023 - 🇮🇳India ebrahimjmi
Hi @Santosh_Verma, Please consider the latest one patch, actually I have follow the coding standard.
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 11:46am 24 May 2023 - Status changed to RTBC
almost 2 years ago 11:32am 25 May 2023 - 🇮🇳India santosh_verma Faridabad
@ebrahimjmi I have tested the patch #14 and its applied cleanly and resolving the issue.
- 🇩🇰Denmark ressa Copenhagen
Moving issue to Drupal core, per the project page:
Claro is now part of Drupal core
All new issues should be filed in the Drupal Core issue queue → .
Drupal 11 has modernized its admin UI, moving towards a cleaner, more intuitive design.
Instead of separating "add a new field" and "reuse an existing field" with an explicit "or," these actions are now likely presented in a unified workflow or dropdown for simplicity. now it have adopted modern design principles, moving away from unnecessary separators like "or."
The focus is now on providing clearer, less cluttered options for field management.
@ressa this issue is no more exist Drupal 10 and 11. now Reusing existing fields is integrated seamlessly without needing a separate selector.- 🇩🇰Denmark ressa Copenhagen
Thanks for reviewing the issue @kushagra.goyal. I merely moved a lot of Claro issues to their correct place -- so feel free to change Status to "Closed (Outdated)", for this and similarly no longer relevant issues.
Ah Alright, Thanks for the update! Since the issue has been correctly categorized and is no longer relevant, I have changed the status to Closed (Outdated). Let me know if any further action is needed.