orphan Page_Nodes showing up in search
My search results are turning up pages that should no longer exist. These pages are either deleted older versions of current pages, or pages that simply do not exist anymore.
A look through the sf_page_node table shows multiple records that simply should not be there -- several records with duplicate titles, and records with titles of pages that no longer exist, which seems to correspond to the errant search results. I believe this to be a remnant of a mass cleaning/restructuring I've performed on the site structure beforehand. However, expected behavior is that when you delete a page in the Pages section, the corresponding page_node record should also be removed from the database.
At any rate, is it safe for me to clear out rogue records from this table? Other than dependent tables, are there other tables that I might need to sift through as well?
Thank you
I would actually hope that is not the case if only to allow me to "undelete" which has been high on my wishlist.
If you use the FluentAPI or Managers can you see those pages still in code?
I do see the pages in code when I do a PagesFacade query = App.WorkWith().Pages().Take(_count_);
Hello,
The search does not make database queries to give you some results. We use Lucene that has its own segment files where the data is stored. Can you to recreate/reindex the website and see whether you will keep getting results to old data. Note that currently the search pipe does not allow you to split results by culture and this is a feature that we are going to have Q2/Q3.
Greetings,
Ivan Dimitrov
the Telerik team