[#43453] - Updating Radio Type Custom Field Removes Selection from Article
- Closed
- 20 May 2024
- Medium
- Build: v5.1.0
- # 43453
Steps to reproduce the issue
Create a Radio Type Custom Field, and add some options
In Article, Select an option from the Custom Field
Go Back to Custom Field and Update the Value of an existing custom field, that was chosen in the Article
Go Back to Article, and see that the Selection is now removed
Additional Test: Changing "Name" of option does not affect the Article.
Video Example: https://youtu.be/UZEk8wuhWW0
Expected result
I would expect that changing a value in a custom field would not affect the article at all.
Actual result
The article selected radio option has been removed, after the update to the custom field radio button value. i can verify also that changing the name of the option does not affect the article.
System information (as much as possible)
attached the systeminfo text
Additional comments
| Labels |
Removed:
?
|
||
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
systeminfo-2024-05-09T15_41_27+00_00.txt
@richard67 - you're right, i did try to upload, but failed.. im in github now.. - Also is it better to upload json or txt?
I would expect that changing a value in a custom field would not affect the article at all.
I would not expect that
This is correct and inteded. If you remove a value - how should it be displayed? Closing this as expected behaviour.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2024-05-20 08:36:12 |
| Closed_By | ⇒ | chmst |
@chmst , the value is not being removed, only updated. It doesn’t make sense to me that it’s intended behavior.
I feel like it’s an article in blog category. If I change the article, doesn’t affect the blog category.
But can understand this being a low priority item or case to really pay attn to.
In your case it might be just changing the value to fix a spelling error but it could also be to change a yes to a no. Thats why its the intended behaviour
@SumCompanyInc Where? If you tried to attach it in our issue tracker, it might have not worked. Please try directly on GitHub.