If a create a new product i cannot search for it until I have rebuilt the search index, is this correct behavior or maybe I'm doing something wrong?
Our solution is built on Quicksilver. I create and publish a new product and I try to search for it wihtout success.I then run the "Rebuild index" scheduled task and after that the product is searchable in the catalog GUI.Shouldn't the index for internal search update when the product is created or at least when it is published?
Something wrong with my search configuration?
I actually just tried the same thing in the standars Quicksilver with the same behavior. The product is not searchable until the index is rebuilt.If I don't publish the product and rebuild the index it is not searchable.
I suppose you are using the searchprovider? if yes, then the index processor must be running for the newly created entries to be indexed automatically. Otherwise you'll have to build/rebuild the index manually.
Check Commerce manager/Administration/Settings/Search Setting and Recover the index processor if needed (it is probably in Invalid mode now)
That was correct the Indexing Processor State was "Indexing processor state is invalid".I pressed recover and the status changed to Processing. I went for lunch and when I came back it was Invalid again.
Any ideas what that could be?
That is strange. Was the status of the indexing processor "Recovering" or "Processing"?
Recover will try to rebuild the entire index. If it does not succeed then then the status will be Invalid again. But if the status was Processing, that means the recover succeeded.
Hmm - which version are you using? There was a bug that will make the processor "Invalid" when you edit a code of an entry, but that was fixed long ago.
We are running Commerce 9.17.
I just did a test on our test server. The index goes into Valid but as soon as I publish a product it goes into Invalid. Very strange. Any ideas?
Did you have any suggestions for my publishing problem?
It seems to me that there might be issues with your change processors system. However it's vague to know which exactly the problem is. I would suggest you to contact our developer support service. When we have access to your environment (ideally a VM with the site + database) we'll be able to tell more.
Do I understand correctly that you would like to have access to our server to look into the problem?And to give you that I send an email to firstname.lastname@example.org with or problem? Should I point out this thread as a reference?
Yes and yes, I think you should to send an email to that address and include this thread. It might not be handled by me - as I'm not in developer support team - but they will know what to do :)
I solved it. Developer support pointed me to this article:
And that was exactly my problem.
From the post:
The reason was wrong configuation in CMS/Mediachase.Search.config.
The problem was solved by synchronizing configuration in both Mediachase.Search.config (CommeraceManager/CMS) files.
Glad that it helped.