joomla/Component-Builder

Fork 12

[ENHANCEMENT]: add default option to the form field type usergrouplist #1233

New Issue

Open

opened 2025-07-17 14:02:43 +00:00 by Tom van der Laan · 1 comment

Tom van der Laan commented

2025-07-17 14:02:43 +00:00

Member

Enhancement Details

The usergrouplist form field type in JCB does not have the option "default" had to add it manually.

Which part of the extension will be affected by this enhancement?

Fieldtypes(admin_views)

Additional Context

No response

### Enhancement Details The usergrouplist form field type in JCB does not have the option "default" had to add it manually. ### Which part of the extension will be affected by this enhancement? Fieldtypes(admin_views) ### Additional Context _No response_

Tom van der Laan added the

enhancement

label 2025-07-17 14:02:43 +00:00

Llewellyn commented

2025-07-30 19:50:12 +00:00

Owner

Thanks for pointing this out!

Just a heads-up — the field types are now maintained in a separate repository here:
👉 https://git.vdm.dev/joomla/joomla-fieldtypes

This means you don’t necessarily have to open an issue for something like a missing value. You can now directly contribute improvements by following this workflow:

Fork the repository to your own account so that you can make changes.
In your JCB instance, configure it to use your forked version of the field types repository (this gives you full access to make changes).
Apply the fix or enhancement — in your case, add the missing value.
Push your change to your fork.
Create a pull request back to the core field types repo.

If your contribution is accepted, it becomes part of the official field type set and will be available to everyone.

The exciting part is that JCB now supports this external repository integration fully. Once a field type is updated in the external repo, the core can perform a reset to pull the latest changes, and that field type is synced back into JCB automatically.

So in short:
✅ You can fix it once in your fork
✅ Share it with the community
✅ And keep your version in sync with the core updates at your own pace

Let me know if you need help getting your JCP repo linked to your fork — happy to help!

Thanks for pointing this out! Just a heads-up — the field types are now maintained in a separate repository here: 👉 **[https://git.vdm.dev/joomla/joomla-fieldtypes](https://git.vdm.dev/joomla/joomla-fieldtypes)** This means you don’t necessarily have to open an issue for something like a missing value. You can now directly contribute improvements by following this workflow: 1. **Fork the repository** to your own account so that you can make changes. 2. In your **JCB instance**, configure it to use your forked version of the field types repository (this gives you full access to make changes). 3. Apply the fix or enhancement — in your case, add the missing value. 4. Push your change to your fork. 5. Create a **pull request** back to the core field types repo. If your contribution is accepted, it becomes part of the official field type set and will be available to everyone. The exciting part is that JCB now supports this external repository integration fully. Once a field type is updated in the external repo, the core can perform a `reset` to pull the latest changes, and that field type is synced back into JCB automatically. So in short: ✅ You can fix it once in your fork ✅ Share it with the community ✅ And keep your version in sync with the core updates at your own pace Let me know if you need help getting your JCP repo linked to your fork — happy to help!

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: joomla/Component-Builder#1233

No description provided.