Home » Forum
  • If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Index only visible text? Must skip "option" source code.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Index only visible text? Must skip "option" source code.

    Never mind. I received an email reply from David Wren and he clued me in. In one place, I had incorrect and incomplete ZOOMSTOP code. In another place, I wrapped the wrong section of ASP code!

    I do have a follow-up question, though. Each time I insert a snippet of ZOOMSTOP code, the indexing-on-demand time seems to slow down. What initially took about 10 minutes is now taking about 25 -30 minutes.

    ---------------

    Is there a way to tell Zoom Search (v6.0.100) to index only visible text? Selecting "page content" appears to trawl through source code. I don't want that.

    As a fix, I tried ZOOMSTOPFOLLOW. But it did not prevent the indexing of product names contained in our "option" source code, e.g.:

    <option value="" selected>Any Category</option>
    <option value="2">Apples</option>
    <option value="3">Artichokes</option>
    <option value="4">Asparagus</option>
    <option value="5">Avocados</option>
    <option value="22">Bell Peppers</option>
    <option value="40">Blueberries</option>
    <option value="7">Broccoli</option>

    See http://www.greengiantfresh.com/new/gg_search.asp?zoom_query=squash&zoom_page=3&zoom_p er_page=10&zoom_and=0&zoom_sort=0

    I only want ZS to index visible HTML/ASP text on the page. As powerful and customizable as the program is, it comes up short on this issue. Any ideas?

    The ASP code which generates the product table is below (ZOOMSTOPFOLLOW code inserted). Am I approaching this problem in the wrong way?

    <!--ZOOMSTOP-->
    <!--ZOOMSTOPFOLLOW-->
    <td width="15%" align="center" valign="top">
    <table width="100%" border="0" cellspacing="1" cellpadding="0" bgcolor="#FFFFFF">
    <%
    Do Until objRs.EOF
    Response.Write "<tr><td><a href=""" & Request.ServerVariables("URL") & "?action=search&category=" & objRs("ID") & """><img src=""images/recipes/icons/cat_" & objRs("ID") & ".jpg"" width=""130"" height=""20"" border=""0"" alt=""Show Recipes for " & objRs("CATEGORY") & """></a></td></tr>"
    objRs.MoveNext
    Loop
    %>
    </table>
    <div align="center">
    <%If Request.Querystring("action") = "view" Then%>
    </div>
    <!--ZOOMRESTARTFOLLOW-->
    <!--ZOOMRESTART-->

    The resulting sidebar table appears as a bunch of stacked bitmapped products images:

    http://www.greengiantfresh.com/new/recipes.asp

    Richard Schletty
    Last edited by rschletty; 02-03-2009, 09:01 PM.

  • #2
    In anything indexing should be slightly faster (or use slightly less CPU time, if the server is the bottleneck) if you are excluding a lot of text from indexing.

    Might it be that you are indexing more pages than before, now you have got your tags sorted out?

    Comment


    • #3
      Slow indexing

      My fault for the slow indexing. I had entered this incorrect tag.

      <!--ZOOMSTARTFOLLOW-->

      Here is what WrenSoft support wrote:

      We had a look at your site and can confirm that it is indexing much slower
      than expected.

      The cause of this is because some of the pages on your site are using
      incorrect tags. For example, this one:
      http://www.greengiantfresh.com/new/products.asp

      Has the tag pair: <!--ZOOMSTOPFOLLOW--> and <!--ZOOMSTARTFOLLOW-->

      Note that it should be <!--ZOOMRESTARTFOLLOW--> for the second tag (RESTART
      not START).

      I noticed that it's corrected on some other pages of your site, but there
      are still many pages which have the incorrect tags, and they are causing the
      slow-down.

      Having said that, we will fix the Indexer so that the incorrect tags should
      not cause such a significant slowdown (it's because it spends too much time
      looking for the missing RESTART tag than necessary that is why it's slow).
      So this should not be a problem in the next build. However, you will still
      need to fix the tags on all the pages for them to take effect properly.

      Comment

      Working...
      X