Pending

User tests: Successful: Unsuccessful:

avatar krishnagandhicode
krishnagandhicode
4 Apr 2026

Pull Request resolves #47507

  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

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)

Testing Instructions

Navigate to: administrator > content > Articles > create a new article

Actual result BEFORE applying this Pull Request

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 )

Expected result AFTER applying this Pull Request

The Category field shows the preselected value and existing save behavior remains same.

Link to documentations

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

avatar krishnagandhicode krishnagandhicode - open - 4 Apr 2026
avatar krishnagandhicode krishnagandhicode - change - 4 Apr 2026
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 4 Apr 2026
Category JavaScript Repository NPM Change
avatar HLeithner
HLeithner - comment - 4 Apr 2026

@Fedik can you please double check.

avatar hiteshm0 hiteshm0 - test_item - 4 Apr 2026 - Tested successfully
avatar hiteshm0
hiteshm0 - comment - 4 Apr 2026

I have tested this item ✅ successfully on 95041e0

I have observed the before and after mentioned in the testing instructions.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47546.

avatar Fedik
Fedik - comment - 5 Apr 2026

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.

avatar krishnagandhicode
krishnagandhicode - comment - 5 Apr 2026

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.

Thanks for the clarification, @Fedik - Will rework this to a narrower workaround and avoid broad behavior changes

Add a Comment

Login with GitHub to post a comment