User tests: Successful: Unsuccessful:
adds a custom field to show a list of all menu items that can be selected and then displayed as a link in the frontend
Install a prebuilt package
or
Install this PR, discover the extension and publish the plugin
Create a menuitem custom field. Check that it shows all menuitems from all menus in the select ;ist and then check on the front end that the link is displayed.
New plugin
Status | New | ⇒ | Pending |
Category | ⇒ | SQL Administration com_admin Postgresql Language & Strings Installation Libraries Front End Plugins |
Labels |
Added:
Language Change
?
|
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Labels |
Added:
?
|
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-07-13 17:40:42 |
Closed_By | ⇒ | roland-d |
Thank you.
So I checked and the Default value
has no use in this field. However there is no toggle we can set to not show it for a specific field. Due to being there and when filled, it is added as XML element to the list of options to render and this crashes because it is not used and as such does not match anything and the default is throw this error message.
Since the default makes no sense here, I will create a PR where the field itself can decide if the Default value
should be shown.
only because we both misread each others comments
Best thing would be to offer the plugin in the JED and not bloat the core.
Why? Then we should remove all the plugins that are for core fields. Honestly that makes zero sense.
Because core has already over 200 extensions when you do a blank installation, which I think is more than enough. Instead of, we should try to push the extension directory.
I have tested this item✅ successfully on b304e06
Hi,
Txs very much Brian for introducing this new Type of Custom Fields!
Note for those who don't know: this follows a question I raised yesterday on the Joomla Facebook Group: https://www.facebook.com/groups/joomlanospam/posts/10158401801610997/
I have tested this successfully (on an existing J4.1 website).
You can see the result on https://subform.joomlacustomfields.org/ (link "Matrioshka" at the bottom of Article 1).
This new Type of Custom Fields can be useful in many cases.
But let me share here my own usecase as it could give ideas to others: suppose you have a Blog View... but when clicking on one of the post you don't want to open the corresponding article... but another Blog View. With other words, you want "nested Blog Views" (ie a kind of "Matryoshka").
Txs again Brian for this (very) quick PR :)
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38244.