This can be caused by several reason. Most common causes are:
There may be following issue:
Solr stores value of the filters in its Index. Depending on what filter you change, you may need to re-index few products, categories or whole catalog. Try re-indexing those products where you think filter should be updated.
This can be caused when your trial period is over. If you are running with Live site and you see this message kindly disable Product Listing & Search from nopAccelerate plugins and contact us to purchase license.
When you make changes to any product from nopCommerce administration panel, nopAccelerate Plugin update certain records into “Incremental_Solr_Product” table, which keeps tracks of products whether they are indexed or not into Solr. We update this table on UpdateProduct Event which is triggered when you update product from nopCommerce administration panel.
In cases, when you are updating products outside of nopCommerce administration panel the event is not triggered and nopAccelerate Plugin doesn’t know which products are changed. So the changes you made are not pushed into the Solr Index.
If you are making changes into the Products from some other application then you can make use of nopAccelerate API methods to update records as required. You can find API documentation with sample code into the download folder of the Plugin.
If you are making changes into the Products directly from the SQL, then you can update appropriate records directly into the “Incremental_Solr_Product” table. Here is the very basic explanation on how it can be done:
Schema of the “Incremental_Solr_Product” table:
2. Solr Status
3. Is Deleted
6. In Time
Solr Status field tracks whether the Product has been Indexed or not. When indexing is done, the plugin sets status to Indexed.
IsDeleted field describes whether product is published or not, and whether we should index it or not. Products that are not published or deleted are not indexed and needs to be deleted from Solr Index.
Store field keeps track of product mapping to particular store. One product may be mapped to one or more stores and depending on its mapping Plugin index it to correct Solr Core.
Now, on following events you can update records as following:
On Adding Products from outside nopCommerce Admin Panel
You need to create new record for new product ID, Solr Status should be Pending, and IsDeleted should be False, and Store should be the store where this product is mapped. You need to add products for all the store it is mapped to as IsDeleted false. For stores where this product is not mapped, make sure to keep IsDeleted true.
On Editing / Updating Products from outside nopCommerce Admin Panel
You need to change Solr Status to Pending for such product.
On Publishing, un-published product from outside nopCommerce Admin Panel
You need to change Solr Status to Pending and IsDeleted to false for such product.
On Deleting or Un-publishing Products from outside nopCommerce Admin Panel
You need to change Solr Status to Pending and IsDeleted should be true for this product.
After you made changes to appropriate product records into the table “Incremental_Solr_Product”, the nopAccelerate IDI process takes care for the rest and the updated products will be indexed.
If after new installation or performing an update to the plugin, are not able to access plugin’s configuration page and get similar error to the following:
The controller for path '/Admin/Plugins/SolrCore/SolrAdmin/Configure' was not found or does not implement IController.
Check that the Plugin folder has correct permissions assigned. To verify please go to Systems > Warnings in nopCommerce Admin Panel. You should not have any warning. If you are seeing a warning here, please fix all of them and try again. Moreover, also make sure to Restart application after you make changes.
This can be caused by incomplete uninstall of the plugin only in cases where the specific stored procedure is not dropped during uninstallation. And the next time you’re trying to install the newer version of plugin, on Plugins page, you get following error:
There is already an object named 'SpecificationAttributeOptionFilter_ByCatId' in the database.
To solve this error make a following query to the database to drop that procedure, and try installing Plugin again.
Drop procedure SpecificationAttrbuteOptionFilter_ByCatId
If you face above error, then try increasing Java Heap Space (JVM Memory). Depending on your installation, this can be done in several ways. Please check following:
If you are not sure how to do it yourself, please consider opening support ticket for the same. We’ll be happy to look into it.