s is also slightly helpful when common menu items might end up
as search terms.
But, I would agree that in most cases it's better to index the content,
and let the user worry about using good queries. Anyway, how much
common content do
On Wed, Jun 02, 2004 at 12:43:00PM -0500, Timm Murray wrote:
> At 09:45 AM 6/2/04 -0700, Bill Moseley wrote:
> <>
> >> I don't think either solution is particularly difficult to implement,
> >> but scanning the content files directly also lets us have an easier
&
On Wed, Jun 02, 2004 at 11:29:47AM -0500, Timm Murray wrote:
> At 09:22 AM 6/2/04 -0700, Bill Moseley wrote:
> >On Wed, Jun 02, 2004 at 11:08:25AM -0500, Timm Murray wrote:
> >> At 09:01 AM 6/2/04 -0700, Bill Moseley wrote:
> >> <>
> >> >Spider your co
On Wed, Jun 02, 2004 at 11:08:25AM -0500, Timm Murray wrote:
> At 09:01 AM 6/2/04 -0700, Bill Moseley wrote:
> <>
> >Spider your content instead. Does htdig have anything like
> > ?
>
> We discussed spidering and my boss is against the idea. I personally would
&
gt; htdig:// with a filter program that will convert the templates into text
> for indexing.
Spider your content instead. Does htdig have anything like
?
If not, you can use swish-e (http://swish-e.org) and then wrap your
headers, footers and menus in ....
--
Bill Mose
> (a missing required field, for example) are
> "carried through" ... that is, the form is regenerated,
> and any fields filled out in the first submission
> retain their respective values at the next iteration.
Yep, that's sticky forms. Use HTML::FillInForm and you
be a score of 1000.
I feel like those are display issues -- the web designer might want to use
10 stars, or a bar graph. So is there a way to accomplish this in the
template directly based on the rank, instead of requiring a change to the
code that creates the template variables?
Thanks,
--
Bill M
g the file name
of the template. Then a quick view/source in the browser would help us
know what template needs, eh, fixing.
Any tricks to do this? I was trying to avoid adding a comment directly
into each of the templates as they may get moved around in the template
directory structure.
Thanks
