[#18928] - [com_fields] Using {field xx, layout} does not function inside editor custom field
- Closed
- 2 Dec 2017
- Medium
- Build: staging
- # 18928
Steps to reproduce the issue
- Create editor custom field
- Create any other custom field
- In an article, try to use {field n} inside the editor field (where n is ID of the second field)
Expected result
In frontend the second field shows up rendered inside the editor field.
Actual result
In frontend the editor field only prints {field n} instead of actually rendering the second field.
Additional comments
I'm really hoping I overlooked something really obvious and this actually works. If it doesn't work, I'm going to guess that this behavior is intentional. If so it's damn unfortunate and short sighted.
Other plugins already effortlessly work inside editor custom field. It really should behave exactly as the regular content field including using {field n}.
| Labels |
Added:
?
|
||
| Category | ⇒ | com_fields |
| Status | New | ⇒ | Information Required |
What can be done is to trigger the event with a special context where the fields content plugin is handlicg specially. But that sounds for me more than a hack.
Yep indeed sounds hacky.
There is also a risk of producing recursions. Eg if someone adds the custom editor field into a custom editor field
I guess that is just something which can't work properly and thus isn't supported.
Guys, I know I may come off as snarky and complaining as I mostly post here when I run into bugs (from my point of view anyway). If I knew anything about programming I'd like to participate more, but all I can do now is offer opinions which may or may not be worth anything.
Joomla is falling behind times pretty fast as it is. Please don't saw off the remaining legs it's standing on. Perhaps these issues have been solved in Joomla 4 and thus it isn't worth it fixing them in Joomla 3, I can understand that. On the other hand even a hacky solution maybe worth it for an app that is basically nearing end of its life and wont see any major revisions in the future.
You're obviously restricted by past decisions on how Joomla was build. Ideally the regular content field and the build in image and link fields should be custom fields like any other, perhaps with the exception that they can only be disabled, and not entirely deleted.
Custom fields should definitely be able to be added in the content and image tabs in backend. Or in other words those tabs should just be regular Field Groups.
There are so many things just plain wrong with Joomla, but I'm not going to go there now. I've been building websites on Joomla since version 1.5 and I've done a lot of them.
Here's hoping Joomla 4 will take a turn for the better.
Sorry for the tiny rant. ;-) Over and out.
J4 will not make you happy in that case.
I would do so. With reason "known restriction" :)
Agree.
| Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
| Status | Information Required | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-12-02 06:45:45 |
| Closed_By | ⇒ | franz-wohlkoenig |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/18928
closed as stated above.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18928.
Most likely it doesn't work because there is no (or wrong) "context" passed for the content.prepare event in the custom editor field. @laoneo Any thoughts?