com_fields is hooking into the onPrepareFinderContent event here https://github.com/joomla/joomla-cms/blob/staging/plugins/system/fields/fields.php#L539. Must be done something different on the save event?

Looking at the supported events in the finder plugins I'd say it's the wrong event to use. But I don't know how finder works. @chrisdavenport is the master chief there 😄

Hook into onFinderAfterSave which is fired from the "Content - Smart Search" plugin when enabled. Check the "Smart Search - Content" (this naming still is goofy as all can be) for other Smart Search specific events that are triggered when the content plugin is enabled.

I'v just tested it and as soon as I'v enabled the "Content - Smart Search" plugin, it worked

@Bakual can you confirm that you had the plugin enabled? From my memory of smart search it makes perfect sense that this would have to be enabled

I think I had it enabled, but can't say for certain.
I did some more tests now (with the plugin enabled 😄).
I can confirm it's updating the fields, but not there are some bugs. Maybe that's what I experienced:

• When pressing "Save" ("apply", not "Save & Close) it doesn't update Smart Search. Even after saving multiple times. It updates as soon as I change another field and save, but then the newly changed field isn't updated.
• When pressing "Save & Close", it doesn't update Smart Search, however when opening the article again and saving again, it updates.

It acts real strange imho and I don't know why that is.

@chrisdavenport can you help out here?

I've had a look at this issue and I've fixed a number of problems and I have it mostly working now (PR to follow). However, the most basic problem is that this line: https://github.com/joomla/joomla-cms/blob/staging/plugins/system/fields/fields.php#L521 is returning the old value for the custom field, rather than the new value. That's why the first save doesn't update the index, but the second one does. Any idea how to fix that?

I guess we can close this one as there is a pr availabke.

If I understand @chrisdavenport right, it doesn't fix it fully. It still only updates on second save.

That's right. If someone can fix $fields = FieldsHelper::getFields($extension . '.' . $section, $tmp, true); so it returns the new field values rather than the old ones, then it could be considered a fix. Until then, I suggest we leave this open.

if Issue isn't fixable Users should get at "Fields" a Message about "Save Article 2 Times to index Field for Search in Frontend" (like in ACL about "Inherited", "Denied", ...).

Closing as there is a pull request. Please test #36747 . Thanks in advance.