Tweet
Here is description of possible bug I discovered today.
I created two configuration files; one is for indexing entire site except site news pages and has two starting points, and the second one is only for indexing site news pages and has only one starting point.
The first one's name is zoom.zcfg (default name) and it runs in CGI, and the second one is news.zcfg and runs in ASP, and both of them runs very smooth.
But when I load news.zcfg configuration, under List of start points I can see the starting point of the first config file. I tryed to delete the unvanted start point and re-save the configuration, but when I exit the indexer and enter it again, "the foreign" start point appears so I have to delete it.
So I presumed it should be a bug.
I created two configuration files; one is for indexing entire site except site news pages and has two starting points, and the second one is only for indexing site news pages and has only one starting point.
The first one's name is zoom.zcfg (default name) and it runs in CGI, and the second one is news.zcfg and runs in ASP, and both of them runs very smooth.
But when I load news.zcfg configuration, under List of start points I can see the starting point of the first config file. I tryed to delete the unvanted start point and re-save the configuration, but when I exit the indexer and enter it again, "the foreign" start point appears so I have to delete it.
So I presumed it should be a bug.
Comment