Closed GoogleCodeExporter closed 9 years ago
Original comment by rakeshs101981@gmail.com
on 7 Aug 2009 at 2:17
Original comment by rakeshs101981@gmail.com
on 10 Sep 2009 at 8:44
3 customer requests
Original comment by rakeshs101981@gmail.com
on 18 Sep 2009 at 4:13
Original comment by rakeshs101981@gmail.com
on 23 Sep 2009 at 9:00
Original comment by rakeshs101981@gmail.com
on 25 Sep 2009 at 2:08
The workaround is to find out what those pages are, and add to the "Exclude
patterns"
in connector config and/or GSA's "do not crawl patterns".
Original comment by jeffl...@google.com
on 18 Feb 2010 at 9:28
Two more impacted customers.
Original comment by danth...@google.com
on 18 May 2010 at 10:46
Updated CustomersAffected Tag per danthony's comment.
Original comment by j.dars...@gmail.com
on 19 May 2010 at 2:08
The SharePoint built-in web-services do not provide access to the "Search
Visibility"
configuration but the SharePoint API SPWeb object (that represents to a Site)
does.
We will have to implement a custom web-service to expose the following details:
SPWeb.AllowAutomaticASPXPageIndexing
SPWeb.ASPXPageIndexMode
SPWeb.NoCrawl
The connector will also need extensive modifications to read the configuration
and
act accordingly.
Original comment by j.dars...@gmail.com
on 19 May 2010 at 6:53
Affected customer count is 5, which is the highest among all bugs, so promoting
this
one to a high priority.
Original comment by j.dars...@gmail.com
on 19 May 2010 at 8:50
Original comment by rakeshs101981@gmail.com
on 20 May 2010 at 6:17
Fix details:
--------------
Revision 740:
http://code.google.com/p/google-enterprise-connector-sharepoint/source/detail?r=
740
Revision 757 to revision 762
http://code.google.com/p/google-enterprise-connector-sharepoint/source/detail?r=
762
Original comment by rakeshs101981@gmail.com
on 14 Jun 2010 at 8:36
Original comment by rakeshs101981@gmail.com
on 14 Jun 2010 at 8:36
Original issue reported on code.google.com by
rakeshs101981@gmail.com
on 30 Jun 2009 at 7:48