OK, we figured it out:
1) Yes, we do have a separate webpage with that form, which isn't generated
2) It looks like the dr_o variable (formerly known as
DateRanges_date_option) needs to have a number passed in, instead of one of
the text descriptors. We switched it to use dr_o = 13, instead of
DateRanges_date_option="Last 7 days" and now it's cool.
Thanks for the assist!
[mailto:email@example.com]On Behalf Of Bill Moseley
Sent: Monday, March 08, 2004 4:25 PM
To: Multiple recipients of list
Subject: [SWISH-E] Re: Help - upgraded, and now broken
On Mon, Mar 08, 2004 at 01:14:56PM -0800, David VanHook wrote:
> I think that it's basically a problem of variable names -- I've noticed
> on the old version (which still works), the date variables are named
> 'DateRanges_date_option', 'DateRanges_start_mon', etc. But on the new
> version's files (in the DateRanges.pm, etc.), the variables are called
> 'dr_o','dr_s_mon', etc.
Do you have a separate web page with that form -- that is one that's
not generated by swish.cgi?
> I've been going back and forth, trying to figure out where I need to
> these variable names, and I think I've got them all. But it's still not
If it's really just a CGI param name issue you could rewrite parameters
in .swishcgi.conf. There's a callback early on in the process where you
can modify the CGI object.
Bummer about the upgrade change. The other one that caught people is
the change in the index format during the revisions up the release.
Received on Mon Mar 8 14:30:05 2004