I have added a nodeTypeAlias to a content set (Article Content Set) in the ExamineIndex.config file. When I build locally it appears in the Examine Management panel in the back office. However, when I publish to the web app the index does not update. (My new node type is not added to the list).
Have tried:
Publishing whole app
Restarting web app
Republishing site
Rebuilding index
Creating a page using that doctype
Going to mark as solution as you led me in the right direction. An error in a config .xslt file was pointing the target environment at the wrong Examine.Settings.config file. Once I fixed that it all worked.
Hi Matt
Thanks for your suggestions. Yes, I can see the change made when I inspect the ExamineIndex.config file in Azure and the node type is definitely the same. Indeed when I build locally it’s against the database for this instance (it’s a dev instance).
Examine Index content set not updating
I have added a nodeTypeAlias to a content set (Article Content Set) in the ExamineIndex.config file. When I build locally it appears in the Examine Management panel in the back office. However, when I publish to the web app the index does not update. (My new node type is not added to the list).
Have tried: Publishing whole app Restarting web app Republishing site Rebuilding index Creating a page using that doctype
Nothing works. Any ideas?
Have you verified that the ExamineIndex.config file on your published instance contains the additional nodeTypeAlias?
Perhaps there is something wrong with your deployment process, and the file isn't being updated.
Also double checked that the nodeTypeAlias of the content on your published instance is exactly the same as what's in the ExamineIndex.config?
Going to mark as solution as you led me in the right direction. An error in a config .xslt file was pointing the target environment at the wrong Examine.Settings.config file. Once I fixed that it all worked.
Thanks for your help!
Hi Matt Thanks for your suggestions. Yes, I can see the change made when I inspect the ExamineIndex.config file in Azure and the node type is definitely the same. Indeed when I build locally it’s against the database for this instance (it’s a dev instance).
is working on a reply...