+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Issues with PageIndexing on 3.6

Issues with PageIndexing on 3.6

5 posts, 2 answered
  1. Troy Benedict
    Troy Benedict avatar
    37 posts
    Registered:
    29 Apr 2009
    04 Oct 2010
    Link to this post
    I'm having two issues with SiteFinity 3.6's search control. 

    The first issue - I have a site broken up into several page groups that represent the site's main options.  Within each page group is are numerous pages.  Whenever I specify the ~/default.aspx as the starting node to index the site, I only get results back from the first page group.  None of the other page groups' index pages are included in the search. 

    If I'm not being clear, let me try and illustrate the issue.  Below is a layout of the site.  I've broken it out by sections.
    - "Home" (~/default.aspx) (no sub pages)
    - "Section 1" (10 indexable subpages)
    - "Section 2" (6 indexable subpages)
    - "Section 3" (4 indexable subpages)
    - "Section 4" (5 indexable subpages)


    When I set the Home tab (~/default.aspx) to be the starting node, and re-index the site, I *only* get results for Section 1.  It fails to capture any info from 2, 3, and 4.  However, if I redo the pageindex to specify a starting node for "Section 2" it'll capture all 6 pages.  And here's where my second issue arises.

    Issue Two:
    If I add multiple pageindexes each with their own starting node for Home, Section 1, Section 2..., etc. and reindex the site, I get no results back.   

    To the best of my knowledge the site set up as defaulted. 

    Any suggestions would be greatly appreciated! 
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    04 Oct 2010
    Link to this post
    Hello Troy,

    The index looks inside the staring node HTML and all child nodes of the starting node you have specified. From the structure you have posted it looks like that "Section1", Section2"  etc are not child nodes of "Home" and this is why these pages are not added to the index. The crawler goes through all pages recursively based on the parent. If you want to get results from all pages, just do not set the StartingNode when you set up your index or choose All Pages.

    Greetings,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
    Answered
  3. Troy Benedict
    Troy Benedict avatar
    37 posts
    Registered:
    29 Apr 2009
    04 Oct 2010
    Link to this post
    Thanks for getting back to me so quickly.  I suppose I should have clarified, that the Home tab actually is the parent to all of these children tabs. 

    I have been able to make some progress, and might be making baby steps to determine the overall issue. 

    I've been able to identify something interesting over the past several hours.  It seems that pages ARE getting indexed in the various sections, but the search caps out at 10.   

    I removed two indexed pages from the search for Section 1 (which is 10 pages total, 8 of which are indexed right now), and it pulled through the first two pages from Section 2. 

    If I include indexes for Sections 3 and 4, it'll pull through all of those documents, as their indexed pages total 9.  However, if I add another section it'll only pull through 10 indexed pages. 

    Is there a value limit for the search results that might be causing this issue?
  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    05 Oct 2010
    Link to this post
    Hello Troy,

    There is no limit of the indexed pages or output of the search results., but it is possible that you have some control / code on a pager or master page which stops the index. Generally this occurs that you check for some user identity (User.IsAuthentiated), you use session or call some methods that log out a user like FormsAuthentication.SignOut().

    Greetings,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
    Answered
  5. Troy Benedict
    Troy Benedict avatar
    37 posts
    Registered:
    29 Apr 2009
    05 Oct 2010
    Link to this post
    I figured out the problem. 

    There seemed to have been some confusion between the parameter in the query string for the SiteFinity search indexing: "/Services.aspx?service=Search" and one of our home-built controls.  The other url was appending a "?ProgramID=10" to the url and for whatever reason the indexer was applying that to the control every time I built the index. 

    It works perfectly now. 

    Thanks for your help!

    -- Troy
Register for webinar
5 posts, 2 answered