Skip to main content

Changes are not visible in the frontend

If a product is not visible in Magento or changes are not displayed in the frontend, this can have different reasons:

1. Indexes are set to manual​

If an indexer is set to manual, cobby cannot call it. But if the product is changed in the backend of Magento, the manual setting cannot be considered by Magento.

Example: The "Special Price" of a product has been changed. This is also displayed directly on the product page after the saving process. However, the old price is still displayed on the item list. A possible reason for this is that the catalog index is set to manual.

Solution: Please check the setting for the indexes. In the job-log you can see exactly which indexers are built.
Past jobs can be viewed in the Customer Portal.

2. Cache​

Another reason could be that another cache such as Varnish is taking hold.

Checking: By adding a parameter, e.g. to the category page, this assumption can be checked. Usually, parameters are not cached, so adding them will give the correct result.

Another alternative could be a replaced search that is not up-to-date, such as SOLR or ElasticSearch. Often the search functions in M2 installations are exchanged. In this case, it is important to ensure that the new search provider also takes the corresponding events into account. Read more about it here: cobby API requests and events.

Solution: For the Integernet SOLR Extension, for example, there is already a module that takes all events into account.

4. For each attribute and storeview/Corrupt data​

Magento can store different values per attribute and storeview. If a storeview is subsequently removed, the deviating values previously created for the storeview are not automatically removed from the database. If a storeview is subsequently removed, it is possible that there are still data corpses in the system. If the article is now edited for the first time via the Magento backend, Magento saves all values again and deletes these corpses. cobby works more granular here and always really only realizes the change you wanted to make, on attribute and storeview level. This can cause a problem in this particular case, when corrupt data is already present in Magento.

Checking: Please check if there are values in the EAV tables that do not have the storeview 0. These would have to be cleaned up manually.