Common Issues of Data Synchronization in M1

Issue: Prices and stock are not updating

# Possible Reasons Solutions
1 Magento Cron is not working. If there are some issues with Magento Cron, please setup external Cron (independent of Magento Cron) by following the below guide: https://support.klevu.com/knowledgebase/run-klevu-cron-independent-of-magento-cron//
2 Magento Indexers are not up to date. Please make sure to rebuild Magento Indexers before syncing data to Klevu.
3 The website is using some third-party tool to update the prices and Stock. This involves the execution of direct database queries. As Klevu module relies on updated_at feild of the catalog_product_entity table, In this case, updated products are not synced to Klevu. Please enable the MySQL trigger by following the guide: https://support.klevu.com/faq/faqs/how-to-update-stock-and-prices-while-using-third-party-tool-or-erp/
The immediate solution: Rebuild the Magento Indexers and perform the full Catalog sync to Klevu by executing the below command in the directory <magento-root>/shell/klevu directory:
php sync.php --alldata

 

Issue: Catalog rule taking much time to update from admin

# Possible Reasons Solutions
1 This happens because Klevu module uses the observer to get the products data and change its properties so that it will be synced to Klevu. Time is taken while loading the product data. Please follow the steps given below.

  1. Go to the file <magento-root>/app/code/community/Klevu/Search/etc/config.xml
  2. Comment the below code:
    <catalogrule_rule_save_commit_after>
        <observers>
    <klevu_search_catalogrule_change>
    <type>singleton</type>
    <class>klevu_search/observer</class>
    <method>catalogRulePriceChange</method>
    </klevu_search_catalogrule_change>
    </observers>
    </catalogrule_rule_save_commit_after>
    <catalogrule_rule_delete_before>
        <observers>
    <klevu_search_catalogrule_delete_before>
    <type>singleton</type>
    <class>klevu_search/observer</class>
    <method>catalogRulePriceChange</method>
    </klevu_search_catalogrule_delete_before>
    </observers>
    </catalogrule_rule_delete_before>
    
  3. Please enable the MySQL trigger by following the guide: https://support.klevu.com/faq/faqs/how-to-update-stock-and-prices-while-using-third-party-tool-or-erp/

 

Issue: Images are not updating

# Possible Reasons Solutions
1 It can be the issue with data sync. Please check if the Cron is running or not, and perform full Catalog sync to Klevu after rebuilding the Magento Indexers.
2 The product images are directly replaced on the server and have the same name as that of the previous image. Please follow the steps given below.
Please download generatethum_extenal_script_m1.zip file, extract it and put generatethum_extenal_script_m1.php on the root of Magento and run until it is finished.
Once done, please perform the full Catalog sync to Klevu by selecting “All Data” option as given in the below guide:
https://support.klevu.com/knowledgebase/synchronize-data-with-klevu-search-2/

 

Issue: Preserve layout search relevancy

# Possible Reasons Solutions
1 There is some confliction of third party module with Klevu module on Catalog Search Result page Please apply the changelog given below in Klevu module files.
https://support.klevu.com/wp-content/uploads/2018/11/klevu_conflict_changelog_m1.txt

 

Issue: Out of stock products displaying in search results

# Possible Reasons Solutions
1 The website is using the collection method and has the option “Show Out of Stock Product” set as “No” on the website level. In that case, Klevu has limitation to sync the Out of Stock products. Please apply the attached changelog out_of_stock_issue_m1.txt in the Klevu module files and perform the full Catalog sync to Klevu by selecting “All Data” option as given in the below guide:
https://support.klevu.com/knowledgebase/synchronize-data-with-klevu-search-2/
2 As stated in the first part, it can be Magento Indexing or Cron issue. Please follow the instructions given in the first section “Prices and Stock are not updating”.

 

Issue: Large catalog sync issue

# Possible Reasons Solutions
1 The website is using product Object method to sync the data to Klevu which consumes a lot of memory and very slow in case of larger data. Please use the collection method to sync data to Klevu. Here is the guide for the same: https://support.klevu.com/knowledgebase/enabling-collection-method-in-place-of-product-object-to-sync-data/.
Please note, as collection method relies on Magento Indexers, you need to make sure Magento Indexers are up to date while syncing products to Klevu.