A TYPO3 extension that integrates the Apache Solr search server with TYPO3 CMS. dkd Internet Service GmbH is developing the extension. Community contributions are welcome. See CONTRIBUTING.md for details.
GPL-3.0 License
Published by dkd-kaehm over 3 years ago
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
https://shop.dkd.de/Produkte/Apache-Solr-fuer-TYPO3/
or call:
+49 (0)69 - 2475218 0
Published by dkd-kaehm almost 4 years ago
Like always this release would not have been possible without help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Published by dkd-kaehm about 4 years ago
This is a bugfix-only release that contains only a few bugfixes
Like always this release would not have been possible without help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2020 program:
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by dkd-kaehm about 4 years ago
This is a bugfix-only release that contains only a few bugfixes
Like always this release would not have been possible without help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2019 program:
Special thanks to our premium EB 2019 partners:
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 4 years ago
This is a bugfix-only release that contains only a few bugfixes
Like always this release would not have been possible without help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2020 program:
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 4 years ago
This is a bugfix-only release that contains only a few bugfixes
Like always this release would not have been possible without help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2020 program:
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 4 years ago
We are happy to release EXT:solr 11.0.0.
The focus of this release was the support of TYPO3 10 LTS.
Important: This version is installable with TYPO3 9 and 10 LTS. For TYPO3 9 LTS at least version 9.5.16 is required. EXT:solr 11 requires the usage of the TYPO3 site handling for the configuration of solr.
The legacyMode
that allows the usage of domain records and configuration of solr cores in TypoScript was dropped with EXT:solr 11.
With EXT:solr 11 we provide the support of TYPO3 10 LTS. If you update to EXT:solr 11, make sure, that you are using the TYPO3 site management to manage your Apache Solr endpoints.
Thanks to: Achim Fritz & b13 for the support on that topic
With EXT:solr 11 we support Apache Solr 8.5.1, the latest release of Apache Solr.
To see what was changed in Apache Solr 8.5.x please read the release notes of Apache Solr:
https://archive.apache.org/dist/lucene/solr/8.5.1/changes/Changes.html
Beside the major changes we did several small improvements and bugfixes:
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2020 program:
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund about 5 years ago
This is a bugfix-only release that contains only a few bugfixes
Like always this release would not have been possible without help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2019 program:
Special thanks to our premium EB 2019 partners:
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund about 5 years ago
We are happy to release EXT:solr 10.0.0. The focus of EXT:solr 10.0.0 was, to support the site handling was introduced in TYPO3 9 LTS .
Important: This version is installable with TYPO3 9 LTS only.
Since the development budget is limited at one side and we have other project requests at the other side we could spend less time on the development of EXT:solr.
If you want to support us please consider to sponsor us.
The major new feature of EXT:solr 10 is the support of the TYPO3 site handling. You can now configure the Apache Solr connections along with your TYPO3 site.
To get a typical solr site running you now need only a few settings and can use the site handling user interface for that.
EXT:solr 10 ships Apache Solr 8.2.
Note: The data volume of the Apache Solr Docker container was changed from /opt/solr/server/solr/data
to /var/solr/data/data
this might require changes in your infrastructure configuration.
Most (not all) of the extension scanner violations have been fixed. We hope to get the extension scanner violations cleaned in the next releases.
To simplify the development we've dropped the compatibility for TYPO3 8 LTS. If you need to use TYPO3 8 please use the 9.0.x branch.
To allow external applications to index common information for product's we've added a field for price and image. Along with that we've changed the suggest to render the content of the "image" field instead of "previewImage_stringS", this might require changes in your index configuration.
By default EXT:solr 10 expects the configuration of solr connections and cores in the site handling module, along with your TYPO3 site.
The configuration of the solr connections with your site are available immediatly, so no initialization of connections is required anymore.
The old fashioned setup (domain records and solr connections in TypoScript) are now the legacy mode. If you want or need to use that still, you can enable the legacy mode, with your extension configuration by setting allowLegacySiteMode = 1
. This is only possible when you do not use the site handling at all.
The following things will become standard, and should be preferred and activated/configured as close as possible and in some cases immediately, otherwise the things wil not work or break the whole setup:
plugin.tx_solr.solr
This TypoScript configurations for Constants and for Setup are at least partially obsolete and are ignored on Site Handling activated sites.
All Apache Solr connections must be stored in Site Handling "config.yaml" file for each language.
config.absRefPrefix
The config.absRefPrefix is "obsolete" and must be replaced with Site Handlings "base" or "baseVariants" settings.
Important: The goal of the configuration with your TYPO3 site and the site module UI was to simplify the setup, especially for new users. Therefore, not all options are still possible as before, but the most of them are still possible by editing the yaml file.
There are the following known and wanted limitations:
It is not possible to configure a username and a password for the solr server with the UI. You still have the possibility to add that configuration in the yaml file, in that case make sure that this file is not readable from the web!. Another approach is to configure the usage from the environment variables. To configure a username the setting solr_username_read
or solr_password_read
can be used in the yaml file.
It is not possible to configure a different solr hostname with the UI. If you need that you can still configured that in the yaml file, by using the fallback mechanism.
The fallback mechanism work like that:
Each setting has the following structure solr_{$setting}_{$scope}"
. The scope can be read or write. Every setting can be overwritten for the scope write, if nothing is configured it will fallback to the read setting. Every setting can be defined on the language level, if it is not configured on the language level it fallsback to the global setting.
Example:
base: 'http://solr-ddev-site.ddev.site/'
baseVariants: { }
errorHandling: { }
languages:
-
title: English
enabled: true
base: /
typo3Language: default
locale: en_US.UTF-8
iso-639-1: en
navigationTitle: ''
hreflang: en-US
direction: ''
flag: global
solr_host_read: solr_node_1
solr_core_read: core_en
languageId: '0'
-
title: German
enabled: true
base: /de/
typo3Language: de
locale: de_DE.UTF-8
iso-639-1: de
navigationTitle: ''
hreflang: de-DE
direction: ''
flag: global
solr_host_read: solr_node_2
solr_core_read: core_de
languageId: '1'
rootPageId: 3
routes: { }
solr_enabled_read: true
solr_path_read: /solr/
solr_port_read: 8983
solr_scheme_read: http
solr_use_write_connection: false
The example above shows that you are able to define the setting solr_host_read
on the language level. Since this is a more advanced configuration and the user interface should be kept simple, this can only be configured in the yaml.
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2019 program:
Special thanks to our premium EB 2019 partners:
There are many ways to get involved with Apache Solr for TYPO3:
Support us by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 5 years ago
This is a maintenance release with a few bugfixes and improvements.
Thanks to bibus.ch for sponsoring the work on the feature.
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2019 program:
Special thanks to our premium EB 2019 partners:
Thanks to everyone who helped in creating this release!
In the next release, we will drop the support of TYPO3 8 and focus on the integration into TYPO39. Depending on the funding we would like to support
the integration into the TYPO3 site management and want to allow to configure your Solr site with the TYPO3 site management module.
With the move to the solarium PHP API, we take the first step of the integration. In the next releases, we want to use more parts of the solarium API and also contribute to that API to share the improvements with other PHP projects.
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2019 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 5 years ago
We are happy to release EXT:solr 9.0.0. The focus of EXT:solr 9.0.0 was, to support the latest version of Apache Solr (7.6.0) and to drop the usage of the solrphpclient and use the solarium PHP API instead.
Important: This version is installable with TYPO3 9 LTS, but does not support all features of TYPO3 9 yet. Especially the site handling needs further development in EXT:solr to fully support it with TYPO3 9 LTS. Beside the open tasks in EXT:solr there are also parts left in the TYPO3 core (e.g. when using language fallbacks). In the next release of EXT:solr we want to improve the integration with the site management in TYPO3. Since the development budget is limited at one side and we have other project requests at the other side we could spend less time on the development of EXT:solr by the end of the year. If you want to support us please consider to sponsor us in 2019.
Several new features have been implemented for EXT:solr 9.0.0.
EXT:solr 9.0.0 ships a ready to use docker container with Apache Solr 7.6. This makes new features of Apache Solr available to EXT:solr.
For the communication between EXT:solr we've used the solrphpclient library. This library was not maintained anymore and had several custom modifications. Therefore we made the decision to move to the solarium PHP API.
This brings us the following advantages:
The migration to solarium required several changes in EXT:solr and all add-ons and we will provide compabitility releases for them as well.
With the move to solarium we donated some parts to the solarium API (e.g. the solr core handling). This allows us to remove some redundant logic in EXT:solr in the future.
Thanks:
Pull requests and Links:
Outlook:
By now we use the Queries and Httpclient of solarium, but not the domain classes because this requires additional changes in EXT:solr and solarium.
In the future, we want to get rid of redundant code and use the API where we can and it makes sense and support solarium with the features that we need for EXT:solr.
The current release is installable and useable with TYPO3 9 LTS but not all features are supported.
Currently, it is supported to:
The following parts require additional work and are not supported:
Since backward compatibility to TYPO3 8.7 LTS makes it harder to support the previously mentioned topics. We will drop the support for TYPO3 8 LTS
in the next version and improve the support of those TYPO3 9 LTS features.
Nevertheless, a lot of work was already done for the basic support of TYPO3 9 LTS in the following pull requests:
This patch allows creating data range facets with an open beginning or open end.
By now each site had one solr connection for reading and writing. In most of the cases this good enough when you want to index and search in the same core.
Some setups require a more flexible approach:
With a separation of read and write connections, this is now possible. With these building blocks, you could e.g.
The new setup can be configured like that:
plugin.tx_solr.solr {
read {
scheme = https
host = 127.0.0.1
port = 8983
path = /solr/core_en/
}
write < .read
write {
port = 8984
}
}
For compatibility reasons EXT:solr is falling back to plugin.tx_solr.solr.*
when nothing is configured here:
Important: When you update from EXT:solr 8.1.0 you need to re-initialize your EXT:solr connections.
You could create now a facet item link (add, set, remove) somewhere else in the results view where no facet object is available.
Beside
{s:uri.facet.setFacetItem(facet: facet, facetItem: option)}
you could create a set link now with this vh arguments:
{s:uri.facet.setFacetItem(facetName: 'type', facetItemValue: 'pages', resultSet: resultSet)}
Thanks to Marc Bastian Heinrichs for creating a patch for that.
When you want to exclude facets from the counts of another facet, Apache Solr uses tags and excludeTags to realize that.
With the setting additionalExcludeTags
you can add custom exclude tags for a facet and addFieldAsTag
allows you, to force the creation of a tag for a certain facet.
Thanks to Marc Bastian Heinrichs for creating a patch for that and to in2code for paying for the finalization and documentation.
When you access this argument in your FLUID Template, you need to change that as well.
plugin.tx_solr.solr {
read {
scheme = https
host = 127.0.0.1
port = 8983
path = /solr/core_en/
}
write < .read
write {
port = 8984
}
}
The following code parts have been removed as announced in previous versions of EXT:solr:
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2019 program:
Special thanks to our premium EB 2019 partners:
Thanks to everyone who helped in creating this release!
In the next release, we will drop the support of TYPO3 8 and focus on the integration into TYPO39. Depending on the funding we would like to support
the integration into the TYPO3 site management and want to allow to configure your Solr site with the TYPO3 site management module.
With the move to the solarium PHP API, we take the first step of the integration. In the next releases, we want to use more parts of the solarium API and also contribute to that API to share the improvements with other PHP projects.
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2019 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund about 6 years ago
This release is a bugfix only release.
This release contains the following bugfixes and small changes:
The TranslateViewHelper produces a warning in some TYPO3 installations:
1476107295: PHP Warning: Declaration of ApacheSolrForTypo3\Solr\ViewHelpers\TranslateViewHelper::compile($argumentsName, $closureName, &$initializationPhpCode, TYPO3\CMS\Fluid\Core\Parser\SyntaxTree\ViewHelperNode $node, TYPO3Fluid\Fluid\Core\Compiler\TemplateCompiler $compiler) should be compatible with TYPO3\CMS\Fluid\ViewHelpers\TranslateViewHelper::compile($argumentsName, $closureName, &$initializationPhpCode, TYPO3Fluid\Fluid\Core\Parser\SyntaxTree\ViewHelperNode $node, TYPO3Fluid\Fluid\Core\Compiler\TemplateCompiler $compiler) in /var/www/site/web/typo3conf/ext/solr/Classes/ViewHelpers/TranslateViewHelper.php line 0
This bug has been fixed.
The root_pid in the statistics was not always set properly to the root page of the current site. This is fixed now.
With json facets you should be able to sort the options by a function. In EXT:solr this should be supported e.g. with the following configuration:
pid {
label = Content Type
field = pid
metrics {
newest = max(created)
}
sortBy = metrics_newest desc
}
This was not working because the "metrics_" sortings where filtered, but it is technically possible by solr and therfore we should support it.
Thanks to all contributors:
Thanks to all eb partners:
Special thanks to our premium EB 2018 partners:
Thanks to everyone who helped in creating this release!
It version 9 of EXT:solr we will provide the first integration of the solarium php api and ship the latest Apache Solr version. EXT:solr 9 is scheduled for the end of september.
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2018 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 6 years ago
We are happy to release EXT:solr 8.1.0. The focus of EXT:solr 8.1.0 was, to improve the API for the new EB addon's "solrconsole" and "solrdebugtools".
When solrfluidgrouping is installed the groups are also respected for the top results in the suggest.
This patch extends the hook PageModuleSummary displaying information about the plugins flexform settings in the page module. Now the plugin name will be displayed and linked to the edit form, similar to the default behavior.
The TypoScriptService was moved from extbase to the core and we now use the service in the TYPO3 core.
The implementation of solrconsole required several API changes for the implementation of the commands. These changes have been added with the following pull requests:
We've updated shipped Apache Solr version to 6.6.3
Several issues have been fixed in the documentation to keep it up-to-date.
For the example index configuration for EXT:news, the datetime fields have been added.
Since several versions it is possible to anonymize the ip-address in the statistics. This is now enabled by default.
This setting is not used anymore. It was replaced by a label in fluid in version 7.
Now you can configure custom url arguments in the search that are transported from page to page.
Use the following setting to configure them:
plugin.tx_solr.search.additionalPersistentArgumentNames = foo, bar
When terms get removed because they are stopwords this might have an unwanted impact when the mm condition is evaluated. Setting mm.autoRelax to true fixes this.
See also:
This patch add's signals to the SearchController that allow passing custom arguments to the search view's.
With the suggest there where several issues:
Impact: If you just use the default ViewHelpers and templates you need to change nothing. When you add custom filters to the suggest you now need to pass each filter as an array item of the argument "additionalFilters"
With 8.1.0 we do not officially support TYPO3 9. You can install it on TYPO3 9.3.99 for development and we tried to fix the most important issues during the development but there are already
a few known issues:
https://github.com/TYPO3-Solr/ext-solr/issues?q=is%3Aissue+is%3Aopen+label%3A9LTS
The following pull requests have already been merged in order to optimize the TYPO3 9 compatibility:
The following methods have been marked as deprecated and will be removed in EXT:solr 9.0.0:
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors to this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2018 program:
Special thanks to our premium EB 2018 partners:
Thanks to everyone who helped in creating this release!
In the next release, we want to focus on the move to solarium and the support of the latest Apache Solr version.
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2018 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 6 years ago
This release is a bugfix only release. It contains all patches from 7.5.1 + the update to Apache Solr 6.6.3. If you have the possibility to update to 8.0.x we recommend to do that.
There was a security issue with Apache Solr 6.6.2 in combination with the DataImportHandler. This handler is disabled by default in our configuration and you only need to update when you have enabled the DataImportHandler.
Thanks to all contributors:
Big thanks to our partners that have joined the EB2018 program:
Special thanks to our premium EB 2018 partners:
Thanks to everyone who helped in creating this release!
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2018 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 6 years ago
This is a maintenance release. It contains only bugfixes and small changes
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors for this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2018 program:
Special thanks to our premium EB 2018 partners:
Thanks to everyone who helped in creating this release!
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2018 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 6 years ago
This is a bugfix only release.
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors for this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2018 program:
Special thanks to our premium EB 2018 partners:
Thanks to everyone who helped in creating this release!
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2018 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 6 years ago
We are happy to release EXT:solr 8.0.0. The focus of EXT:solr 8.0.0 was, to improve the user experience in the frontend and backend.
In the following paragraphs we want to summarize the new features that will be shipped with EXT:solr 8.0.0
We've replaced the old jQuery UI based autosuggest with a new suggest (https://github.com/devbridge/jQuery-Autocomplete). The advanced suggest can not only show the suggestions, it can also show a configurable amount of top search results.
When the user clicks on the result, he can directly jump to the result page without opening the search results page.
Thanks:
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1638
Apache Solr offers a JSON API for faceting since several versions. Starting with the options facet we've added the support to use this JSON faceting API in EXT:solr.
The support of the JSON API, in general, allows us to build new features on top of that API, that was impossible before. With the first implementation we've added the following features:
By now an option was simply the value and the count, that reflects the number of documents that belong to that option. At EXT:solr 8.0.0 we've added a TypoScript option that is called "metrics", that allows us to collect and show several metrics from documents that belong to a facet option. Examples of metrics are e.g "sum of downloads", "average price",... These metrics will be available in Option model in the FLUID template and can also be used to sort the facet options.
The following example shows an configured options facet with a configured metric:
plugin.tx_solr.search.faceting.facets.type.metrics {
newest = max(created)
oldest = min(created)
}
In the FLUID template you could use the following code in the facet partial to render those metrics:
<span>
newest: {option.metrics.newest -> f:format.date(format: 'Y-m-d H:i:s')}
</span>
<span>
oldest: {option.metrics.oldest -> f:format.date(format: 'Y-m-d H:i:s')}
</span>
Thanks:
Since we'replaced the whole internal communication from EXT:solr to Apache Solr when options facets are used we are very happy to get your feedback and bug reports when you use the options facets with EXT:solr
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1764
When you have option facets with a lot of options, it would be nice to group those options by a prefix. An example is that you group all options by the starting letter to organize them in tabs:
With EXT:solr 8 we ship the following components that allow grouping your facet options to arrange them as you need them in your template:
Thanks: This feature was sponsored by https://www.linnearad.no/
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1717
In the previous section, the facets get grouped by prefix to organize a large number of options. Another way that you also often see on the web is to allow to filter the options with an additional input box above the facet.
The implementation of that feature is possible just with a partial and a few JavaScript components. To simplify the integration of that feature in a project we ship
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1741
The old templating was created with custom CSS that was shipped with the extension. Since we want to decrease the effort that is required to create a mobile search and many integrators use bootstrap.css we decided to ship bootstrap templates by default. If you want to use another framework or your own custom CSS you are still able to do that with custom templates.
Nevertheless, the mobile search in a TYPO3 introduction installation with bootstrap is much better than before and your effort to adopt it should be reduced.
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1738
In EXT:solr 7.x and below a ping request was done before each search. In EXT:solr 8.0.0 we just catch a failed search and handle the unavailability. This saves up to 30% time because we just need one HTTP request to Apache Solr instead of 2.
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1660
In the previous versions, we've introduced own backend modules that can also be used by regular TYPO3 users to perform several tasks. With EXT:solr 8.0.0 the index inspector will be moved from the common info module to our info module:
Besides the move, we also added the functionality to ReQueue a single document from the index inspector when you have permissions on the index queue module.
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1763
The indexing of pages is now done with the shipped Guzzle client in TYPO3.
Thanks: Thanks to Benni Mack from b13 who has implemented that feature http://www.b13.de/
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1837
When you index a lot of documents you might want to create facets based on patterns that occur in the content.
The cObject SOLR_CLASSIFICATION allows you to do a lightweight classification based on regex patterns that you configure in the index configuration.
The following example shows how SOLR_CLASSIFICATION can be used to map patterns on classes that are indexed into a Solr field that could be used for faceting:
plugin.tx_solr.index.queue.pages.businessarea_stringM = SOLR_CLASSIFICATION
plugin.tx_solr.index.queue.pages.businessarea_stringM {
field = __solr_content
classes {
automotive {
patterns = car,jeep,SUV
class = automotive
}
pharma {
patterns = pharma,doc,medicine
class = pharma
}
}
}
With the configuration above Solr documents get the value "automotive" assigned in the Solr field "businessarea_stringM" when the content contains the term "car", "jeep" or "SUV".
Thanks: Thanks to http://www.bibus.ch who sponsored the implementation of this feature.
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1723
With plugin.tx_solr.search.query.(phrase/bigramPhrase/trigramPhrase).fields you can control what is passed to Solr with the ps,ps2 and ps3 value.
With these phrase fields, you can boost documents where phrases occur in close proximity. This can be very handy when you want to tune your search in terms of relevancy.
Related links:
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1735
With plugin.tx_solr.search.query.tieParameter you can now configure the tie value that is passed to Apache Solr.
This value allows you to configure the impact of low scoring fields to the overall score. 0.0 means, that only high score fields will matter, 0.99 means that all fields have the same impact
Related links:
Thanks: Thanks to Marcus Schwemer and in2code that sponsored and shared that feature.
Related pull request: https://github.com/TYPO3-Solr/ext-solr/pull/1690
TYPO3 8 introduced Doctrine DBAL for database queries and the old API will be removed in TYPO3 9. Since we've used a lot of repositories with custom SQL queries, we had to rewrite a lot of queries.
In EXT:solr we've used the chance to restructure the SQL related code and move them to repositories whenever this was possible.
With EXT:solr 8 every usage of the old database API is removed and we are prepared in that way to be ready for TYPO3 9.
Many parts of the code of EXT:solr deal with queries for Apache Solr that's no surprise :). The corresponding parts in the code especially the Query class had grown over time and reached a huge complexity.
This has several drawbacks:
To get better in that regards our goal is to split the Query into:
With the current state the QueryBuilder does the following to build a Query from the user input:
$query = $queryBuilder->newSearchQuery($rawQuery)
->useResultsPerPage($resultsPerPage)
->useReturnFieldsFromTypoScript()
->useQueryFieldsFromTypoScript()
->useInitialQueryFromTypoScript()
->useFiltersFromTypoScript()
->useFacetingFromTypoScript()
->useVariantsFromTypoScript()
->useGroupingFromTypoScript()
->useHighlightingFromTypoScript()
->usePhraseFieldsFromTypoScript()
->useBigramPhraseFieldsFromTypoScript()
->useTrigramPhraseFieldsFromTypoScript()
->getQuery();
Finally, this allows us to:
With EXT:solr 8.0.0 we will not officially support TYPO3 9 since it is not an LTS release! Nevertheless, we want to stay close to the TYPO3 core and allow the usage in 9 already.
By now we mainly fix Doctrine and Composer related issues and support the dropped "pageslanguageoverlay" table.
So to sum up... EXT:solr 8.0.0 will mainly support TYPO3 8 LTS and we will support TYPO3 9.x a good as we can without losing the backward compatibility to TYPO3 8 LTS.
In the long run we want to be able to use other PHP frameworks for Apache Solr e.g. solarium(http://www.solarium-project.org/). To make this possible, we
need to split the pure Solr query related logic from the TYPO3Solr specific query logic (e.g. accessFilter,...). To get a step closer into this direction, we've extracted
the logic that is required to build a TYPO3 specific Solr query into the QueryBuilder. The pure Solr related query logic remains in the Query class.
Impact:
Beside the query refactoring, that required to remove and change several methods, the following code has been removed:
Hooks:
The following methods have been marked as deprecated and will be removed in EXT:solr 9.0.0
Like always this release would not have been possible without the help from our
awesome community. Here are the contributors for this release.
(patches, comments, bug reports, reviews, ... in alphabetical order)
Also a big thanks to our partners that have joined the EB2018 program:
Special thanks to our premium EB 2018 partners:
Thanks to everyone who helped in creating this release!
In the next release we want to focus on the move to solarium and the support of the lastest Apache Solr version.
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2018 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund over 6 years ago
This is a bugfix only release.
It contains:
Thanks to all contributors:
Big thanks to our partners that have joined the EB2018 program:
Special thanks to our premium EB 2018 partners:
Thanks to everyone who helped in creating this release!
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2017 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund about 7 years ago
This release is a bugfix only release. It contains all patches from 7.0.2 + the update to Apache Solr 6.6.2.
This release is for everyone who needs to stay on TYPO3 7 LTS, if you are using 8 LTS you should update to 7.5.0 when possible.
There was a zero day exploit discovered in Apache Solr that allows to load external entities by manipulating the doctype of the response. The Apache Solr release 6.6.2 fixes this issue. This patch add's the support for Apache Solr 6.6.2 and updates the docker container to be based on Apache Solr 6.6.2.
During the update you should update your Apache Solr server to the shipped and supported version 6.6.2 by using the shipped docker container or using your own install process for apache solr. Just updating the extension is not enough.
A change in phpunit required to update the testcases. This fix was backported to the 7.5.x branch to be able to run all tests.
Big thanks to our partners that have joined the EB2017 program:
Thanks to everyone who helped in creating this release!
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2017 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0
Published by timohund about 7 years ago
This release is a bugfix only release. It contains all patches from 6.1.3 + the update to Apache Solr 6.6.2. This release is for everyone who needs to stay on TYPO3 7 LTS or can not update to 7.x.
There was a zero day exploit discovered in Apache Solr that allows to load external entities by manipulating the doctype of the response. The Apache Solr release 6.6.2 fixes this issue. This patch add's the support for Apache Solr 6.6.2 and updates the docker container to be based on Apache Solr 6.6.2.
During the update you should update your Apache Solr server to the shipped and supported version 6.6.2 by using the shipped docker container or using your own install process for apache solr. Just updating the extension is not enough.
Since the encyptionkey in the testingframework was changed, this needs to be updated in the tests as well.
Big thanks to our partners that have joined the EB2017 program:
Thanks to everyone who helped in creating this release!
There are many ways to get involved with Apache Solr for TYPO3:
Support us in 2017 by becoming an EB partner:
http://www.typo3-solr.com/en/contact/
or call:
+49 (0)69 - 2475218 0