The answers to the most frequently asked questions about Makaira.

Which (store) languages are supported?

By default, the initial setup includes ElasticSearch configuration for the following languages: DE, EN, AT, CH, FR, ES, IT and NL

If additional languages are required, the necessary ones can be supplied in consultation with support.

How long does it take for changes to my data (products, categories, etc.) to become visible in the frontend?

In normal operation, the Importer compares the status of the data in the store with that in Makaira 1x per minute. This interval is shortened to a few seconds if required - if there are a large number of differing data records.

How can Makaira be used in a multishop setup?

Currently, the oxfield2shop field is not supported on the Makaira side. However, there are three ways to use the full functionality of Makaira in a multishop setup:

  1. If there are no shop-specific fields except for translations of titles, descriptions or similar, one subshop can be used per language. In this scenario, each language gets its own ElasticSearch index according to the Makaira standard, with the configuration of filters etc. coming from a common Makaira instance. This is possible because in this case the oxfield2shop field is not used.
  2. If individual configurations of the search, filters or similar are required for each subshop, but the dataset is the same across the subshops, a separate Makaira instance can be used for each subshop. These instances share a common ElasticSearch index. This allows you to reduce the load on each subshop during data import, but at the same time make shop-specific settings in Makaira. (Note: Synonyms are an exception in this case, as they are stored directly on the ElasticSearch index).
  3. If shop-specific fields, such as prices, are required in addition to the language, it is possible to use a separate Makaira instance with a separate ElasticSearch index for each subshop. This allows small adjustments in the subshops during the import to ensure that the correct, shop-specific values are transferred. The disadvantage of this variant compared to 1) and 2) is that a large number of import processes run here, which can lead to an increased load on the store systems or databases.

I have been using OXSEARCH until now. Do I still need the OXSEARCH module after switching to Makaira?

Once the complete migration to Makaira is done, the OXSEARCH module is no longer needed and can be removed from the store. The migration path consists of the following steps:

  1. Installing/updating the Connect module
  2. Deactivation of OXSEARCH
  3. If necessary, adapt the templates (filters, autosuggest, additional search results)

Do my changes to the settings in Makaira take effect immediately?

Changes to the search and filter configuration and antonyms take effect immediately.

For synonyms, it may be necessary to update the associated product data, for example as part of a full import.

Is there a possibility to deposit multiple users?

Yes, you can add as many users as you want to Makaira. Simply send an email to the support with the desired email addresses.

Furthermore, it is possible to restrict users to certain instances. This can also be configured by the support per user.

Is there a role/rights management to give certain users certain access rights?

No, unfortunately not yet. So far, only a restriction of instances is possible.

Can attributes contain multiple values?

Yes, attributes can be provided with multiple values. These are simply appended to each other with #.

My new imported filter values are not immediately visible, is something wrong with the data?

By default, Makaira works with a caching of the filter values for 15 minutes. Therefore, changes can take up to 15 minutes after import until Makaira displays them.

The feeds are essential for my store, how can I make sure they work?

If feeds are used for automatic processing in other systems, we offer a notification by mail in case something goes wrong. Contact support if you want to use this option.