User tests: Successful: Unsuccessful:
Right now if you want to include some custom fields in your template you need to include a custom field path in the relative xml file, something like:
<fieldset addfieldpath="/templates/<template 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
edit administrator/templates/isis/templateDetails.xml
and paste at line 49
<field name="testone" class="" type="testone" default="0"
label="test one"
description="test one" />
Create a folder named field
inside administrator/templates/isis
copy testone.php to the folder you just created from https://gist.github.com/dgt41/ec0e2afe879c5d07ffadd2c8a639e1a7
Go to Edit Style for Isis and check if the first field is like the one from the image below
If so you have a successful test!
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 |
Labels |
Added:
?
|
Category | ⇒ | Fields Templates (site) |
Category | Fields Templates (site) | ⇒ | Fields Templates (admin) Templates (site) |
yup!, Thanks
I have tested this item successfully on 6408672
I have tested this item successfully on 6408672
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:45 |
Closed_By | ⇒ | wilsonge |
Labels |
Removed:
?
|
In your test instructions it says create a file called testing.php. Shouldnt that be testone.php?
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9794.