Used Custom Fields to add content to article, Used Manual Display, {field 1} etc... to call the custom field into the article's grid
The fields shows up on the page in frontend and should show in search result
now getting {field x} in my Smart Search's Snippets (see attached)
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-08-19 09:06:51 |
Closed_By | ⇒ | franz-wohlkoenig |
Closed_Date | 2017-08-19 09:06:51 | ⇒ | 2017-08-19 09:06:52 |
Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/17557
closed as stated above. Please reopen if guess isn't correct.
Rel_Number | 0 | ⇒ | 17175 |
Relation Type | ⇒ | Duplicate of |
Please reopen, my comment was just a hint where to search.
Status | Closed | ⇒ | Discussion |
Closed_Date | 2017-08-19 09:06:52 | ⇒ | |
Closed_By | joomla-cms-bot | ⇒ |
Status | Discussion | ⇒ | New |
Closed_Date | 0000-00-00 00:00:00 | ⇒ |
Set to "open" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/17557
Status | New | ⇒ | Discussion |
Any news on this cannot really us custom fields if they do not appear correctly on search results
The issue is that com_finder calls the event with its own context ('com_finder.indexer'). See https://github.com/joomla/joomla-cms/blob/staging/administrator/components/com_finder/helpers/indexer/helper.php#L500
I saw that, but this can be handled in the fields content plugin itself. I thought it would crash as it is run on the back end in the indexer.
The plugin event is called, but it doesn't find any fields due to the wrong context.
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-10-24 10:12:59 |
Closed_By | ⇒ | franz-wohlkoenig |
Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/17557
@afri-can please read https://docs.joomla.org/Bug_Tracking_Process and test on a dev-Enviroment using Patchtester.
If a Pull Request have at least 2 successfully Test Release Lead decide if its merged in next Release.
Guess this one is similar to #17175, the on content prepare event is not triggered.