User tests: Successful: Unsuccessful:
Pull Request resolves #47507
This fixes a Joomla 6 regression where the category field on New Article looks empty, even though a category is already selected. I updated the joomla-field-fancy-select so that, right after Choices initializes, it picks up any preselected <select> value and shows it in the UI. (same expected UX as previous versions j5.4 etc)
Navigate to: administrator > content > Articles > create a new article
The Category field render as empty on New Article, even though a category was selected and used on save. (ie if you only give that article a name and click on save without specifying any category - and then you open the article you see preslected/default category(uncategorized) is assigned to it )
The Category field shows the preselected value and existing save behavior remains same.
Please select:
Documentation link for guide.joomla.org:
No documentation changes for guide.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | JavaScript Repository NPM Change |
I have tested this item ✅ successfully on 95041e0
I have observed the before and after mentioned in the testing instructions.
Sorry, the fix is wrong.
It looks like a bug in Choices.js side, and related to <select> behavior.
On our side we can maybe do a workaround and set first element selected but not how it done in the PR.
Sorry, the fix is wrong. It looks like a bug in Choices.js side, and related to
<select>behavior.On our side we can maybe do a workaround and set first element
selectedbut not how it done in the PR.
Thanks for the clarification, @Fedik - Will rework this to a narrower workaround and avoid broad behavior changes
| Labels |
Added:
NPM Resource Changed
PR-6.0-dev
|
||
Yes, that looks better now.
Please add the comment above the changes with description why this workaround was add for a developers from future.
Then it can be tested.
Yes, that looks better now. Please add the comment above the changes with description why this workaround was add for a developers from future.
Then it can be tested.
Sure - It's done : )
I have tested this item ✅ successfully on dbf0457
I have successfully tested this PR. Thanks @krishnagandhicode!
I have tested this item ✅ successfully on dbf0457
Thanks @krishnagandhicode for the Pull Request.
| Status | Pending | ⇒ | Ready to Commit |
RTC
| Status | Ready to Commit | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-04-15 06:25:19 |
| Closed_By | ⇒ | bembelimen | |
| Labels |
Added:
RTC
|
||
Sorry my fault, missed this PR when deleting the branch.
| Status | Closed | ⇒ | New |
| Closed_Date | 2026-04-15 06:25:19 | ⇒ | |
| Closed_By | bembelimen | ⇒ | |
| Labels |
Removed:
RTC
|
||
| Status | New | ⇒ | Pending |
| Title |
|
||||||
I have tested this item ✅ successfully on 61c51d7
Tested Successfully!
I have tested this item ✅ successfully on 61c51d7
Tested Successfully!
I have tested this item ✅ successfully on 61c51d7
I have tested this item ✅ successfully on 61c51d7
| Status | Pending | ⇒ | Ready to Commit |
RTC
RTC
@Fedik can you please double check.