[SiteSettings] # Prepend site URL with http:// or https:// URLProtocol=http:// # Site index public available. For changes to take effect, the search # index must be updated by running bin/php/updatesearchindex.php IndexPubliclyAvailable=disabled # Search other installations SearchOtherInstallations=disabled [SearchHandler] # DefaultSearchHandler: can be any of standard, simplestandard, ezpublish, heuristic # standard: the Solr standard handler is called with all syntax supported, # searching is done against all searcheable fields # simplestandard: the Solr standard handler is called with all all syntax # supported, searching is done against the aggregated field ezf_df_text # ezpublish: the recommended handler (Solr dismax based) for typical user # searches using keywords without boolean or other operators # except for + (required) and - (excluding) # heuristic: depending on the presence of special characters indicating boolean, # wildcard or fuzzy expressions, either the standard or dismax handler is called DefaultSearchHandler=heuristic [LanguageSearch] # It is possible to search all languages simultaneously, but the common use case is to search only the main language # # Example : # in site.ini : # # [RegionalSettings] # SiteLanguageList[] # SiteLanguageList[]=eng-GB # SiteLanguageList[]=fre-FR # # When SearchMainLanguageOnly is set to 'enabled', only results in the first language # in site.ini[RegionalSettings].SiteLanguageList[] will be returned. # # When SearchMainLanguageOnly is set to 'disabled', results will be returned with respecting # the fallback defined in site.ini[RegionalSettings].SiteLanguageList[] : # Of all matching results, the ones in eng-GB will be returned, and in case no translation in # eng-GB exists for a result, it will be returned in fre-FR if existing. SearchMainLanguageOnly=enabled # Multicore = enabled|disabled # If enabled, each language will be indexed in a distinct solr core in order to # provide better language specific analysis #MultiCore=enabled MultiCore=disabled # Default solr core # This is used for two purposes: # - index languages that aren't mapped to a specific core # - as a hub when searching, since one core must contact all the other ones DefaultCore=eng-GB # Each language must be mapped to its own core # Unmapped languages won't be indexed, so make sure the configuration is # complete # Syntax: LanguagesCoreMap[]= # Example: LanguagesCoreMap[eng-GB]=eng-GB LanguagesCoresMap[] #LanguagesCoresMap[eng-GB]=eng-GB #LanguagesCoresMap[fre-FR]=fre-FR #LanguagesCoresMap[nor-NO]=nor-NO [SpellCheck] #SpellCheck = enabled | disabled SpellCheck=enabled #DefaultDictionary: default only for now, realms (for example per language, or using # external dictionaries) to be supported later # this can also be specied in the spellcheck parameters in search requests DefaultDictionary=default [FacetSettings] # Installation name map. The key is the installation ID, # and the value is the name displayed in the design templates. # # Use this SQL to get the value : SELECT value FROM ezsite_data WHERE name='ezfind_site_id'; # Example: # SiteNameList[] # SiteNameList[3e731797af0a6b79e943eefaf437f956]=eZ.no SiteNameList[] [SolrFieldMapSettings] # List of custom datatype mapping. eZ Publish datatype string is used # as key, and the value if the name of the class to use. # # Example: # CustomMap[eztext]=ezfSolrDocumentFieldText CustomMap[dummy_example]=ezfSolrDocumentFieldDummyExample CustomMap[ezobjectrelation]=ezfSolrDocumentFieldObjectRelation CustomMap[ezobjectrelationlist]=ezfSolrDocumentFieldObjectRelation CustomMap[ezxmltext]=ezfSolrDocumentFieldXML CustomMap[ezmatrix]=ezfSolrDocumentFieldXML # Datatype to field type map. # Since ez find 2.2, this means searching # as for facets, sorting, others mappings may be used DatatypeMap[ezstring]=text DatatypeMap[eztext]=text DatatypeMap[ezboolean]=boolean DatatypeMap[ezdate]=date DatatypeMap[ezdatetime]=date DatatypeMap[ezfloat]=sfloat DatatypeMap[ezinteger]=sint DatatypeMap[ezprice]=sfloat DatatypeMap[eztime]=date DatatypeMap[ezkeyword]=lckeyword # Since ez find 2.2 # Mapping for datatypes to sortable fields # This means usually very little transformations at index time # If not specified, the search mapping is used DatatypeMapSort[] DatatypeMapSort[ezstring]=string # Since ez find 2.2 # For facets, the mapping is also tbe re-used for facet filters # This may be different from normal filtering, which may rather use the # normal search fields types (tokenized fully, stemmed, ...) DatatypeMapFacet[] #DatatypeMapFacet[ezstring]=simpletext #DatatypeMapFacet[ezkeyword]=lckeyword DatatypeMapFilter[] #DatatypeMapFilter[ezstring]=simpletext #DatatypeMapFilter[ezkeyword]=lckeyword # Default field type Default=text [IndexOptions] ## OptimizeOnCommit controls the behaviour of the addObject and deleteObject calls # with respect to Optimizing the Solr Index on commits # If turning this off, a cron job should be set up to schedule optimize actions OptimizeOnCommit=enabled ## DisableDirectCommits: if true, another mechanism must be enabled to do commits: cronjob, # solrconf.xml or by giving CommitWithin a positive value (expressed in milliseconds) DisableDirectCommits=false (default) ## If set to a positive value will add those delays with every addObject call # if set to 0 (default), it will be ignored CommitWithin=0 (default) # DisableDeleteCommits=true|false # Be careful with this option, deleted objects may still show up in search results, leading to (fatal) errors # Make sure you have a frequent commit cronjob enabled if you set it to true to minimize errors DisableDeleteCommits=false ###Boost factors used when indexing #When multiple boost factors match, they are ADDED, not multiplied #be ware of mixin boost factors on class and attribute level: Solr/Lucene does MULTIPLY the class boost factor with the attribute boost factor [IndexBoost] #MetaField: set boost factors on meta fields, boost per field # Metafield: not yet implemented !! MetaField[] #MetaField[name]=2.0 #MetaField[owner_name]=2.0 #ClassBoost: set boost factors on document (object) level #format Class[]= Class[] #Class[user]=3.0 #AttributeBoost: set boost factors on attributes at field level #you can specify the class identifier as optional (!) element for greatest flexibility #If more than attributeidentifier is used, the last one has precedence Attribute[] #Attribute[user/last_name]=2.0 #Attribute[user/first_name]=2.0 #Attribute[title]=1.5 #AttributeBoost: set boost factors on attributes at field level based on their datatype Datatype[] #Datatype[ezkeyword]=3.0 #ReverseRelatedScale: scale factor to use in $boost = $boost + * ReverseRelatedScale=0 #ReverseRelatedScale=0.5 [IndexExclude] #exclude certain objects from indexing alltogether #only classes supported for now ClassIdentifierList[] #ClassIdentifierList[]=folder #ClassIdentifierList[]=secret [SearchFilters] #Search filters to be applied for every query made #Expert settings! #Currently support for one filter type, a raw Solr query string RawFilterList[] #Example to exclude certain classes #RawFilterList[]='meta_class_identifier_s:[* TO *] -meta_class_identifier_s:folder' #Workaround for non indexed hidden nodes #Needed for eZP 4.0 and 4.1 without the cronobs enabled #Set to enabled if this is the case FilterHiddenFromDB=disabled [MoreLikeThis] #Experimental!! #fields to use for query term extraction: proper fields "native", # or "general" which uses the aggregate field ezf_df_t currently (subject to change, best is to have # dedicated aggregator fields with their own analyzers -- omitting stemming for example) ExtractionFields=general #tuning parameters for more like this #minimum term frequency MinTermFreq=1 #Minimum document frequency MinDocFreq=1 #Minimum word length MinWordLength=4 #Maximum word length MaxWordLength=30 #Maximum query terms to extract from the object MaxQueryTerms=10 #Use popularity to boost the query terms BoostTerms=true [HighLighting] # configuration parameters for highlighting SnippetsPerField=1 FragmentSize=200