|
779 | 779 | <resource>Algolia_AlgoliaSearch::algolia_algoliasearch</resource>
|
780 | 780 | <group id="synonyms_group" translate="label" type="text" sortOrder="10" showInDefault="1" showInWebsite="1" showInStore="1">
|
781 | 781 | <label>Synonyms</label>
|
782 |
| - <comment> |
783 |
| - <![CDATA[ |
784 |
| - <div class="algolia-admin-content"></div> |
785 |
| - ]]> |
786 |
| - </comment> |
787 |
| - <field id="enable_synonyms" translate="label comment" type="select" sortOrder="5" showInDefault="1" showInWebsite="1" showInStore="1"> |
788 |
| - <label>Enable Synonyms Management</label> |
789 |
| - <source_model>Magento\Config\Model\Config\Source\Yesno</source_model> |
| 782 | + <field id="notice" translate="label comment" type="label" sortOrder="10" showInDefault="1"> |
| 783 | + <label>Notice:</label> |
790 | 784 | <comment>
|
791 |
| - <![CDATA[ |
792 |
| - Do you want to manage <a target="_blank" href="https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/?utm_source=magento&utm_medium=extension&utm_campaign=magento_2&utm_term=shop-owner&utm_content=doc-link">synonyms</a> in Magento? |
793 |
| - If not, synonyms will be managed only in <a target="_blank" href="https://www.algolia.com/dashboard/">Algolia's dashboard</a> and won't be overridden by Magento. |
794 |
| - ]]> |
795 |
| - </comment> |
796 |
| - </field> |
797 |
| - <field id="synonyms" translate="label comment" sortOrder="10" showInDefault="1" showInWebsite="1" showInStore="1"> |
798 |
| - <label>Synonyms</label> |
799 |
| - <frontend_model>Algolia\AlgoliaSearch\Model\Source\Synonyms</frontend_model> |
800 |
| - <backend_model>Magento\Config\Model\Config\Backend\Serialized\ArraySerialized</backend_model> |
801 |
| - <comment> |
802 |
| - <![CDATA[ |
803 |
| - <a href="https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/?utm_source=magento&utm_medium=extension&utm_campaign=magento_2&utm_term=shop-owner&utm_content=doc-link#regular-synonyms-default" target="_blank">Synonyms</a> can be defined by a comma-separated list of words that will be considered equivalent by the Algolia engine.<br> |
804 |
| - For instance: <code>tv, television, tv set</code><br> |
805 |
| - Using that set, if a record contains “television” and a user searches for “TV”, this record will be returned. |
806 |
| - ]]> |
807 |
| - </comment> |
808 |
| - </field> |
809 |
| - <field id="oneway_synonyms" translate="label comment" sortOrder="20" showInDefault="1" showInWebsite="1" showInStore="1"> |
810 |
| - <label>One-way Synonyms</label> |
811 |
| - <frontend_model>Algolia\AlgoliaSearch\Model\Source\OnewaySynonyms</frontend_model> |
812 |
| - <backend_model>Magento\Config\Model\Config\Backend\Serialized\ArraySerialized</backend_model> |
813 |
| - <comment> |
814 |
| - <![CDATA[ |
815 |
| - <a href="https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/?utm_source=magento&utm_medium=extension&utm_campaign=magento_2&utm_term=shop-owner&utm_content=doc-link#one-way-synonyms" target="_blank">One-way synonyms</a> |
816 |
| - allow you to define alternative words for a search term, which are not synonyms to each other.<br> |
817 |
| - Let’s take an example: when a user searches for “tablet”, you want him to be able to find iPads and Galaxy Note tablets alike, but you might not want Android tablets to show up when he searches for “iPad”.<br> |
818 |
| - To do this, you’d define a one-way synonym set between <code>tablet</code> (as input) and <code>ipad, galaxy note</code> (as synonyms). When the user types in “tablet”, records containing “iPad” and “Galaxy Note” will be returned. However records containing only “tablet” or “Galaxy Note” won’t be returned if he searches for “iPad”. |
819 |
| - <br> |
820 |
| - <br> |
821 |
| - Algolia offers more synonymys’ types - placeholders and alternative corrections. These types can be managed directly from your <a href="https://www.algolia.com/dashboard" target="_blank">Algolia’s dashboard</a>. |
822 |
| - Any changes you make to placeholders and alternative corrections in Algolia’s dashboard won’t be overridden. |
823 |
| - ]]> |
824 |
| - </comment> |
825 |
| - </field> |
826 |
| - <field id="synonyms_file" translate="label comment" type="file" sortOrder="30" showInDefault="1" showInWebsite="1" showInStore="1"> |
827 |
| - <label>Synonyms File</label> |
828 |
| - <backend_model>Algolia\AlgoliaSearch\Model\Source\SynonymsFile</backend_model> |
829 |
| - <upload_dir config="system/filesystem/media" scope_info="1">algoliasearch_admin_config_uploads</upload_dir> |
830 |
| - <base_url type="media" scope_info="1">algoliasearch_admin_config_uploads</base_url> |
831 |
| - <comment> |
832 |
| - <![CDATA[ |
833 |
| - If you have a large amount of synonyms (more than 1 hundred), you don't have to manually enter them in the inputs above. |
834 |
| - You can upload a <a href="https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/how-to/managing-synonyms-from-the-dashboard/?utm_source=magento&utm_medium=extension&utm_campaign=magento_2&utm_term=shop-owner&utm_content=doc-link&language=php#importing-synonyms-from-a-file" target="_blank">JSON file</a> with synonyms instead. |
835 |
| - <br><span class="algolia-config-warning">⚠</span> |
836 |
| - When you upload a JSON file, all the synonyms settings from above will be ignored and only synonyms from the JSON file will be pushed to Algolia. |
837 |
| - ]]> |
| 785 | + <![CDATA[Configurations related to Synonyms have been deprecated from the Magento dashboard. We advise you to configure synonyms from the Algolia dashboard]]> |
838 | 786 | </comment>
|
839 | 787 | </field>
|
840 | 788 | </group>
|
|
0 commit comments