User tests: Successful: Unsuccessful:
Right now if you want to include some custom fields in your plugin you need to include a custom field path in the relative xml file, something like:
<fieldset addfieldpath="/plugins/system/<plugin name>/field">
Documented here: https://docs.joomla.org/Creating_a_custom_form_field_type
This PR leverages this, so custom fields will happily reside inside a folder named field
Why field and not fields?
Singular word help us transition to autoload and namespace
Apply this patch with patch tester
Go to plugins tinyMCE and if you can see a dropdown for the skins you have a successful test:
Also go to Profile and check the Term of service and Date of birth, if dropdown then success:
Check the stats plugin and observe that all fields are correctly rendered/functioning
No backwards compatibility break
We just add one more folder check to the whole stack, so performance degradation should be unnoticeable. (Joomla itself does that hundreds of times for core libraries)
Status | New | ⇒ | Pending |
Category | ⇒ | Fields Plugins |
Labels |
Added:
?
|
This PR has received new commits.
CC: @brianteeman
I have tested this item successfully on 5dbed46
I have tested this item successfully on 5dbed46
Thanks
Status | Pending | ⇒ | Ready to Commit |
RTC - leaving it to the maintainers to decide the milestone
Labels |
Added:
?
|
Milestone |
Added: |
Status | Ready to Commit | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-04-09 13:56:30 |
Closed_By | ⇒ | wilsonge |
Labels |
Removed:
?
|
I have tested this item successfully on 7bcedf1
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9796.