Taken from Joomla backend:
php: Linux Humulus 4.11.11-200.fc25.x86_64 #1 SMP Mon Jul 17 17:41:12 UTC 2017 x86_64
dbversion: 5.5.5-10.1.24-MariaDB
dbcollation: utf8mb4_unicode_ci
dbconnectioncollation: utf8mb4_unicode_ci
phpversion: 7.0.21
server: Apache/2.4.27 (Fedora) OpenSSL/1.0.2k-fips PHP/7.0.21
sapi_name: apache2handler
version: Joomla! 3.7.4 Stable [ Amani ] 25-July-2017 11:11 GMT
platform: Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
useragent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
Labels |
Added:
?
|
Category | ⇒ | com_fields Search |
Status | New | ⇒ | Discussion |
The issue is that HTML and the {} code get filtered out for the result. An event can be triggered but it will have a performance impact as every search result will run trough the content plugins. Don't know if we want that.
So the custom fields will always be second class citizens? If we suggest new type of field it is a no-go since nobody wants that, if we ask for equal display in search or on page it is no-go because of performance issues, if we ask about versions it is a no-go for whatever reason. I understand that Joomla! is a open source project and the developers and others do not get paid for working on it.
But it should not be like that. Custom fields are important since they help the authors to better structure the content and to display different information on different pages so we do not have to enter the same content on multiple articles in multiple categories just to get it display for a different purpose. Of course there is a performance impact. But why did you start implementing it if you did not want performance impact?
And perhaps the users are willing to exchange some server power for this feature? To implement it with on/of switch and let the users decide?
I am sorry for the tone of this text. I have full respect for your work you all do for this CMS. It is the result of the frustrations of waiting for such a long time for the custom fields feature and now seeing how it does not meet the high Joomla! standards.
Unsubscribed
Title |
|
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-03-11 21:43:06 |
Closed_By | ⇒ | jwaisner |
Closed_By | jwaisner | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @jwaisner by The JTracker Application at issues.joomla.org/joomla-cms/17294
This discussion has ran its course. Closing this due to lack of activity for many months.
This is the expected behaviour (even if its not the desired behaviour). There is no searching of the fields.
@laoneo Care to expand on this answer