PassMark Logo
Home » Forum

Announcement

Collapse
No announcement yet.

Question/request

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

  • Question/request

    A few (minor) questions/requests:

    a) The "link back" url configuration option doesn't work correctly if the url already contains a script option (e.g. ..myscript.php?page=search) - search.php will create urls with double ?'s in them (..myscript.php?page=search?zoom_query...). Fixing this involves a simple change to the code in search.php - but am I missing something?

    b) The name/location of the search_template.html file does not seem to be a configurable option. Could it be?

    c) The page navigation bar is placed after the search results. Could the location of this become an option?

  • #2
    Originally posted by AndrewD View Post
    a) The "link back" url configuration option doesn't work correctly if the url already contains a script option (e.g. ..myscript.php?page=search) - search.php will create urls with double ?'s in them (..myscript.php?page=search?zoom_query...). Fixing this involves a simple change to the code in search.php - but am I missing something?
    You're right, this is an issue in the current scripts. We'll make a note of addressing this in a future release.

    b) The name/location of the search_template.html file does not seem to be a configurable option. Could it be?
    That's correct, however, you should not need to ever change the name or location of the "search_template.html" file. First of all, the file should never be accessed directly by the end user. Only the search script should need access to it. Second, if you wish to insert PHP/ASP or any SSI to the template, you should do this via the method documented here:
    http://www.wrensoft.com/zoom/support/faq_ssi.html

    c) The page navigation bar is placed after the search results. Could the location of this become an option?
    I presume you are referring to the list of links for the "Result pages" (eg. "1 2 3 4 Next >>"). While you can not quite place this anywhere you like, you can, to a certain degree, configure its location on your page via CSS.

    For example, the following CSS placed on the "search_template.html" page will position the "Result pages" links 300 pixels down from the top of the page:

    Code:
    .result_pages { font-size: 100%; position: absolute; left: 10px; top: 300px;}
    You can alter the position to suit your page's layout, or increase the spacing between other elements of the page to allow this to fit better.

    While absolute positioning is understandably not ideal, this does allow for some less requested layouts to be possible. A more configurable search page template (which would allow for more elements to be moved around easily) is on our list of things to consider for V6. At the same time however, we're hoping to avoid making the template too complicated for users who are less familiar with HTML and may be using WYSIWYG editors.
    --Ray
    Wrensoft Web Software
    Sydney, Australia
    Zoom Search Engine

    Comment


    • #3
      Originally posted by Ray View Post
      That's correct, however, you should not need to ever change the name or location of the "search_template.html" file. First of all, the file should never be accessed directly by the end user. Only the search script should need access to it. Second, if you wish to insert PHP/ASP or any SSI to the template, you should do this via the method documented here:
      http://www.wrensoft.com/zoom/support/faq_ssi.html
      Thanks - I agree with what you say - but the reason for suggesting this is that we have to integrate Zoom inside another php product, and need to be sure that filenames, etc don't conflict.

      Along those same lines, although the code inside search.php doesn't currently cause any difficulties, it would be better in another round to encapsulate everything inside functions with a clear naming convention, so that we don't accidently clash.

      Comment


      • #4
        We'll keep it in mind for a future version.

        In the meantime, alot of our users who are integrating Zoom within another application are using the CGI version. This avoids any possibility for code conflict since the CGI is executed as a separate process. More info here:
        http://www.wrensoft.com/zoom/support...i.html#ssi_cgi
        --Ray
        Wrensoft Web Software
        Sydney, Australia
        Zoom Search Engine

        Comment

        Working...
        X