i am very interested in this but i don't know what any of that means, could you explain it a bit please.
Tyler Clendenin GSL Solutions 0ld sk3wl ----- Original Message ----- From: "Robert Everland" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 05, 2002 2:36 PM Subject: RE: Indexing a FuseBox Site > DOES ANYONE LISTEN TO ME!!!!!!! > > Index your site as a localhost C:\CFusion\Verity\_nti40\bin\vspider -common > c:\cfusion\verity\common -collection C:\Inetpub\wwwroot\Newweb\verity -start > http://localhost -indinclude * -cgiok -followdup > > > Then do this #replacenocase(URL, "http://localhost";, "http://#HTTP_HOST#"; , > "ALL")#">#TITLE#</a> bada bing, bada boom, almost as good as google, pulls > in page titles, pulls in content and you don't have to worry about crappy cf > stuff. > > Robert Everland III > Dixon Ticonderoga > Web Developer Extraordinaire > > -----Original Message----- > From: Nat Papovich [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, June 05, 2002 2:28 PM > To: [EMAIL PROTECTED] > Subject: RE: Indexing a FuseBox Site > > > > > > So this is leading me to believe that nobody has ever indexed any static > > content (static display fuses) within a Fusebox site? This seems > > very hard > > to believe. > > Jeff - > > You will find that this assumption is essentially correct, with one > modification: "Nobody has ever indexed any static content within a Fusebox > site successfully and easily." There are ways you *could* do it, but the > simpler solution is to create a content library in XML or the DB and do in > the indexing there. > > Here is a response I sent to someone off-list with the very same question > you had: > > // > Using file-based searches with Verity and ColdFusion was the subject of some > heated debate a while ago, and some smarty people put some really serious > time into coming up with solutions, none of which were pretty. > > The easiest solution was to remove all content from files and into the > database. Then, it is easy to make Verity work, since the problem you > identified below doesn't happen. > > If that's not an option, you can add a line like: > <!--- <thispagefuseaction>company.aboutUs</thispagefuseaction> ---> > > in each display page. Then, when Verity finds that page, you can perform > some processing to redirect to the proper fuseaction to display this fuse. > It's a little kludgy depending on how you implement the processing (whether > by using a Verity-specific link, or in application.cfm or something else). > > Good luck, > NAT > > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
