Hi,

let me try to explain this, MonoX has few development approaches and your are referring to two of them, one is the UI based development and management through the MonoX administration and one is the manual development by adding and removing pages in the solution. So MonoX will not remove the page documents from the database automatically as it doesn't how did page get removed etc. Yes there should be one utility page that will help you identify the missing pages on the disk and allow you to easily remove the orphan documents, good point and we will see if we can do something about this.

Regarding the "/MonoX/ApplicationData/FullTextIndexes", MonoX used database in order to search trough the documents via search providers, above index is used inside a different search provider the one that will index all the documents on the disk, by documents I mean e.g. PDF uploads etc. This provider needs to be explicitly turned on in the web.config

Let me know if you need more information about this, and we will see if we can implement some kind of utility screen for orphan search.

Thanks for your feedback, it's great as always.

Regards

> there should be one utility page that will help you identify the missing pages on the disk

> and allow you to easily remove the orphan documents, good point and we will see if we can do something about this.
</br> </br>

you could change the pages list to show in red color any broken page URLs (or the whole row, but guess the red URL [and more redish on mouse over or something] points the user to the problem [the missing page / broken URL] exactly mentally). Refreshing the list (think there is such button) would update the colours in case you've manually edited files in between.

BTW, Windows does have shell notifications that one can use to see folder changes (there could even be ASP.net API to wrap that functionality of folder-change-monitoring, but not sure) and could even refresh the list remotely on the browser (say using SingalR), but don't need to go to that extent

Thanks for the pointer to the full-test search functionality, will look into enabling it (does it use Windows Search or the older Indexing Service [think that is usually turned off in the OS though in recent Windows] for that or something for that or some custom engine?)

   <!--<add name="IndexingServiceSearchProvider" type="MonoSoftware.MonoX.SearchEngine.Providers.IndexingServiceSearchProvider, MonoX" Catalogs="MonoXSearch" IndexedFileExtensions=".htm;.html;.pdf;.doc;.rtf;.xml;.xls;.csv;.txt;.pps;.ppt;.docx;.xlsx;"/>-->
</br>
</br>I found this in web.config, guess this is the one you were referring to? Should have more file extensions there (like pptx which is also missing at allowed upload file extensions as I mentioned at other post) and should also check in case more documents from the allowed upload file extensions list are indexable to add to this list too

however, I think the Indexing Service is deprecated (and turned off by default) and Windows Search is not used on Windows. I might be wrong though. Not sure if your provider can tap to the Windows Search service too, or one needs to turn on Indexing Service (apart from Windows Search that they have open by default) to use the provider?

also,

        <!--<add name="LuceneFileSystemSearchProvider" type="MonoSoftware.MonoX.SearchEngine.Providers.LuceneFileSystemSearchProvider, MonoX" IndexingEngineInterval="60" IndexingEngineIndexFolder="/MonoX/ApplicationData/FullTextIndexes" IndexingEngineDocDirectory="/;" IndexedFileExtensions=".htm;.html;.pdf;.doc;.rtf;.xml;.xls;.csv;.txt;.pps;.ppt;.docx;.xlsx;"/>-->
</br>
</br>

looks interesting, guess it means Apache Lucene. Would be nice to have a blog post that speaks about full text search providers and how to set them up in MonoX and Windows