[#12623] - [Custom Fields] Still no decision about Mustache or similiar
- Closed
- 1 Nov 2016
- Medium
- Build: master
- # 12623
Steps to reproduce the issue
There is still no decision about Mustache or similiar
Actual result
I'v removed Mustache from the core for now. Content plugins and per field output is not working anymore. I'v opened a new PR joomla-projects/custom-fields#135 which reverts the change. This PR is intended as the starting point for a new common parser functionality for content plugins (if somebody has time to do it). At least we don't hold back the custom fields project. Hope this procedure is ok for all.
joomla-projects/custom-fields#12 (comment)
Additional comments
Other way arround proposal is: #11702
| Milestone |
Added: |
||
| Title |
|
||||||
| Labels |
Added:
?
|
||||||
| Title |
|
||||||
| Milestone |
Removed: |
||
brianteeman
- | Labels |
Added:
?
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-11-01 15:20:18 |
| Closed_By | ⇒ | zero-24 |
| Labels |
Removed:
?
|
||
I do hope that the content plugin functionality (regardless of whether it's based on Moustache, or whatever) can be re-introduced, perhaps in 3.8, as it's one of the most powerful features of the custom fields extension.
Maybe but there are serveral PRs out to remove that functionality and there is no decision by the PLT. So i think first we need a decision there before we can implement such a feature and i know that it is no easy descision.
Closing as we are going zo remove that functionality with content plugins completly.