Gaetano Giunta

@pa I think the way it is currently done is simply because of lack of experience in writing init scripts - no other reason...

+1 (apart from remark)

I checked the Solr changelogs from 4.10.1 to 4.10.4, and found nothing that would reflect on ezfind. Also, I have been using version 4.10.4 for a while now on one...

A document describing many of the subtleties of upserts for Contents has been added, will be in upcoming release 6.1

@paulborgermans any update on the status of this? Is it mostly working, were there any road blockers found, or is it just missing some man-hours to be finished?

As part of 5.8, there will be a `--force` flag available for the `migrate` commands. Not 100% there, but I would say 80%...

Hello the 1st solution that comes to my mind is: you could implement a 'fieldHandler' class as helper for the ezenum fieldType, and make it implement the 'FieldDefinitionConverterInterface' interface. You...

Hello. Where you able to find the cause of your problem? If not, I might be able to take a look, but only in case your code is available somewhere...

Long time open with no feedback. Closing

should this be made optional via an ini setting? normally a content in Solr does not carry info about all its grandparents... or does it ?