User tests: Successful: Unsuccessful:
Pull Request resolves # .
As it is a valid condition in the XML form for the showon attribute to have something like foo: to display a field only if another field is empty, this should also be possible via the custom fields.
foo: as showon rule into the field in the options tab
OR conditions such as foo:[OR]foo:0 or foo:0[OR]foo:foo!: - the bar field should now only be displayed if the foo field is not empty
bar field will now only be displayed if the foo field is empty.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 | ⇒ | Libraries |
| Title |
|
||||||
I have tested this item ✅ successfully on 6e0e00b
I have tested this successfully... Thanks @LadySolveig! (solving useful things I didn't know we had in Joomla ;) )
I also tested foo:[OR]foo:0 or foo:0[OR]foo: and foo!: which all worked as expected.
@richard67 I assume you meant foo!: and not !foo: (as !foo: did yield the same error message of Invalid field: Showon Attribute) while foo!: saved and behaved in the expected opposite manner of foo:
I have tested this item ✅ successfully on 6e0e00b
Everything works as expected(also verified the edge cases - foo!: and foo:[OR]foo:0, and they saved perfectly).
On a personal note: I recently learned about regular expressions in my Formal Theory of Automata course, so seeing this regex fix in action is really cool.
Thanks @LadySolveig : )
Thank you for testing it, @exlemor and @krishnagandhicode! 💚
I really appreciate your personal note. Keep that curiosity and open-mindedness!
The great thing about open source is that throughout our lives, we’ll keep coming across exciting things that we’d previously only heard about in theory.
| Status | Pending | ⇒ | Ready to Commit |
| Labels |
Added:
bug
PR-5.4-dev
|
||
RTC
| Labels |
Added:
RTC
|
||
✅ Final test before merge with JBT
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-03-31 17:51:17 |
| Closed_By | ⇒ | muhme |
Thank you @LadySolveig for your contribution. Thank you @richard67 for support. Thank you @exlemor and @krishnagandhicode for testing.
@LadySolveig Maybe another additional test for a condition
!foo:would be useful to see if that is not broken?I know, it is covered by the last point "check whether other conditions are working as before".
But maybe it should be explicitly mentioned?