Feeling Lucky
?
[#27736] - [4.0] Subfield - require
- Closed
- 1 Feb 2020
- Medium
- Build: staging
- # 27736
Steps to reproduce the issue
- Create a
custom fieldof typesubfieldwith onesubfieldof type text and set it asrequired.
- Create an article and do not fill text in the in step one created custom field.
Expected result
As the field is required the article should not be saved.
Actual result
The article is saved.
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-01-31 18:39:42 |
| Closed_By | ⇒ | astridx |
astridx
- comment
- 31 Jan 2020
OK. Thanks for the answer. Then you don't see it as a bug.
How do others see it? Am I the only one who expects different behavior? I would disable the require option in the subfield field or switch it to invisible.
If I'm the only one who sees an error here, I'll close the issue.
Fedik
- comment
- 31 Jan 2020
yeah, it may be confusing,
removing require option for this field sounds as not a bad idea
astridx
- comment
- 31 Jan 2020
OK. Then I open it again so that it is not forgotten.
| Status | Closed | ⇒ | New |
| Closed_Date | 2020-01-31 18:39:42 | ⇒ | |
| Closed_By | astridx | ⇒ |
| Title |
|
||||||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-02-01 12:03:07 |
| Closed_By | ⇒ | astridx |
Technically it have a value, that why it saved.
To make it work as you expected:
If the subform are non multiple, then one of its field should be set to "required".