Suggestions for v6

[iantresman]

Export (or view) Advanced search form

When playing around with Categories, I'd lilke an easy way to "export (or view) Advanced search form" so I can be sure that my search form has correctly numbered categories selection fields.

I can't find a way of doing this without performing an index update.

[iantresman]

Search specified document/directory

I would like an easy way to "Search this specific document", or "Search these documents in this directory".

By specifying a filename, directory (or patial path), and ensuring search results URLs match, this could be done. PHP would let me generate the specifed filename easily. Think of the directory or filename as a pseudo-category.

Regards,
Ian Tresman

[iantresman]

Sitemap suggestion

I suppose what you mean is a HTML sitemap. This is something we have considered in the past, but we believe it would need to be fairly configurable in layout and design for it to be really useful. So we have pushed it back as an idea, but we may dust it out again if there's interest.

zoom_pagedata.zdat is already similar to a required HTML site map. Aside from formatting the URL into an <a href> tag, I would just add a <li> tag with various classes indicating the entry's (a) category (b) file type (c) directory level (for nested indentions).

[Ray]

I suppose what you mean is a HTML sitemap. This is something we have considered in the past, but we believe it would need to be fairly configurable in layout and design for it to be really useful. So we have pushed it back as an idea, but we may dust it out again if there's interest.

[isd]

hello,
i would like to have ability of creating clickable links in sitemap for human users and beter seo purposes, something like this tool can do:http://www.xml-sitemaps.com/

thank you ewa

[Ray]

ability to insert image in recomended.

This is already in our list of things for V6.

short url mod_rewrite option for search url like:
http://myweb.com/search/search.cgi?zoom_query=searchedword&zoom_per_page=1 0&zoom_and=0&zoom_sort=0 rewrite for: http://myweb.com/search/searchedword

We can not do this for you. It is dependent on your web server configuration. You have to setup your web server to do this using mod_rewrite in Apache, and something else in IIS.

[isd]

ability to insert image in recomended.

short url mod_rewrite option for search url like:
http://myweb.com/search/search.cgi?zoom_query=searchedword&zoom_per_page=1 0&zoom_and=0&zoom_sort=0 rewrite for: http://myweb.com/search/searchedword

ability to edit indexed titles

you are the best without it but it will be very nice to have some of this options in next relase

thank you ewa

[oraya]

Ah ok, I thought it got over written each time that a new one was created! Ok I follow you now. Sorry it's take so long to get there. I appreciate the time and patience you've put into your replies. I will now paste my searchpage into the default.

Oraya

[Ray]

No you don't understand what I mean, or maybe I am missing something here. I have tried this both ways. Firstly if I re-index a site, and just upload the out put files to the server. Then what I get when I use the search form in the nav bar is the results of the search displayed in the default template search_template.html. This file is created each time you re-index a site is it not? So even if I edited this to incorporate my layout, it would be over written once I used the in-built ftp.

No, the search_template.html file is not created each time you re-index the site. Zoom will never overwrite this file in the output directory. So any changes you make to this file will remain.

Zoom will only create this file in the output directory if it does not already exist. If you remove the file or rename it, then yes, Zoom will recreate it.

This is why it was suggested above that changing the name of "search_template.html" does not achieve anything functional. It really doesn't.

Check the Users Guide chapter on customizing the appearance of your search page. You should be making your changes to the created search_template.html file in the output directory, not creating a different file.

And you should not edit the "settings.php" file ... that's why it says "WARNING: DO NOT EDIT THIS FILE." at the top of the file

[oraya]

The difference between renaming the template file or using a template file with a different name is only semantic. The functional outcome is the same.

No you don't understand what I mean, or maybe I am missing something here. I have tried this both ways. Firstly if I re-index a site, and just upload the out put files to the server. Then what I get when I use the search form in the nav bar is the results of the search displayed in the default template search_template.html. This file is created each time you re-index a site is it not? So even if I edited this to incorporate my layout, it would be over written once I used the in-built ftp.

So... what I am suggesting is that if you had a field in the configurations that allowed you to add a file name that has your layout on it with the <!--ZOOMSEARCH--> included for where you wish the search output to be displayed. It would then not create the default search_template.html, but instead just add your file name to the settings.php

I have tried just uploading the output and as i have already said, then when I search the default zoom search_template is used. No layout no nothing! BUT if I edit the settings.php file before upload so that it knows to use my file, I then get the results displayed in my layout. It just means I have to edit it first before I can upload the files.

Listen don't get me wrong. I like the software, but I would like it even more if I could use the built in ftp. It would be just one less job I would have to do.


Oraya

Ps this has nothing to do with server side includes. I know how to do this... It is about telling zoom don't create a default layout, but instead use this one that has already been created, and just add the file name to the settings.php as the default page to display the results.

[David]

The difference between renaming the template file or using a template file with a different name is only semantic. The functional outcome is the same.

[oraya]

I fully understand what you think you are doing. But it is pointless and doesn't accomplish anything. Changing the name (renaming) of the template file from search_template.html to searchpage.php doesn't change the way the file is used.

You probalby think that renaming the file to have a PHP extension means you can include PHP scripts into the file. But it doesn't work like this. The PHP code will not be executed. If you want to have a PHP based header and footer see this FAQ How can I add server-side scripting (eg. PHP, ASP) to the search template.

No I'm not renaming the default html, it is a totally different file with the

<!--ZOOMSEARCH-->

Added to the page. I don't want to use the html template for the results. The page as in my template is a complete html content copy of the layout that would normally be included, ie header footer, it just has a php extension. Yeah i guess i could just call it searchpage.html it just got the php extension because I'm using a php editor. But that is NOT what I am trying to explain to you. When you index a site, it creates a default template (search_template.html) each time, does it not? And this default is set in the php settings file as the default page for where the results will be dispayed. So if I wanted to use my own html file with my own layout wrapped around the <!--ZOOMSEARCH--> it would still mean I would have to keep changing this in the settings, other wise when someone used the search on the nav bar it would just bring up the blank (apart from the results and form) default html file. There would be none of my site layout included in that file. It would be easier for you to be able to set your own default template for each of your sites in the configuration settings for that site. So when you re-index the site, it would not create the search_template.html file, but instead just add the default you have named into the settings file. ie mytemplate.html, which is already on your server. I could then upload all the required files with no editing needed.

Oraya

[David]

I fully understand what you think you are doing. But it is pointless and doesn't accomplish anything. Changing the name (renaming) of the template file from search_template.html to searchpage.php doesn't change the way the file is used.

You probalby think that renaming the file to have a PHP extension means you can include PHP scripts into the file. But it doesn't work like this. The PHP code will not be executed. If you want to have a PHP based header and footer see this FAQ How can I add server-side scripting (eg. PHP, ASP) to the search template.

[oraya]

I think you are missing something. There is no need to rename the template file. The end user doesn't see the file name and changing the name doesn't have any real benefit. Why are you renaming the file?

I am not renaming it. I have a file of my own! My search template is called searchpage.php when ever i run an incremental index, the settings page has $TemplateFilename set to search_template.html, the default. I would like an option so that in each of the sites configuration to name my own TemplateFilename. So that when the site is indexed it would have my own template named in the settings.php


I have the search box displayed in the bottom bar navigation menu, and the result are displayed in my own result template (searchpage.php). This template includes the site design.

At the moment as I have already explained when I run an incremental update, in the settings it is always the default search_template.html that is set for the TemplateFilename. This means I am unable to use the built in ftp to directly upload the files, as I have to change this in the settings.php to my search page template. Are you following what I mean now! Sorry explaining myself has never been my forte. I know exactly what I mean, but trying to get it into words, well lol......

Best wishes,
Oraya

[David]

I think you are missing something. There is no need to rename the template file. The end user doesn't see the file name and changing the name doesn't have any real benefit. Why are you renaming the file?