The built-in search tool in Movable Type can be slow and can take a lot of processing power, especially if you have blogs with many entries. When I recently upgraded to version 3.31 of MT, I was dismayed to learn that searches became slower and more processor-intensive (at least on my server). I was forced to disable the mt-search.cgi script, as it was overloading my dedicated server. So I went looking for an alternative. I found a PHP mySQL Fulltext method that worked very fast, and without the CPU problems.

So contacted Iñaki, the creator of this PHP solution, who granted me permission modify the solution and package it up as a Movable Type plugin. I have added a number of features, and I have made significant efforts to make the plugin easy to install and use.

Fast Search is a PHP plugin for Movable Type. This means that Fast Search uses Movable Type's dynamic PHP-based publishing system to display search results. However, you can continue to use static publishing for all of your indexes and archives. Fast Search is fast in part because it uses mySQL fulltext indexing -- basically this means that a search index will be created for the entries in your database, making searches much faster.

Template Tags

Version 1.0 of FastSearch is designed to easily replace the existing search functionality in Movable Type. For example, if you are currently using customized search templates, you can use them with Fast Search, with very few changes in most cases. Many Fast Search template tags have the same names as their CGI counterparts:

• <MTSearchString> - The search string (query) being searched.
• <MTSearchResults> - A container tag that displays search results. Arguments include (all are optional):
• lastn - restricts the search to n results. (example <MTSearchResults lastn="10"> ) The lastn argument, like all arguments for MTSearchResults, can also be specified in the URL (...&lastn=10) or POSTed from a search form)
• offset - used in coordination with lastn, starts M entries from the start of the list. (example <MTSearchResults lastn="10" offset="10"> will display results 11-20)
• order - must be either 'date' or 'relevance', the default is 'relevance'. (example $lt;MTSearchResults order="date"> will provide similar results as the CGI search)
• category - must be a valid category ID for the current blog - restricts the search results to entries from this category.
• google_highlight - if specified, search words will be highlighted. (example <MTSearchResults google_highlight="1"> )
• query - the search string (text) to be searched. In normal use, you would NOT include this argument as part of the <MTSearchResults> tag, rather, it would be specified as a URL paramter (example ...query=search+phrase) or POSTed from a search form.
• <MTBlogResultHeader> - this is container tag that displays content before the search results. (Note: in version 1.0 of Fast Search, you cannot search multiple blogs in the same search)
• <MTBlogResultFooter> - this is container tag that displays content below the search results.
• <MTNoSearchResult> - A container tag that displays its content only if zero results are found. Note that this tag must be used after a <MTSearchResults> container.
• <MTNoSearch> - A container tag that displays its content only if no search phrase was specified.
• <MTSearchCount> - The number of search results displayed. This tag should be used with a <MTBlogResultHeader> or <MTBlogResultFooter> container.
• <MTSearchFirst> - The number of the first search result on the current page. This tag should be used with a <MTBlogResultHeader> or <MTBlogResultFooter>container.
• <MTSearchLast> - The number of the last search result on the current page. This tag should be used with a <MTBlogResultHeader> or <MTBlogResultFooter>container.
• <MTSearchIfNextPage> - A conditional tag that displays its content if there is a subsequent page of search results. This tag should be used with a <MTBlogResultHeader> or <MTBlogResultFooter>container.
• <MTSearchNextPageLink> - Output a URL to the next page of search results. This tag should be used within <MTSearchIfNextPage> tags.

As you may have noticed, most of the tags above are identical to the ones used for the existing CGI-based search results. This is by design, so you will easily be able to cut-and-paste your existing search template code into the Fast Search template, though some minor modifications may be required.

Working Examples:

Here are some working examples you can try. Feel free to try additional search queries and note the speed that searches are performed.

• Mars Rover Blog has over 5,000 entries. Example search: "water on mars". Note that this example shows the default FastSearch template, which is very similar to the default search results template in MT 3.2.
• Seinfeld Blog has over 8,000 entries, 180 of which consist of the episode descriptions and scripts of all 180 episodes. Fast Search powers the Seinfeld Script Search, which is restricted to a single category containing the episodes. Example search: 'bubble boy'

Requirements:

• Movable Type 3.2 or 3.3
• mySQL 4.0.1 or higher

Instructions

1. Download the plugin and expand the zip file.
2. Upload the contents of the 'plugins' folder to the 'plugins' directory of your MT installation (usually something like /cgi-bin/mt/plugins).
3. Upload the contents of the 'php' folder to the 'php' directory (usually something like /cgi-bin/mt/php)
4. Login to the MT admin interface. If you already logged in, choose 'Main Menu'
5. If your are running MT 3.3, you should be redirected to an 'Upgrade' screen at this point. The Fast Search upgrade process will update your database to add a fulltext index to the table in your database where entries are stored. Note that this may take some time if you have many entries, and this will add to the overall size of your database.
6. If you are running MT 3.2, you will not see the upgrade screen (as it is a 3.3 feature), so you need to create the index by browsing to the 'Settings' of a blog where you want to use Fats Search. Choose the 'Plugins' tab then find 'Fast Search' and choose 'Settings'. Now click the link in bold that says "Click here to create or rebuild the FastSearch fulltext index". Again, this may take some time, please be patient. After the index has been created, hit the Back button.
7. Now browse to the 'Publishing' settings tab for the blog, and scroll down to the Setting called "Dynamic Publishing". If the first option, "Build all templates statically", is selected, you should change this setting to "Set each template's Build Options separately" and click "Save Changes" at the bottom of the screen. Otherwise, you don't need to make any changes here.(Note that change this setting will create an .htaccess file in the root path of the blog. Normally you won't notice this and everything will work fine, but if you have an existing.htacces file, you may want to take a look at it to make sure everything looks okay)
8. If you just changed your Dynamic Publishing settings in the previous step, you should now rebuild all files for this blog by choosing "Rebuild Site" from the left menu, then "Rebuild all Files". You should also ensure that you have a "Dynamic Site Bootstrapper" (mtview.php) index template and make sure that it gets built, if it hasn't been built previously.
9. Now return to the Fast Search settings ('Plugins' tab within 'Settings') and check the box to enable Fast Search. You may also want to adjust the settings for Maximum Search Results and logging, then click "Save Changes".
10. Open the Fast Search settings once again and choose "Click here to install the default Fast Search Template." The template will be created and then displayed. This is an dynamic Index template (which can be customized) used to display the search results. (If desired you can also skip this step and create the index template manually, use the template tags as desired, or by cutting and pasting your exisiting search template code)

If you already have search forms on your blog pages, you need to update them to point to the new Fast Search template. For each template that contains a search form, look for the following (or similar):

<form method="post" action="<$MTCGIPath$><$MTSearchScript$>"

...and change it to:

<form method="post" action="<$MTBlogURL>fastsearch"

...save the template and repeat this step for every template that has a search form.

If you want to insert a new search form on your site, or completely replace existing forms, you can use the following:

<form method="get" action="<$MTBlogURL$>fastsearch">
    <label for="query" accesskey="4">Search this blog:</label><br />
    <input id="query" name="query" size="20" />
    <input type="submit" value="Search" />
</form>

Of course you can also add optional fields to the form such as:

<input type="hidden" name="order" value="date" />

....to sort the results by date, or....

<input type="hidden" name="category" value="5" />

...to restrict the search to category_id = 5.

Once you have the search form(s) on you site, rebuild those pages and start searching. You should notice significant speed and resource improvement, especially on blogs with many entries.

Download Fast Search

Non-commercial use - FREE ( although you must include a

Movable Type search results powered by 

<a href="http://mt-hacks.com/fastsearch.html">Fast Search</a>

Also, donations are appreciated:

Commercial use - $97.00

Download Now

,<$MTAjaxRatingVoteCount type="fastsearchdownloads" id="1"$>,0);">
Downloads: <$MTAjaxRatingVoteCount id="1" type="fastsearchdownloads"$> (since 3/6/07)

As always, suggestions and feedback are appreciated. Please reply to this entry.

Note: FastSearch v1.0 is a suitable replacement for most implementations of the built-in search function in Movable Type. However, there are a few features that Fast Search v1.0 does not include. Fast Search v1.0 does not support comment searches, multi-blog searches (searching multiple blogs at the same time), regexp search, case-senstive search, the use of AND and OR operators, and Edit Entry Links). Also, Fast Search v1.0 does not inlcude MT 3.3 search features such as tag search. Some of these features may be supported in future versions -- please let me know what features you would like to see.

Updated: 8/9/06 07:39:00 - added some additonal info to the instructions based on feedback from Patrick.

I highly recommend switching from MT's search to this method, we've been using it in our 16 blogs for months and works really well: searches are much faster for users, and the load on the system is much lower.

1. I have an all-static blog and the mtview.php file failed to be created when switching to "Set each template's Build Options separately". I had to create a static template for "myview.php" containing the following (found here: http://forums.sixapart.com/lofiversion/index.php/t49502.html).

<?php
include('<$MTCGIServerPath$>/php/mt.php');
$mt = new MT(<$MTBlogID$>, '<$MTCGIServerPath$>/mt.cfg');
$mt->view();
?>

2. Setting "Set each template's Build Options separately" caused MT to create an .htaccess file in my blog's directory, and since I use a global .htaccess at my site's root (which does all kinds of redirects under my blog's path), I had to delete that and add the following to my own .htaccess.

RewriteRule ^mt/fastsearch$ /mt/mtview.php [L,QSA]

3. <MTElse> doesn't seem to be supported, so I had to rewrite some things differently.

4. <MTNoSearchResults> must be used after <MTSearchResults>, not before.

5. Really DO rebuild all files, because that will create [redundant] entry data in the mt_fileinfo table, necessary for the PHP dynamic templates. If you have trouble with <$MTEntryPermalink$> or if getting unexpected "Page not found" errors, rebuild.

It took me a while to figure out that last one especially, but otherwise it went ok and my search now works faster than ever!

1. Regarding the mt-view.php file, it seems like you have have deleted this template in the past (because you don't need it for an all static blog). When I installed Fast Search for MT Hacks, I had a similar problem, in which the mt-view.php template was previously set by me to NOt rebuild with indexes, and had never been built. So I had to build manually. Perhaps the plugin could check for these things -- at a minimum, a note about it in the Instructions may be helpful.

2. Yes, setting build options seperately does create that .htaccess file. In most cases, it plays nice with existing .htaccess files, but I have run into cases where I have needed to make modifications to get everything working. I am not sure if this is avoidable, but do like your one-line rewrite rule, which is great for people who only have Fast Search as a dynamic page/template.

3. Regarding <MTElse>, I assume you are using this in conjunction with the <MTSearchIfNextPage> tag? I will look into this, and may be able to add support for this in future.

4. True, <MTNoSearchResults> does need to come after <MTSearchResults>. This seems reasonable to me, as it is mutually exclusive to <MTSearchResults> -- are there cases where there would be advantages to reversing the order? I should at least add a note about this in the instructions.

5. Yes, I had the same confusion and problem intially. It was only after digging in the PHP code for <MTEntryPermalink> that I relaized that it was looking for the link data from the FileInfo table, and that MT creates FileInfo records for every page in your blog, even if only one of them is set to dynamic publishing. Seems a little odd, but the implication is that is important to do a full rebuild of all files after changing your dynamic publishing settings.

Patrick, your implementation looks good. It seems like you customized things to provide multiple-blog search results. I would be interested to hear how you set this up. ;)

1. You must certainly be right, I often delete stuff that I don't need (or think I need!). :)

3 and 4. I was using <MTElse> with <MTNoSearchResults>, so that I could include header and footer text to the results (other than the <MTBlogResultHeader> which I used as a real per-blog header). My previous template was actually sort of like this (simplified):

<MTNoSearchResults>
  Sorry, no matches for "<MTSearchString>".
<MTElse>
  </h1>Search results for "<MTSearchString>".</h1>
  <MTSearchResults>
    <MTBlogResultHeader><h2><$MTEntryBlog$></h2></MTBlogResultHeader>
  ...
  </MTSearchResults>
</MTNoSearchResults>

> Patrick, your implementation looks good. It seems like you customized things to provide multiple-blog search results. I would be interested to hear how you set this up. Wink

Actually I'm doing that with a rather patchy technique. That search.php script does HTTP requests to /mt/fastsearch, /mt/agenda/fastsearch (etc. for each of my blogs) and then outputs the results together. Each blog's fastsearch template is very minimal. You can see one's output here:
http://www.chipple.net/mt/fastsearch?search=test

<MTSearchResults>
    <MTBlogResultHeader>
<h1>Search results for "<MTSearchString>".</h1>
<h2><$MTEntryBlog$></h2></MTBlogResultHeader>
  ...
  </MTSearchResults>
<MTNoSearchResults>
  Sorry, no matches for "<MTSearchString>".
</MTNoSearchResults>

... and the subsequent blogs would omit the <h1> part:

<MTSearchResults>
    <MTBlogResultHeader>
<h2><$MTEntryBlog$></h2></MTBlogResultHeader>
  ...
  </MTSearchResults>
<MTNoSearchResults>
  Sorry, no matches for "<MTSearchString>".
</MTNoSearchResults>

I was wondering if that was your approach to multi-blog search. Perhaps the next version of Fast Search can incoporate multi-blog searching in one form or another...

plugins
--FastSearch
php
--Plugins

Right now the PHP files are in the php folder, and I know I couldn't get the forms to even load and got a bunch of smarty errors until I moved those files into the plugins folder.

Still working on getting it to work properly on my site, but after having trouble with mt-search for a long time, this will make me stupidly happy if I can get it to work :-)

Please let me know if you need any help or advice with getting it working on your server.

I will play around with .htaccess to see if I can come up with some rewrite rules. Intially I was hoping to just override the <MTSearchScript> tag and point it to Fast Search, but the default templates preface this with the <MTCGIPath> tag, which complicates things. That said, there may be some rewrite solutions.

I'm trying to isntall FastSearch. Got to step 6 (Yes, I am on 3.2) and when I click the link I get the following:

Can't call method "do" on an undefined value at /home/u2/dascalargo/html/mt/plugins/FastSearch/FastSearch.pl line 56.

Any ideas?

Please forgive the obvious question: can you confirm that your installation of MT is using mySQL as a data source? If you are not sure, look for an "ObjectDriver" line in your config file (either named mt.cfg or mt-config.cgi).

Yesterday afternoon I decided to try to migrate over to MySQL. A lot of this stuff is groping in the dark, learning as I go along, and I'd done pretty well... until now.

I got MySQL set up, no problem. Started the MT upgrade which transferred everything over, but it bombed out in the middle for some reason. I got some totally non-descript error message -- something akin to, "I'm afraid I can't do that, Dave," with no further explanation. Long story short, the MySQL database was corrupted and my MT password ceased working.

So... I'm starting from scratch, installing MT 3.3. I had been considering doing that anyway -- I originally installed MT a few years ago, when even more of this was trial-and-error for me, then upgraded to 3.2, and then moved the entire install to a new server, so the set-up was in desperate need of a clean-up anyway -- but I always talked myself out of it because of the work involved. Looks like I convinced myself. :D

Bottom line: Once I get MT installed (this time using MySQL), I'm going to try FastSearch again. I look forward to using it.

Sorry to have unnecessarily bothered you with this.

Finally got Fast Search to work with my new install of MT... sort of.

It seems to not see certain words. Bat, Fox, Dog, between, able, two, first, something, and sent are all words that appear in the main body of an entry, but which Fast Search doesn't see. I have rebuilt the site as well as building, rebuilding, and re-rebuilding the fulltext index, and it's always the same words that go unnoticed.

Here's something else I noticed in experimenting. I have the word voice in two entries, both of which Fast Search returns when I search on that word. Fast search finds neither that nor to, but it CAN differentiate between and find the correct entry if I search for the phrases "voice that" and "voice to".

The page can be viewed at http://www.triviot.com/index2.php. It's not live and the subsequent archives and search results pages have no styles applied to them yet.

I generally tend to think I did something wrong in these cases, but this time I'm stumped.

On your default search results page, the courtesy link back to you is broken. Looks like you left off the dot-com.

Sorry to be flooding the comments.

You description above about the search results is normal and to be expected. mySQL fulltext search excludes words less than 4 characters by default -- this is why searches for words like bat, fox, and dog don't work. Furthermore, fulltext also excludes a list of "stop words", which likely include between, able, something, etc. The goal in both cases if to avoid really short or commmon words in order to return the most relevant results.

So you didn't do anything wrong. Some people don't like the fact that you can't search for 3 letter words -- this can be changed in the mySQL config file, but unless you have a dedicated server, this may not be possible.

Yeah, I'd probably want to be allowed to search three-letter words if I had the option -- my database should be small enough that I don't think it would make a big difference in building the file -- but that option isn't available to me. As for the stopwords, I have no problem with the concept that it doesn't include certain words. I mean, in reality I never would search on the words I tested anyway. I did find a copy of the built-in stopwords list (which my server is using), and it helps to see what isn't on the list.

Thanks again. I'm up and running, and fully understanding now. I think I'm finally out of your hair. :wink:

Yes, Fast Search does log searches to the Activity Log. Both 3.2 and 3.3 log formats are supported. Logging is off by default but can be enabled on a per-blog basis (blog-level settings).

Thanks for bringing to my attention the fact that I was not explicit about this above.

Can you provide installation instructions for lighty+fastcgi. We are currently getting 404 errors. Lighty will not recognise .htaccess files

Anish

I've added the Rewrite ruled in my .htaccess file as mentioned by Patrick and I even see the query show up in my the Movable Type activity log, but FastSearch doesn't seem to work for me (even after rebuilding several times to update the fulltext index).

Any thoughts on what I might be doing wrong? The server is Red Hat Linux Enterprise running Apache 2.0 on one of Media Temple's dedicated virtual servers.

.htaccess:
RewriteEngine on
RewriteRule ^/fastsearch$ /mtview.php [L,QSA]

Given your description, you can try two things:

1) Try rebuilding all indexes. However, it sounds like you have done this.

Is the "not found" page a standard apache 404 page, or does it look different? Specifically, I am wondering whether this page is being generated by mtview.php. If it is not, try the following:

2) Check to make sure that Apache is configured to allow the use of .htaccess files in the root directory of the web site. Since this is a dedicated server, you should be able to check and change this, if necessary. I recently came across this issue with a Fast search install. The solution was to add the following to the apache config:

Options Indexes FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all

"AllowOverride All" is the key line above.

If you can provide a link to your search form, I can confirm whether the "not found" page is being generated by mtview.php, or not. If it is, it means that you .htacess is working fine, but the MT "FileInfo" record is not there. In this case, make sure that you have completed step 7, check that your Dynamic publishing settings are set to "Set each template's Build Options separately". As well, make sure that the Fast Search index template is present under Index Templates. If it is not there, revist step 10: Open the Fast Search settings once again and choose "Click here to install the default Fast Search Template." In the Fast Search index template is there, make sure it is set to build dynamically. Then rebuild indexes.

Please let me know if any of the above fixes the problem.

Any suggestions appreciated.

Thanks - I'll be installing it on all of my blogs

It seems like you may be missing the "Dynamic Site Bootstrapper" (mtview.php) index template -- or, this index template has not been built. If you see this under index templates, rebuild it. If not, you need to create it. Name it "Dynamic Site Bootstrapper" and use output file "mtview.php". You can grab the default template from here. This template does not need to be "rebuilt with indexes", but be sure to build it at least once.

Let me know if this doesn't work...

A relief too. Much better search method.

I want to know if you can do me and a lot of others, who are using MT to publish weblogs in non-Latin alphabets, a favour by solving this issue. I'm eager to donate some if you can solve this problem. besides I know a lot of other who are capable of donating more if you end this search nightmare for them.

Waiting to hear good news from you.

SQL/DB Error -- [You have an error in your SQL syntax near 'BOOLEAN MODE) AS score FROM mt_entry, mt_author WHERE entry_blog_id IN (1) AND e' at line 1]

I'm using the MT 3.33 on a MySQL database. Can't figure out what is wrong. I do see the fastsearch page, I do see a search box and I also see the error mentioned above. Is it a MT 3.33 problem? I have rebuilded the fulltextsearchindexthingie and my whole blog.

Oops. I'm using the 3.23.58 version. Going to kick my provider :-)

Thanks!

I noticed there is a next page tag but I was wodering if in the future you plan to include a previous tag or why not some pagination numbers ala Google.

This is such a huge improvement from the search.cgi that I hope Six Apart implements this in their next major release!

Thanks.

Weird question: is there any restricted English words that won't appear in the search results page?

I'm having a problem with the word "associated". I've created an entry with the text below:

"an association of associates. associate. associater. associated. asociated."

and all the words can be found except "associated". I'm quite confused about this.

Do you have any suggestions or has anyone had a similar issue?

For those interested, the link to the full list is below:
http://dev.mysql.com/doc/refman/5.0/en/fulltext-stopwords.html

With respect to a "previous" tag, yes, I think that is something that I could add in future.

Regarding the pagination numbers, this is possible, but I decided against it, as it could affect perfomance. The challenge pagination numbers is that you need to know the total number of search results -- and this would require another "count" query. I'm not a mySQL expert, so I am not sure how much this would impact performance, but with blogs with many entries, it might.

Thanks for coming out with such a useful plugin. I was dissapointed at the speed of search.cgi in MT 3.3 too.

I managed to install the plugin but the fastsearch template breaks with some MT tags. I can get a full list of search results if I only list the <MTEntryTitle> or <MTEntryDate> tag in the template but the results break on the first one if I want to include <MTEntryExcerpt> or <MTEntryBody>. My entries are stored in a MySQL database.

Any thoughts? Thanks a lot!

That's a strange one. Being a php plugin, Fast Search won't support many tags from other non-php plugins, BUT it does support core MT tags such as MTEntryExcerpt and MTEntryBody. Both of these have been tested and work fine in the search results. Can you provide an example of an error message? Or perhaps a link to your search form?

MySQL has a SQL_CALC_FOUND_ROWS keyword that seems to makes this doable in a more efficient way than doing a separate COUNT().

http://dev.mysql.com/doc/refman/4.1/en/information-functions.html#id2826088
Some PHP related comments are here:
http://www.php.net/manual/en/function.mysql-num-rows.php

When I was validating the fast search results page with the html validator at http://validator.w3.org/ I got some errors due to encoding (My page's xhtml).

By encoding the ampersands in block.MTSearchResults.php line 100 as below the validation passes.

$next =
$uri[0]."?query=".urlencode($query)."&category=".$category."&order=".$order."&lastn=".$lastn."&offset=".$offset;

Hope it helps.

Click here for deatils about Fast Search v1.5.

Warning: main(/var/www/vhosts/tracli.net/cgi-bin/mt8/php/mt.php): failed to open stream: Operation not permitted in /var/www/vhosts/tracli.net/httpdocs/test8/mtview.php on line 2

Warning: main(): Failed opening '/var/www/vhosts/tracli.net/cgi-bin/mt8/php/mt.php' for inclusion (include_path='.:/usr/share/pear') in /var/www/vhosts/tracli.net/httpdocs/test8/mtview.php on line 2

Fatal error: Cannot instantiate non-existent class: mt in /var/www/vhosts/tracli.net/httpdocs/test8/mtview.php on line 3

error -_-" why not

SQL/DB Error -- [You have an error in your SQL syntax near ' MATCH (entry_title, entry_text, entry_text_more, entry_keywords ) A' at line 1]

SQL/DB Error -- [You have an error in your SQL syntax near '()' at line 1]

Any idea what might cause this?

I changed the settings to "non-fulltext" and rebuilt the FastSearch Index and now the error looks like this:

SQL/DB Error -- [You have an error in your SQL syntax near 'DISTINCT * FROM mt_entry left outer join mt_placement on ' at line 1]

SQL/DB Error -- [You have an error in your SQL syntax near '()' at line 1]

However, the version of MySQL you're using really is very old, and you might run into other problems.

Parse error: parse error, unexpected \'{\', expecting \')\' in /home/slobokan/public_html/cgi-bin/mt/php/extlib/smarty/libs/Smarty.class.php(1936) : eval()\'d code on line 35

I have not made any modifications to any of the mt files, or the fast search, since installation, and it used to work just fine.

Any ideas?

Smarty error: [plugin] modifier 'textile_2' is not implemented (core.load_plugins.php, line 118)

Yes, it is possible.

Just create a second index template for the Feed template, using the Fast Search template tags as appropriate. You could start with the default RSS or Atom template, or even with the 3.3 search feed template code. Either way, you will have to modify/remove tags as appropriate. A future version of Fast Search may have "built-in" support for search feeds.

Thank you.

My question: does fastsearch support mt 3.34s tags and if so what code would we use to update a tag listing like this:

<MTEntryIfTagged>
<a>TAGS: </a><MTEntryTags glue=", "><a href="<$MTTagSearchLink$>"><$MTTagName$></a></MTEntryTags></MTEntryTags> <MTElse>
</MTElse>
</MTEntryIfTagged>

jim, as stated above, the current version of Fast Search does not support tag searches (MT 3.3+). That may be added in a future version.

Unfortunately MT-Search wasn't up for the extra load and my server started crashing once a week. I installed FastSearch and it's almost perfect. The problem I'm having is that links to domain.com/tag/whatever now get rewritten as domain.com/fastsearch?query=whatever. Is there any way to "beautify" the FastSearch result. I think the short URLs really matter. This may just be my ignorance of how htaccess works, but for the life of me I can't figure this out.

More about how I've pulled this altogether on this immodestly named post on my design blog. Thanks for a great plug-in and thanks everyone for any answers to my problem.
Martin

default is: relevance=1 and google_results=1

The problem with relevance currently is that it looks at all the entries with "all the keywords" then it looks at single keywords. But when grouping the entries, it reads oldest to newest. Most search results give you "latest by date" first since that's what you're looking for, not the oldest post.

That said,the other issue if the URL rewriting make nice looking URLs like domain.com/tag/something. Unforunately, due to the way that MT dynamic publishing works, when you try to do this kind of thing, it does not work as you would expect. This is a pet peeve of mine because it does not support .htaccess URL rewriting like this. In future, I plan to release a modified version of the MT.php file that will support -- if it works, it will enable you do what you are trying to do. Look for this in conjucntion with the release of Fast Search 2.

Also found a slight bug in the fastsearch template.

Right above the search results, if you try to search again, it fails. I changed it to show the following and it works now:

fastsearch.php">
" />
Search this site:

" />

< form method="get" action=" <$MTBlogURL>fastsearch.php">
<input type="hidden" name="IncludeBlogs" value="<$MTBlogID$>" >
<label for="search" accesskey="4"><h3>Search this site:</h3><label>
<p><input id="search" name="search" size="30" value="<$MTSearchString$>" >
<input type="submit" value="Search" >
</form>

Which is why I edited the template itself.

The search form which is given above is fine, but there is nothing about changing the template itself. The above code is actually right in the middle of the fastsearch template.

The only time IncludeBlogs is required is when you are searching one or more blogs other than the blog where fast search template lives.

1. AND!

2. Support for custom mysql entries like those added by Right Fields.

3. Full support for tags.

4. Multiblog results

I'd suggest setting the default search results to AND and 'by date'.

When I just left it as default, it would give blank query strings.

The results aren't displaying by date but not totally by relevance either.

I know this because, for example, when I do a search for "pies." There are five listings that come up. If I update one of the listings and add information about different pies, the order of the search results doesn't change.

If I remove all mentions of pies from a listing, it doesn't show up in the search results any longer.

I added one new listing for a pie shop, with lots of listings of pies, and it shows up at the bottom of the search results.

I guess I'm wondering what FastSearch uses to determine relevance?

Any thoughts? I've been doing lots of tests and am not having much luck. Any help would be greatly appreciated!

" Every correct word in the collection and in the query is weighted according to its significance in the collection or query. Consequently, a word that is present in many documents has a lower weight (and may even have a zero weight), because it has lower semantic value in this particular collection. Conversely, if the word is rare, it receives a higher weight. The weights of the words are combined to compute the relevance of the row. Such a technique works best with large collections (in fact, it was carefully tuned this way). For very small tables, word distribution does not adequately reflect their semantic value, and this model may sometimes produce bizarre results."

It's not Google-quality relevance, but in general it seems to work pretty good.

Would the length of the search word make a difference? When I search for the word "pie" using Fulltext mode, no entries are found even though I have one listing with the word "pie" in it. When I use Fallback, a whole bunch of listings are found that include "pie" as part of other words.

Basically, my client is doing searches on businesses listed on his site and is bothered that the most relevant businesses are showing up closer to the bottom than the top.

ANY help you can give would be greatly appreciated. I've spent a lot of time on this and I feel like I'm getting nowhere.

With mySQL fulltext search, words less than 4 charaters long are not indexed, that's why they show zero results. If you have access to the mySQL config files, you can change this setting. When you use "Fallback", Fast Search will fallback to a non-fulltext search, which does allow 3 letter words, including partial words, etc.

MySQL relevance is what it is, so its tough to change that. If you are on a dedicated server, you could tweak some seeting as mentioned here.

Mark :
Smaty, you would use in your Fast Search template

My Form :

<form method="get" action="<$MTBlogURL$>fastsearch">
<label for="query" accesskey="4">Search this blog:</label><br />
<input name="blogs" type="hidden" value="1,3,6">
<input id="query" name="query" size="20" />
<input type="submit" value="Search" />
</form>

Notice the line in bold above. Edit the 1,3,6 to have the blog_ids of the blogs that you want the form to search.

Support for custom mysql fields would also be great although I understand why this would be a low priority.

A few things to note:

The "non-fulltext" search mode does currently default to AND searching -- only results with all keywords will be returned. And its still pretty fast compared to the built-in search. You should try it. (Fast Search v1.5+)

The fulltext mode also supports AND -type searching, but not by default. You currently need to preface each word with a + to required that keyword to be present. A future version of Fast Search may include an option for searches to default in this way, only displaying results that contain all keywords. Click for a description of the AND/OR operators currently supported.

what is solution?

Does your host allow custom error pages? If so, you may be able to assign mtview.php as the custom 404 page not found error page. This would work. Apart from that, I can't think of a way to do it without .htacess.

The search function is working great and I have been able to customize the templates to some degree but there is one thing I cannot seem to fix and I was hoping you might help me. I use another plugin called Right Fields http://www.staggernation.com/mtplugins/RightFields which allows me to create my own tags.

The challenge is that your Fast Search plugin does not recognize the Right Fields plugin tags that I have created and am displaying in my search results and it throws an error (whereas the original mt-search.cgi does not)... For this reason I cannot use your search at all on my site because the extra Right Fields tags are critical to the design. Also note, if you visit my site, I am using the Google Site search utility, tags are really the only way I am "searching" with your or MT search utilities.

At this point I have reset my search to the old MT version so that I don't get the error. You can visit my search results page at http://www.abstractmall.com/mt/mt-search.cgi?tag=men&blog_id=1 to see how it should or would look. An example of the Right Tags that throw off your results is

Note: all of the t-shirt images and hover images are being brought in with Right Fields, if you could add compatibility for this plugin to your search plugin I would most appreciate it!

Also, how do you get your link to PayPal to land on the "enter credit card" page instead of the login page? I am using PayPal standard and I assume you are too?

I've tried a few different form methods but nothing seems to work. Oh and i've rebuilt a lot and reindexed a few times too.

thanks,

karim

For what its worth, I have some site on both dreamhost and hosting matters, and they are both generally pretty with MT, but I haven't tested Fast Search on either of them (yet).

Searched for ""

No pages were found containing "".

when there was definitely text entered. I've recreated files, reuploaded, checked permissions, etc. So something is causing the search string to vanish.

I am not sure what might be causing this. Can you confirm which version of Fast Search your are using? Version of MT (though I doubt it matters in this case)?

I am very happy with the ease of the plugin, but if it can't use it to search the additional fields I have, I'll have to go back to the default cgi search. :-(

kb, that one is also tough to support, because there are at least 3 different plugins that provide extra fields, and it might be cumbersome to support all three. Perhaps, add-on module could be created for each to support such searches.

We are installing FastSearch, and getting selective or partial results. On certain terms, all the entries are returned, but on other terms, FastSearch only displays a handful of the relevant entries, sometimes none.

Any thoughts for why this may be happening?

I've checked to make sure the search term is more than 3 letters and exactly matches the terms in the entry title or body.

Thanks,

Michele

can i replace that with ur fast search plugin if yes please tell me how to use it .

lookin forward to your answer , thanks alot !