I added a category field to my table with type of INT. Later I enabled multiple select as an option, not realising that the database field type would not support that. Compiling the component would result in a multiple-select form, but saving would return an error: Save failed with the following error: Incorrect integer value: '{"0":"193"}' for column 'catid' at row 1
Unfortunately I had to use my poor brain once more and figure out that the database just wanted a single integer. Perhaps an additional help text on the "multiple" option would help prevent such issues?
Which part of the extension will be affected by this enhancement?
Field(admin_view)
Additional Context
### Enhancement Details
I added a category field to my table with type of INT. Later I enabled multiple select as an option, not realising that the database field type would not support that. Compiling the component would result in a multiple-select form, but saving would return an error: Save failed with the following error: Incorrect integer value: '{"0":"193"}' for column 'catid' at row 1
Unfortunately I had to use my poor brain once more and figure out that the database just wanted a single integer. Perhaps an additional help text on the "multiple" option would help prevent such issues?
### Which part of the extension will be affected by this enhancement?
Field(admin_view)
### Additional Context
<img width="1606" alt="image.png" src="attachments/e1a3b8eb-3874-4927-a2ee-e20a1f3fc956">
@ConfidantCommunications this is actually very easy to accomplish, and we will also implement it on our side.
That said, you can already achieve this yourself in a simple way - and even share it with others:
Go to the Fieldtypes area in JCB.
Locate the relevant fieldtype (for example, category).
On the Description side of each value, find the entries for single or multiple.
Update those descriptions with any notes or reminders you need.
If you have a Fieldtypes repository set up, you can then:
Push your updated fieldtype, and
Optionally create a PR to the main Fieldtypes Repo to share it with the community.
As mentioned, we'll also update the core fieldtypes and keep the main repository aligned.
@ConfidantCommunications this is actually very easy to accomplish, and we will also implement it on our side.
That said, you can already achieve this yourself in a simple way - and even share it with others:
1. Go to the **Fieldtypes** area in JCB.
2. Locate the relevant fieldtype (for example, `category`).
3. On the **Description** side of each value, find the entries for *single* or *multiple*.
4. Update those descriptions with any notes or reminders you need.
If you have a **Fieldtypes repository** set up, you can then:
- Push your updated fieldtype, and
- Optionally create a PR to the [main Fieldtypes Repo](https://git.vdm.dev/joomla/joomla-fieldtypes) to share it with the community.
As mentioned, we'll also update the core fieldtypes and keep the main repository aligned.
@ConfidantCommunications We've added the requested note to the Category Fieldtype. Now, in your JCB system, when you go to Fieldtypes, select the Category Fieldtype, and click Reset, the updated note about whether it should allow multiple selection or not, will automatically be included in your fieldtype.
@ConfidantCommunications We've added the requested note to the [Category Fieldtype](https://git.vdm.dev/joomla/joomla-fieldtypes/src/branch/master/src/f70346b3-2096-4f44-8b26-01ab87da7d1e). Now, in your JCB system, when you go to Fieldtypes, select the Category Fieldtype, and click `Reset`, the updated note about whether it should allow multiple selection or not, will automatically be included in your fieldtype.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Enhancement Details
I added a category field to my table with type of INT. Later I enabled multiple select as an option, not realising that the database field type would not support that. Compiling the component would result in a multiple-select form, but saving would return an error: Save failed with the following error: Incorrect integer value: '{"0":"193"}' for column 'catid' at row 1
Unfortunately I had to use my poor brain once more and figure out that the database just wanted a single integer. Perhaps an additional help text on the "multiple" option would help prevent such issues?
Which part of the extension will be affected by this enhancement?
Field(admin_view)
Additional Context
@ConfidantCommunications this is actually very easy to accomplish, and we will also implement it on our side.
That said, you can already achieve this yourself in a simple way - and even share it with others:
category).If you have a Fieldtypes repository set up, you can then:
As mentioned, we'll also update the core fieldtypes and keep the main repository aligned.
@ConfidantCommunications We've added the requested note to the Category Fieldtype. Now, in your JCB system, when you go to Fieldtypes, select the Category Fieldtype, and click
Reset, the updated note about whether it should allow multiple selection or not, will automatically be included in your fieldtype.