yams-discuss Mailing List for YAMS
Brought to you by:
modred
You can subscribe to this list here.
1999 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2000 |
Jan
(7) |
Feb
(1) |
Mar
(25) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Garth S. <ga...@al...> - 2000-05-01 11:25:10
|
The Mail::Sendmail module is available from CPAN (www.cpan.org) or can be installed from the commnad by running perl -MCPAN -eshell and at the prompt type install Mail::Sendmail Garth On Sun, 30 Apr 2000, David Jackson wrote: > Can someone please help. > > I am setting up Yams and I don't have the Sendmail.pm it is not located in > the tar. Can someone please e-mail a the Sendmail.pm. I have had to add the > modules by using the use lib 'eg/eg/2'; > > When I do a debug it says it cannot find the Sendmail.pm > > Sorry if this is a stupid question and I have missed something. > > Thanking you in advance > David Jackson > > _______________________________________________ > Yams-discuss mailing list > Yam...@li... > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > |
From: David J. <dj...@vi...> - 2000-04-29 15:58:53
|
Can someone please help. I am setting up Yams and I don't have the Sendmail.pm it is not located in the tar. Can someone please e-mail a the Sendmail.pm. I have had to add the modules by using the use lib 'eg/eg/2'; When I do a debug it says it cannot find the Sendmail.pm Sorry if this is a stupid question and I have missed something. Thanking you in advance David Jackson |
From: Greg L. <gl...@me...> - 2000-03-19 18:42:22
|
Dear Sirs: Please excuse the intrusion on your list, but I think you'll agree that this is an issue that warrants all of our attention. I'm sure that you're aware that Amazon.com has been issued a patent on the very simple feature of using a cookie to place an order. Their application date was September 1997. As a developer in this area, you probably were ahead of them in developing this simple capability. I'm trying to organize knowledgeable software engineers to show how ridiculous this patent is, and to strike a blow against the entire software patent process. There is a discussion going on in misc.int-property where a lawyer has challenged software engineers to publish the prior art that proves this patent is invalid. If we can do so, he has offered to represent us for free in the reexamination process. Any help that you can provide that proves that you knew about this technique prior to Amazon's patent would be greatly appreciated. Ideally, the prior art would be in the form of magazine articles, open source software with copyright dates, textbooks, etc. It would be particular useful if your product had this feature before they applied for their patent and you were using it in commerce. Of course, you can ignore this request and decide whether or not Amazon will be coming after *you* next. --------------------- Greg Leman President Metagenix, Inc. 1800 W. Martin Luther King Pkwy Suite 101 Durham, NC 27707 http://www.metagenix.com |
From: Pat E. <pa...@gn...> - 2000-03-18 01:08:37
|
the CVS repository at https://sourceforge.net/cvs/?group_id=64 is now up to date with both yams 0.6.2 and the pre-release version of the sgml based Yams documentation[1]. If you are interested in seeing what's happening with yams between releases, this is a good place to look. Hopefully using cvs will help let people who are interested in fixing or enhancing Yams get their hands dirty and roll their own patches back in. -pate [1] I'd mentioned some time ago that I was going to work on a howto, this is the fruit (so far) of that effort. It includes a modified README, and a very pre-release FAQ. |
From: Derek C. <der...@ma...> - 2000-03-17 21:36:56
|
That's ok, I know that everyone makes dumb mistakes at times. But, I am selecting the right month and year. I have a product that is dated 2000-02-14, has a status of shipped, shipped date of 2000-03-17, order status full shipment, and a charged status of paid. This is the one that I am using for testing and it doesn't show up in Feb 2000 or March 2000. All I get is zeros. Derek Garth Sainio wrote: > > On Fri, 17 Mar 2000, Derek Carr wrote: > > > Well, to tell you the truth I didn't even know that it had been > > released. There wasn't any email sent to the announce list. But any > > ways, I have been following the list and had made the previous changes > > by adding CGI->header and got it working. However, I did just do the > > upgrade and yes it fixed things. Thanks for checking. I am guessing > > that the cgi script for the search feature is the same as the one that > > was posted to the list previously, is this true? > > There was an announcement to both the discuss and announce lists. The > cgi-script in the distribution is the same one that was posted tot he > list. > > > > > Now, the only thing that I still can't get working is the Revenue > > Reports in the admin utility. It shows zeros for everything, and I do > > have finished sales in there. I forget the exact term that is > > specified, but they're there. > > I hate to ask this, but are you sure you are selecting the revenue report > for the correct month? Do the orders have a status of either FULL OR > PARTIAL SHIPMENT? Do the items have a status of SHIPPED? > > > > > Oh, and one last thought, I just noticed the cron scripts in the new > > release. What are these for, and when are the supposed to be scheduled? > > check_subs.pl can be used to warn your users of an expiration that is > about to expire and remove.pl removes expired users from the appropriate > tables once a subscription expires. They are designed to be run daily. > > Garth > |
From: Garth S. <ga...@ap...> - 2000-03-17 17:55:23
|
On Fri, 17 Mar 2000, Derek Carr wrote: > Well, to tell you the truth I didn't even know that it had been > released. There wasn't any email sent to the announce list. But any > ways, I have been following the list and had made the previous changes > by adding CGI->header and got it working. However, I did just do the > upgrade and yes it fixed things. Thanks for checking. I am guessing > that the cgi script for the search feature is the same as the one that > was posted to the list previously, is this true? There was an announcement to both the discuss and announce lists. The cgi-script in the distribution is the same one that was posted tot he list. > > Now, the only thing that I still can't get working is the Revenue > Reports in the admin utility. It shows zeros for everything, and I do > have finished sales in there. I forget the exact term that is > specified, but they're there. I hate to ask this, but are you sure you are selecting the revenue report for the correct month? Do the orders have a status of either FULL OR PARTIAL SHIPMENT? Do the items have a status of SHIPPED? > > Oh, and one last thought, I just noticed the cron scripts in the new > release. What are these for, and when are the supposed to be scheduled? check_subs.pl can be used to warn your users of an expiration that is about to expire and remove.pl removes expired users from the appropriate tables once a subscription expires. They are designed to be run daily. Garth > > Didn't mean to overwhelm you with questions, sorry. > > Derek > > > pat eyler wrote: > > > > Derek, > > does 0.6.2 fix things for you? > > > > -pate > > > > >From: Derek Carr <der...@ma...> > > >To: Pat Eyler <pa...@gn...> > > >CC: yam...@li... > > >Subject: Re: [Yams-discuss] yams 0.6.1 bug > > >Date: Wed, 15 Mar 2000 16:03:13 -0500 > > > > > >I tried this and the drop-down lists still don't appear. Any thoughts? > > >I did implement the other fixes discussed for the search feature and > > >that worked. But, I still can't get these departments to show up. I > > >get the following error still: > > > > > >[Wed Mar 15 16:08:51 2000] [error] [client 192.168.3.1] unable to > > >include "/cgi\ > > >-bin/commerce/shop/toplevel.pl?type=department" in parsed file > > >/home/httpd/html\ > > >/commerce/shop/index.shtml > > >[Wed Mar 15 16:08:53 2000] toplevel.pl: Use of uninitialized value at > > >(eval 14)\ > > > line 27. > > >[Wed Mar 15 16:08:53 2000] [error] [client 192.168.3.1] malformed header > > >from s\ > > >cript. Bad header=<H2>Choose Category</H2><FORM : > > >/home/httpd/cgi-bin/commerce/\ > > >shop/toplevel.pl > > >[Wed Mar 15 16:08:53 2000] [error] [client 192.168.3.1] unable to > > >include "/cgi\ > > >-bin/commerce/shop/toplevel.pl?type=category" in parsed file > > >/home/httpd/html/c\ > > >ommerce/shop/index.shtml > > > > > > > > >Derek > > > > > > > > >Pat Eyler wrote: > > > > > > > > Derek, > > > > it should be modules/Yams/cart.pm that gets the fix. Below is the > > >needed > > > > patch , but it's also attached as a file called quickpatch. to use > > > > it do the following > > > > > > > > $ patch Cart.pm < quickpatch > > > > > > > > in the modules/Yams directory. > > > > > > > > -pate > > > > > > > > --- Cart.pm Fri Mar 10 14:02:53 2000 > > > > +++ newcart.pm Tue Mar 14 22:13:34 2000 > > > > @@ -981,7 +981,7 @@ > > > > } > > > > else > > > > { > > > > - $sql .= "ORDER BY sku"; > > > > + $sql .= " ORDER BY sku"; > > > > } > > > > } > > > > > > > > @@ -1135,7 +1135,7 @@ > > > > # Figure out sku to start the previous page on > > > > $sql = "SELECT sku FROM products WHERE department = > > > > $q_department AND sku $op $q_start"; > > > > $sql .= " AND subdepartment = $q_subdepartment" > > > > if(defined($subdepartment)); > > > > - $sql .= "ORDER BY sku DESC LIMIT $products_per_page"; > > > > + $sql .= " ORDER BY sku DESC LIMIT $products_per_page"; > > > > > > > > $sth = &dbsql($DBH, $sql); > > > > my($prev_sku, $temp); > > > > > > > > > > >------------------------------------------------------------------------ > > > > Name: quickpatch > > > > quickpatch Type: Plain Text (TEXT/PLAIN) > > > > Encoding: BASE64 > > > > > >_______________________________________________ > > >Yams-discuss mailing list > > >Yam...@li... > > >http://lists.sourceforge.net/mailman/listinfo/yams-discuss > > > > ______________________________________________________ > > Get Your Private, Free Email at http://www.hotmail.com > > > > _______________________________________________ > > Yams-discuss mailing list > > Yam...@li... > > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > > _______________________________________________ > Yams-discuss mailing list > Yam...@li... > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > |
From: Derek C. <der...@ma...> - 2000-03-17 17:26:07
|
Well, to tell you the truth I didn't even know that it had been released. There wasn't any email sent to the announce list. But any ways, I have been following the list and had made the previous changes by adding CGI->header and got it working. However, I did just do the upgrade and yes it fixed things. Thanks for checking. I am guessing that the cgi script for the search feature is the same as the one that was posted to the list previously, is this true? Now, the only thing that I still can't get working is the Revenue Reports in the admin utility. It shows zeros for everything, and I do have finished sales in there. I forget the exact term that is specified, but they're there. Oh, and one last thought, I just noticed the cron scripts in the new release. What are these for, and when are the supposed to be scheduled? Didn't mean to overwhelm you with questions, sorry. Derek pat eyler wrote: > > Derek, > does 0.6.2 fix things for you? > > -pate > > >From: Derek Carr <der...@ma...> > >To: Pat Eyler <pa...@gn...> > >CC: yam...@li... > >Subject: Re: [Yams-discuss] yams 0.6.1 bug > >Date: Wed, 15 Mar 2000 16:03:13 -0500 > > > >I tried this and the drop-down lists still don't appear. Any thoughts? > >I did implement the other fixes discussed for the search feature and > >that worked. But, I still can't get these departments to show up. I > >get the following error still: > > > >[Wed Mar 15 16:08:51 2000] [error] [client 192.168.3.1] unable to > >include "/cgi\ > >-bin/commerce/shop/toplevel.pl?type=department" in parsed file > >/home/httpd/html\ > >/commerce/shop/index.shtml > >[Wed Mar 15 16:08:53 2000] toplevel.pl: Use of uninitialized value at > >(eval 14)\ > > line 27. > >[Wed Mar 15 16:08:53 2000] [error] [client 192.168.3.1] malformed header > >from s\ > >cript. Bad header=<H2>Choose Category</H2><FORM : > >/home/httpd/cgi-bin/commerce/\ > >shop/toplevel.pl > >[Wed Mar 15 16:08:53 2000] [error] [client 192.168.3.1] unable to > >include "/cgi\ > >-bin/commerce/shop/toplevel.pl?type=category" in parsed file > >/home/httpd/html/c\ > >ommerce/shop/index.shtml > > > > > >Derek > > > > > >Pat Eyler wrote: > > > > > > Derek, > > > it should be modules/Yams/cart.pm that gets the fix. Below is the > >needed > > > patch , but it's also attached as a file called quickpatch. to use > > > it do the following > > > > > > $ patch Cart.pm < quickpatch > > > > > > in the modules/Yams directory. > > > > > > -pate > > > > > > --- Cart.pm Fri Mar 10 14:02:53 2000 > > > +++ newcart.pm Tue Mar 14 22:13:34 2000 > > > @@ -981,7 +981,7 @@ > > > } > > > else > > > { > > > - $sql .= "ORDER BY sku"; > > > + $sql .= " ORDER BY sku"; > > > } > > > } > > > > > > @@ -1135,7 +1135,7 @@ > > > # Figure out sku to start the previous page on > > > $sql = "SELECT sku FROM products WHERE department = > > > $q_department AND sku $op $q_start"; > > > $sql .= " AND subdepartment = $q_subdepartment" > > > if(defined($subdepartment)); > > > - $sql .= "ORDER BY sku DESC LIMIT $products_per_page"; > > > + $sql .= " ORDER BY sku DESC LIMIT $products_per_page"; > > > > > > $sth = &dbsql($DBH, $sql); > > > my($prev_sku, $temp); > > > > > > > >------------------------------------------------------------------------ > > > Name: quickpatch > > > quickpatch Type: Plain Text (TEXT/PLAIN) > > > Encoding: BASE64 > > > >_______________________________________________ > >Yams-discuss mailing list > >Yam...@li... > >http://lists.sourceforge.net/mailman/listinfo/yams-discuss > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > _______________________________________________ > Yams-discuss mailing list > Yam...@li... > http://lists.sourceforge.net/mailman/listinfo/yams-discuss |
From: pat e. <p_...@ho...> - 2000-03-17 16:33:19
|
Derek, does 0.6.2 fix things for you? -pate >From: Derek Carr <der...@ma...> >To: Pat Eyler <pa...@gn...> >CC: yam...@li... >Subject: Re: [Yams-discuss] yams 0.6.1 bug >Date: Wed, 15 Mar 2000 16:03:13 -0500 > >I tried this and the drop-down lists still don't appear. Any thoughts? >I did implement the other fixes discussed for the search feature and >that worked. But, I still can't get these departments to show up. I >get the following error still: > >[Wed Mar 15 16:08:51 2000] [error] [client 192.168.3.1] unable to >include "/cgi\ >-bin/commerce/shop/toplevel.pl?type=department" in parsed file >/home/httpd/html\ >/commerce/shop/index.shtml >[Wed Mar 15 16:08:53 2000] toplevel.pl: Use of uninitialized value at >(eval 14)\ > line 27. >[Wed Mar 15 16:08:53 2000] [error] [client 192.168.3.1] malformed header >from s\ >cript. Bad header=<H2>Choose Category</H2><FORM : >/home/httpd/cgi-bin/commerce/\ >shop/toplevel.pl >[Wed Mar 15 16:08:53 2000] [error] [client 192.168.3.1] unable to >include "/cgi\ >-bin/commerce/shop/toplevel.pl?type=category" in parsed file >/home/httpd/html/c\ >ommerce/shop/index.shtml > > >Derek > > >Pat Eyler wrote: > > > > Derek, > > it should be modules/Yams/cart.pm that gets the fix. Below is the >needed > > patch , but it's also attached as a file called quickpatch. to use > > it do the following > > > > $ patch Cart.pm < quickpatch > > > > in the modules/Yams directory. > > > > -pate > > > > --- Cart.pm Fri Mar 10 14:02:53 2000 > > +++ newcart.pm Tue Mar 14 22:13:34 2000 > > @@ -981,7 +981,7 @@ > > } > > else > > { > > - $sql .= "ORDER BY sku"; > > + $sql .= " ORDER BY sku"; > > } > > } > > > > @@ -1135,7 +1135,7 @@ > > # Figure out sku to start the previous page on > > $sql = "SELECT sku FROM products WHERE department = > > $q_department AND sku $op $q_start"; > > $sql .= " AND subdepartment = $q_subdepartment" > > if(defined($subdepartment)); > > - $sql .= "ORDER BY sku DESC LIMIT $products_per_page"; > > + $sql .= " ORDER BY sku DESC LIMIT $products_per_page"; > > > > $sth = &dbsql($DBH, $sql); > > my($prev_sku, $temp); > > > > >------------------------------------------------------------------------ > > Name: quickpatch > > quickpatch Type: Plain Text (TEXT/PLAIN) > > Encoding: BASE64 > >_______________________________________________ >Yams-discuss mailing list >Yam...@li... >http://lists.sourceforge.net/mailman/listinfo/yams-discuss ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com |
From: Garth S. <ga...@ap...> - 2000-03-17 14:43:10
|
Version 0.6.2 of Yams has been released. This release should fix most of the issues found in the 0.6.1 release. 0.6.2 - 17 March 2000 * fixed problems with the proper headers not being sent when the server side includes were used under mod_cgi (toplevel.pl, cart.pl) * fixed problem where displaying empty departments did not work properly (Cart.pm) * fixed problem where creating session id was causing a warning message (Cart.pm) * added utility to initialize the search function with the existing product descriptions (create_pds_table.pl) The new version is availabe directly at http://download.sourceforge.net/yams/yams_0.6.2.tar.gz Garth |
From: Bart C. <ba...@ci...> - 2000-03-17 08:52:36
|
Hello all, Just reading over the last couple messages, I thought I would point out something about the way the CGI headers work with mod_perl vs mod_cgi. If you are running a script under mod_cgi, you *must* print either: $cgi->header(); or "Content-type: text/html\n\n"; or an equivalent. BUT, if you are running under mod_perl, you *may* print: $cgi->header(); but you *cannot* print: "Content-type: text/html\n\n"; By default, mod_perl will print the header for you even if the script does not explicitly print the header. By using the $cgi->header() line, the CGI.pm module will mess with the internal request structure and handle the headers appropriately. However, explicitly printing the Content-type header under mod_perl will end up really print something like "Content-type: text/html\n\nContent-type: text/html\n\n" thereby showing the second header in the browser. Generally, unless you have a good reason not to, it is probably best to use $cgi->header(). See also: PerlSendHeader (Apache directive under mod_perl) Hopefully this message was not too far off topic... Bart On Fri, 17 Mar 2000, Gaelyne Gasson wrote: > G'day Pat, > > On Mar 16 2000 pat eyler <p_...@ho...> wrote: > > > >Speaking of $CGI->header, I'm not as familiar with this format for > > >Perl commands. Is there a resource where I can learn more about them? > > > > > > > I good source is either 'Perl Programming' or 'Perl in a Nutshell' > > both from O'Reilly. PiaN has a section on using CGI.pm which does > > a pretty good job of explaining the usage. Here's a link where > > you can get either of them > > http://www1.fatbrain.com/FindItNow/Services/home.cl?from=XJT822&store=1 > > Thanks! > > > >I also tried it in the toplevel.pl file for the ?type=department include, > > >adding print $CGI->header, $CGI->start_html; to the line above the print > > >&printTopLevels line and it too worked. > > > > > > > Great, I'm interested in what causes your apache server to require these > > tho'. which version of apache are you running? > > I don't think it's the version of apache (though it could be a > configuration setting), mainly because I've been using Apache for several > years now, updating as required. Currently the version is 1.3.12, and for > as long as I've been using Apache, there's always been an item in the FAQ > file about requiring scripts to send a header. (What does it mean when > my CGI scripts fail with "Premature end of script headers?"). It's not > only a requirement for Perl scripts but any other type as well, including > PHP. > > After a bit of thought on this, it could be a difference of CGI.pm > versions - or even configuration. I had a look at my CGI.pm file > (something I've never really taken much notice of), and found the > following that may provide the clue, on lines 61 and 62: > > # Change this to 1 to suppress redundant HTTP headers > $HEADERS_ONCE = 0; > > The above is the default setting, as I've not edited the file at > all. > > > > Cheers, > Gaelyne > > //\ /\\ Gaelyne R. Gasson ga...@vi... > || * \ . . / * || 90 Hilliers Rd Phone: +61 8 8322-2716 > \\____\X/____// Reynella, S.A. 5161 Fax: +61 8 8387-5810 > / * /O\ * \ Australia ICQ: 5069384 > \__/ " \__/ http://cbm.videocam.net.au > > > > > > _______________________________________________ > Yams-discuss mailing list > Yam...@li... > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > |
From: Gaelyne G. <ga...@vi...> - 2000-03-17 08:12:32
|
G'day Pat, On Mar 16 2000 pat eyler <p_...@ho...> wrote: > >Speaking of $CGI->header, I'm not as familiar with this format for > >Perl commands. Is there a resource where I can learn more about them? > > > > I good source is either 'Perl Programming' or 'Perl in a Nutshell' > both from O'Reilly. PiaN has a section on using CGI.pm which does > a pretty good job of explaining the usage. Here's a link where > you can get either of them > http://www1.fatbrain.com/FindItNow/Services/home.cl?from=XJT822&store=1 Thanks! > >I also tried it in the toplevel.pl file for the ?type=department include, > >adding print $CGI->header, $CGI->start_html; to the line above the print > >&printTopLevels line and it too worked. > > > > Great, I'm interested in what causes your apache server to require these > tho'. which version of apache are you running? I don't think it's the version of apache (though it could be a configuration setting), mainly because I've been using Apache for several years now, updating as required. Currently the version is 1.3.12, and for as long as I've been using Apache, there's always been an item in the FAQ file about requiring scripts to send a header. (What does it mean when my CGI scripts fail with "Premature end of script headers?"). It's not only a requirement for Perl scripts but any other type as well, including PHP. After a bit of thought on this, it could be a difference of CGI.pm versions - or even configuration. I had a look at my CGI.pm file (something I've never really taken much notice of), and found the following that may provide the clue, on lines 61 and 62: # Change this to 1 to suppress redundant HTTP headers $HEADERS_ONCE = 0; The above is the default setting, as I've not edited the file at all. Cheers, Gaelyne //\ /\\ Gaelyne R. Gasson ga...@vi... || * \ . . / * || 90 Hilliers Rd Phone: +61 8 8322-2716 \\____\X/____// Reynella, S.A. 5161 Fax: +61 8 8387-5810 / * /O\ * \ Australia ICQ: 5069384 \__/ " \__/ http://cbm.videocam.net.au |
From: Gaelyne G. <ga...@vi...> - 2000-03-16 03:50:13
|
On Mar 15 2000 Garth Sainio <ga...@ap...> wrote: > > [error] malformed header from script. Bad header=<FORM METHOD="POST" ACTION="/c: /cgi-bin/commerce4/shop/cart.pl > > [error] unable to include "/cgi-bin/commerce4/shop/cart.pl?action=print_search" in parsed file /commerce/shop/index.html > > toplevel.pl: Use of uninitialized value at (eval 14) line 27. > > [error] malformed header from script. Bad header=<H2>Choose Department</H2><FOR: /cgi-bin/commerce4/shop/toplevel.pl > > [error] unable to include "/cgi-bin/commerce4/shop/toplevel.pl?type=department" in parsed file /commerce/shop/index.html > > It looks like apache is expecting the header from the script. It does. > Do the includes that work print $CGI->header (or its equivalent)? Yes. In fact, in order to have a "view shopping cart" link work, I needed to add the $CGI->header line to the show_cart subroutine. (I was meaning to mention this to you). Speaking of $CGI->header, I'm not as familiar with this format for Perl commands. Is there a resource where I can learn more about them? > On my system if I print out the $CGI->header in the includes, I get > multiple headers left in the html page - your setup may need to print > the header to allow the includes to added to file. From what I can tell, it's not required for some items and is for others. Such as the show_cart page when used as a link and the includes. I experimented and added: print $CGI->header, $CGI->start_html; to the line above the print &getSearchFormString,($CGI, $DBH); string and the virtual include worked fine. Success! I also tried it in the toplevel.pl file for the ?type=department include, adding print $CGI->header, $CGI->start_html; to the line above the print &printTopLevels line and it too worked. > > > As a short term solution, the following HTML code should create the > > > desired form (with the updated path to the cart.pl script): > > > > > > <FORM METHOD="POST" ACTION="/registry/commerce/shop/cart.pl" snip > > Thanks, Garth. This DOES work for the item name. Which description is it > > using? I tried a couple of tests for the description using words that are > > in the shop item descriptions but each time it didn't come up with a match > > when it should have. > > Doh. This was not a good release for me. The table that is used for > searching descriptions needs to be backfilled for existing products. > > The following script should take care of that. It did. Thanks! Cheers, Gaelyne |
From: Derek C. <der...@ma...> - 2000-03-15 21:08:17
|
I tried this and the drop-down lists still don't appear. Any thoughts? I did implement the other fixes discussed for the search feature and that worked. But, I still can't get these departments to show up. I get the following error still: [Wed Mar 15 16:08:51 2000] [error] [client 192.168.3.1] unable to include "/cgi\ -bin/commerce/shop/toplevel.pl?type=department" in parsed file /home/httpd/html\ /commerce/shop/index.shtml [Wed Mar 15 16:08:53 2000] toplevel.pl: Use of uninitialized value at (eval 14)\ line 27. [Wed Mar 15 16:08:53 2000] [error] [client 192.168.3.1] malformed header from s\ cript. Bad header=<H2>Choose Category</H2><FORM : /home/httpd/cgi-bin/commerce/\ shop/toplevel.pl [Wed Mar 15 16:08:53 2000] [error] [client 192.168.3.1] unable to include "/cgi\ -bin/commerce/shop/toplevel.pl?type=category" in parsed file /home/httpd/html/c\ ommerce/shop/index.shtml Derek Pat Eyler wrote: > > Derek, > it should be modules/Yams/cart.pm that gets the fix. Below is the needed > patch , but it's also attached as a file called quickpatch. to use > it do the following > > $ patch Cart.pm < quickpatch > > in the modules/Yams directory. > > -pate > > --- Cart.pm Fri Mar 10 14:02:53 2000 > +++ newcart.pm Tue Mar 14 22:13:34 2000 > @@ -981,7 +981,7 @@ > } > else > { > - $sql .= "ORDER BY sku"; > + $sql .= " ORDER BY sku"; > } > } > > @@ -1135,7 +1135,7 @@ > # Figure out sku to start the previous page on > $sql = "SELECT sku FROM products WHERE department = > $q_department AND sku $op $q_start"; > $sql .= " AND subdepartment = $q_subdepartment" > if(defined($subdepartment)); > - $sql .= "ORDER BY sku DESC LIMIT $products_per_page"; > + $sql .= " ORDER BY sku DESC LIMIT $products_per_page"; > > $sth = &dbsql($DBH, $sql); > my($prev_sku, $temp); > > ------------------------------------------------------------------------ > Name: quickpatch > quickpatch Type: Plain Text (TEXT/PLAIN) > Encoding: BASE64 |
From: Garth S. <ga...@ap...> - 2000-03-15 13:45:30
|
On Wed, 15 Mar 2000, Gaelyne Gasson wrote: > Yes, I'm using an include for header and footer on the index page. These > work fine. I tried adding in the toplevel.pl?type=department include, but > this resulted in another "error processing this directive" from Apache. > > To further test, I have a cgi-bin perl script that displays random text > and is an include. I tried it on the shop page as both: > <!--#include virtual="blah" --> and <!--#exec cgi="blah"--> and it worked > OK both times. Feeling experimental, I changed the Yams include > statements to <!--#exec cgi=".."--> and had the "error processing this > directive" error from Apache. It was worth a try. > > > > Is it running as a cgi script or as an Apache::Registry script? > > cgi script. > > > Are you using the latest version of cart.pl? > > Yes. > > Pat asked me to try cart.pl from the command line and report the > results. Here it is - this is the result **AFTER** changing line 1893: > > ---------------------------- > [shop] # cart.pl > (offline mode: enter name=value pairs on standard input) > action=print_search > <FORM METHOD="POST" ACTION="/cgi-bin/commerce4/shop/cart.pl" ENCTYPE="application/x-www-form-urlencoded"> > <INPUT TYPE="text" NAME="search_terms" SIZE=15 MAXLENGTH=50><SELECT NAME="where"> > <OPTION VALUE="Name">Name > <OPTION VALUE="Description">Description > </SELECT> > <INPUT TYPE="submit" NAME=".submit"><INPUT TYPE="hidden" NAME="action" VALUE="search"><INPUT TYPE="hidden" NAME="session_id" VALUE="8O69g43o0cuU0lWfxnnNRgJp"></FORM>Wed Mar 15 23:12:10 > [shop] # > ---------------------------- > > Here's the log file result **AFTER** changing line 1893, and I've > included the toplevel.pl one for measure. This isn't an option that I > normally use though. > > [error] malformed header from script. Bad header=<FORM METHOD="POST" ACTION="/c: /cgi-bin/commerce4/shop/cart.pl > [error] unable to include "/cgi-bin/commerce4/shop/cart.pl?action=print_search" in parsed file /commerce/shop/index.html > toplevel.pl: Use of uninitialized value at (eval 14) line 27. > [error] malformed header from script. Bad header=<H2>Choose Department</H2><FOR: /cgi-bin/commerce4/shop/toplevel.pl > [error] unable to include "/cgi-bin/commerce4/shop/toplevel.pl?type=department" in parsed file /commerce/shop/index.html It looks like apache is expecting the header from the script. Do the includes that work print $CGI->header (or its equivalent)? On my system if I print out the $CGI->header in the includes, I get multiple headers left in the html page - your setup may need to print the header to allow the includes to added to file. > > > > As a short term solution, the following HTML code should create the > > desired form (with the updated path to the cart.pl script): > > > > <FORM METHOD="POST" ACTION="/registry/commerce/shop/cart.pl" > > ENCTYPE="application/x-www-form-urlencoded"> > > <INPUT TYPE="text" NAME="search_terms" SIZE=15 MAXLENGTH=50> > > <SELECT NAME="where"> > > <OPTION VALUE="Name">Name > > <OPTION VALUE="Description">Description > > </SELECT> > > <INPUT TYPE="hidden" NAME="action" VALUE="search"> > > <INPUT TYPE="submit"> > > </FORM> > > Thanks, Garth. This DOES work for the item name. Which description is it > using? I tried a couple of tests for the description using words that are > in the shop item descriptions but each time it didn't come up with a match > when it should have. Doh. This was not a good release for me. The table that is used for searching descriptions needs to be backfilled for existing products. The following script should take care of that. #!/usr/bin/perl -w # quick script to populate the product_description_search table use strict; use Yams::DBWrap; use Yams::YamsGlobals; my($DBH) = &dbconnect(\%config); my($sql, $sth); $sql = "SELECT sku, short_description, long_description, other_text FROM products"; my($sku, $short_description, $long_description, $other_text); $sth = &dbsql($DBH, $sql); while(($sku, $short_description, $long_description, $other_text) = $sth->fetchrow_array) { my($description) = lc($short_description) . "\n" . lc($long_description) . "\n" . lc($other_text); $description = $DBH->quote($description); my($q_sku) = $DBH->quote($sku); $sql = "INSERT INTO product_description_search VALUES($q_sku, $description)"; my($sth2) = &dbsql($DBH, $sql); $sth2->finish if($sth2); } $sth->finish if($sth); $DBH->disconnect; Garth > > > Cheers, > Gaelyne > > > |
From: Gaelyne G. <ga...@vi...> - 2000-03-15 13:33:25
|
G'day All, Special note to Pat - I have your answers in this mail as well. On Mar 15 2000 Garth Sainio <ga...@ap...> wrote: > The second problem may be related to the fact that I use the environment > variable HTTP_REFERER in the creation of the session_id, so if you go to > the page directly then that value is not available - that explains the > use of initialized variable at Cart.pm line 1894 error. But that really > shouldn't be causing the the malformed header error (which I couldn't > recreate on my box at home, so it may have something to do with the way > apache is configured). > > To fix the use of the unitialized value, change line 1893 from > > my($http_ref) = $ENV{'HTTP_REFERER'}; > > to > > my($http_ref) = $ENV{'HTTP_REFERER'} || ""; I made this change, and it changed the error log info (included below), but it still resulted in Apache reporting an error in completing the directive on the web page. > Are you using any other includes in the page with the include for the > search form? > Do they work? Yes, I'm using an include for header and footer on the index page. These work fine. I tried adding in the toplevel.pl?type=department include, but this resulted in another "error processing this directive" from Apache. To further test, I have a cgi-bin perl script that displays random text and is an include. I tried it on the shop page as both: <!--#include virtual="blah" --> and <!--#exec cgi="blah"--> and it worked OK both times. Feeling experimental, I changed the Yams include statements to <!--#exec cgi=".."--> and had the "error processing this directive" error from Apache. It was worth a try. > Is it running as a cgi script or as an Apache::Registry script? cgi script. > Are you using the latest version of cart.pl? Yes. Pat asked me to try cart.pl from the command line and report the results. Here it is - this is the result **AFTER** changing line 1893: ---------------------------- [shop] # cart.pl (offline mode: enter name=value pairs on standard input) action=print_search <FORM METHOD="POST" ACTION="/cgi-bin/commerce4/shop/cart.pl" ENCTYPE="application/x-www-form-urlencoded"> <INPUT TYPE="text" NAME="search_terms" SIZE=15 MAXLENGTH=50><SELECT NAME="where"> <OPTION VALUE="Name">Name <OPTION VALUE="Description">Description </SELECT> <INPUT TYPE="submit" NAME=".submit"><INPUT TYPE="hidden" NAME="action" VALUE="search"><INPUT TYPE="hidden" NAME="session_id" VALUE="8O69g43o0cuU0lWfxnnNRgJp"></FORM>Wed Mar 15 23:12:10 [shop] # ---------------------------- Here's the log file result **AFTER** changing line 1893, and I've included the toplevel.pl one for measure. This isn't an option that I normally use though. [error] malformed header from script. Bad header=<FORM METHOD="POST" ACTION="/c: /cgi-bin/commerce4/shop/cart.pl [error] unable to include "/cgi-bin/commerce4/shop/cart.pl?action=print_search" in parsed file /commerce/shop/index.html toplevel.pl: Use of uninitialized value at (eval 14) line 27. [error] malformed header from script. Bad header=<H2>Choose Department</H2><FOR: /cgi-bin/commerce4/shop/toplevel.pl [error] unable to include "/cgi-bin/commerce4/shop/toplevel.pl?type=department" in parsed file /commerce/shop/index.html > As a short term solution, the following HTML code should create the > desired form (with the updated path to the cart.pl script): > > <FORM METHOD="POST" ACTION="/registry/commerce/shop/cart.pl" > ENCTYPE="application/x-www-form-urlencoded"> > <INPUT TYPE="text" NAME="search_terms" SIZE=15 MAXLENGTH=50> > <SELECT NAME="where"> > <OPTION VALUE="Name">Name > <OPTION VALUE="Description">Description > </SELECT> > <INPUT TYPE="hidden" NAME="action" VALUE="search"> > <INPUT TYPE="submit"> > </FORM> Thanks, Garth. This DOES work for the item name. Which description is it using? I tried a couple of tests for the description using words that are in the shop item descriptions but each time it didn't come up with a match when it should have. Cheers, Gaelyne |
From: Garth S. <ga...@ap...> - 2000-03-15 12:11:13
|
The second problem may be related to the fact that I use the environment variable HTTP_REFERER in the creation of the session_id, so if you go to the page directly then that value is not available - that explains the use of initialized variable at Cart.pm line 1894 error. But that really shouldn't be causing the the malformed header error (which I couldn't recreate on my box at home, so it may have something to do with the way apache is configured). To fix the use of the unitialized value, change line 1893 from my($http_ref) = $ENV{'HTTP_REFERER'}; to my($http_ref) = $ENV{'HTTP_REFERER'} || ""; Are you using any other includes in the page with the include for the search form? Do they work? Is it running as a cgi script or as an Apache::Registry script? Are you using the latest version of cart.pl? As a short term solution, the following HTML code should create the desired form (with the updated path to the cart.pl script): <FORM METHOD="POST" ACTION="/registry/commerce/shop/cart.pl" ENCTYPE="application/x-www-form-urlencoded"> <INPUT TYPE="text" NAME="search_terms" SIZE=15 MAXLENGTH=50> <SELECT NAME="where"> <OPTION VALUE="Name">Name <OPTION VALUE="Description">Description </SELECT> <INPUT TYPE="hidden" NAME="action" VALUE="search"> <INPUT TYPE="submit"> </FORM> Garth On Tue, 14 Mar 2000, Derek Carr wrote: > I'm sorry, what file should I put the spaces in? > > The search problem pops up when you try to display the form. > > Derek > > > Garth Sainio wrote: > > > > For the first problem add a space to the beginning of the the string in > > lines 980, 984, and 1138. > > > > As for the second I'll have to find a clean box to try and install it on. > > > > Is the problem with search when you try to display the form or when you > > try to get results from the form? > > > > Garth > > > > On Tue, 14 Mar 2000, Derek Carr wrote: > > > > > I just tried testing out the new version and have the same problem. In > > > addition, the listings on the homepage before login of the departments > > > and such no longer display. But, I haven't looked at the error log for > > > these yet. But, I get this same c: error. > > > > > > Derek Carr > > > > > > > > > _______________________________________________ > > > Yams-discuss mailing list > > > Yam...@li... > > > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > > > > > > > _______________________________________________ > > Yams-discuss mailing list > > Yam...@li... > > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > > _______________________________________________ > Yams-discuss mailing list > Yam...@li... > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > |
From: Pat E. <pa...@gn...> - 2000-03-15 03:28:31
|
Derek, it should be modules/Yams/cart.pm that gets the fix. Below is the needed patch , but it's also attached as a file called quickpatch. to use it do the following $ patch Cart.pm < quickpatch in the modules/Yams directory. -pate --- Cart.pm Fri Mar 10 14:02:53 2000 +++ newcart.pm Tue Mar 14 22:13:34 2000 @@ -981,7 +981,7 @@ } else { - $sql .= "ORDER BY sku"; + $sql .= " ORDER BY sku"; } } @@ -1135,7 +1135,7 @@ # Figure out sku to start the previous page on $sql = "SELECT sku FROM products WHERE department = $q_department AND sku $op $q_start"; $sql .= " AND subdepartment = $q_subdepartment" if(defined($subdepartment)); - $sql .= "ORDER BY sku DESC LIMIT $products_per_page"; + $sql .= " ORDER BY sku DESC LIMIT $products_per_page"; $sth = &dbsql($DBH, $sql); my($prev_sku, $temp); |
From: Derek C. <der...@ma...> - 2000-03-14 20:51:36
|
I'm sorry, what file should I put the spaces in? The search problem pops up when you try to display the form. Derek Garth Sainio wrote: > > For the first problem add a space to the beginning of the the string in > lines 980, 984, and 1138. > > As for the second I'll have to find a clean box to try and install it on. > > Is the problem with search when you try to display the form or when you > try to get results from the form? > > Garth > > On Tue, 14 Mar 2000, Derek Carr wrote: > > > I just tried testing out the new version and have the same problem. In > > addition, the listings on the homepage before login of the departments > > and such no longer display. But, I haven't looked at the error log for > > these yet. But, I get this same c: error. > > > > Derek Carr > > > > > > _______________________________________________ > > Yams-discuss mailing list > > Yam...@li... > > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > > > > _______________________________________________ > Yams-discuss mailing list > Yam...@li... > http://lists.sourceforge.net/mailman/listinfo/yams-discuss |
From: Garth S. <ga...@ap...> - 2000-03-14 17:27:23
|
For the first problem add a space to the beginning of the the string in lines 980, 984, and 1138. As for the second I'll have to find a clean box to try and install it on. Is the problem with search when you try to display the form or when you try to get results from the form? Garth On Tue, 14 Mar 2000, Derek Carr wrote: > I just tried testing out the new version and have the same problem. In > addition, the listings on the homepage before login of the departments > and such no longer display. But, I haven't looked at the error log for > these yet. But, I get this same c: error. > > Derek Carr > > Gaelyne Gasson wrote: > > > > G'day Pat, > > > > > Gaelyne, > > > what is you $shop_script_root set to in YamsGlobals.pm? > > > > /cgi-bin/commerce4/shop/ > > > > The directory with the perl .pm files is Yams4, so I use "commerce4" as > > the directory name so I can differentiate between the versions I've been > > testing. > > > > > >From: Gaelyne Gasson <ga...@vi...> > > > >To: yam...@li... > > > >Subject: [Yams-discuss] Search feature > > > >Date: Sat, 11 Mar 2000 20:00:50 +1030 (CST) > > > > > > > >G'day, > > > > > > > >I was able to install the new version OK, but have run into a problem with > > > >the search feature. Here's what the Error log has to say about it (I > > > >stripped the path lines for this). > > > > > > > > cart.pl: Use of uninitialized value at ... Yams4/Cart.pm line > 1894. > > > > malformed header from script. Bad header=<FORM METHOD="POST" > > > > >ACTION="/c: ... cart.pl > > > > unable to include "cart.pl?action=print_search" in parsed file > > > > >/commerce/shop/test.html > > > > > > > >The middle one is curious. It almost looks like an MS-DOS path. > > > >I couldn't find it in any of the .pm or .pl files. It has to be >there > > > >somewhere. > > > > > > > >The update required a few more files to be changed than what was >listed in > > > >the Upgrade text file, by the way. > > > > > > > >For completeness, and in trying to find the solution for this, I >copied > > > >over the entire set of .pl and .pm files and made the >appropriate changes > > > >to the files for location. (Yams:: to Yams4::). > > > > > > > >The related items change worked fine, at least as far as the admin >pages > > > >go - I haven't found how this is displayed just yet though. > > > > Cheers, > > Gaelyne > > > > //\ /\\ Gaelyne R. Gasson ga...@vi... > > || * \ . . / * || 90 Hilliers Rd Phone: +61 8 8322-2716 > > \\____\X/____// Reynella, S.A. 5161 Fax: +61 8 8387-5810 > > / * /O\ * \ Australia ICQ: 5069384 > > \__/ " \__/ http://cbm.videocam.net.au > > > > _______________________________________________ > > Yams-discuss mailing list > > Yam...@li... > > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > > _______________________________________________ > Yams-discuss mailing list > Yam...@li... > http://lists.sourceforge.net/mailman/listinfo/yams-discuss > |
From: Derek C. <der...@ma...> - 2000-03-14 17:11:54
|
I just tried testing out the new version and have the same problem. In addition, the listings on the homepage before login of the departments and such no longer display. But, I haven't looked at the error log for these yet. But, I get this same c: error. Derek Carr Gaelyne Gasson wrote: > > G'day Pat, > > > Gaelyne, > > what is you $shop_script_root set to in YamsGlobals.pm? > > /cgi-bin/commerce4/shop/ > > The directory with the perl .pm files is Yams4, so I use "commerce4" as > the directory name so I can differentiate between the versions I've been > testing. > > > >From: Gaelyne Gasson <ga...@vi...> > > >To: yam...@li... > > >Subject: [Yams-discuss] Search feature > > >Date: Sat, 11 Mar 2000 20:00:50 +1030 (CST) > > > > > >G'day, > > > > > >I was able to install the new version OK, but have run into a problem with > > >the search feature. Here's what the Error log has to say about it (I > > >stripped the path lines for this). > > > > > > cart.pl: Use of uninitialized value at ... Yams4/Cart.pm line > 1894. > > > malformed header from script. Bad header=<FORM METHOD="POST" > > > >ACTION="/c: ... cart.pl > > > unable to include "cart.pl?action=print_search" in parsed file > > > >/commerce/shop/test.html > > > > > >The middle one is curious. It almost looks like an MS-DOS path. > > >I couldn't find it in any of the .pm or .pl files. It has to be >there > > >somewhere. > > > > > >The update required a few more files to be changed than what was >listed in > > >the Upgrade text file, by the way. > > > > > >For completeness, and in trying to find the solution for this, I >copied > > >over the entire set of .pl and .pm files and made the >appropriate changes > > >to the files for location. (Yams:: to Yams4::). > > > > > >The related items change worked fine, at least as far as the admin >pages > > >go - I haven't found how this is displayed just yet though. > > Cheers, > Gaelyne > > //\ /\\ Gaelyne R. Gasson ga...@vi... > || * \ . . / * || 90 Hilliers Rd Phone: +61 8 8322-2716 > \\____\X/____// Reynella, S.A. 5161 Fax: +61 8 8387-5810 > / * /O\ * \ Australia ICQ: 5069384 > \__/ " \__/ http://cbm.videocam.net.au > > _______________________________________________ > Yams-discuss mailing list > Yam...@li... > http://lists.sourceforge.net/mailman/listinfo/yams-discuss |
From: Gaelyne G. <ga...@vi...> - 2000-03-14 02:53:16
|
G'day Pat, > Gaelyne, > what is you $shop_script_root set to in YamsGlobals.pm? /cgi-bin/commerce4/shop/ The directory with the perl .pm files is Yams4, so I use "commerce4" as the directory name so I can differentiate between the versions I've been testing. > >From: Gaelyne Gasson <ga...@vi...> > >To: yam...@li... > >Subject: [Yams-discuss] Search feature > >Date: Sat, 11 Mar 2000 20:00:50 +1030 (CST) > > > >G'day, > > > >I was able to install the new version OK, but have run into a problem with > >the search feature. Here's what the Error log has to say about it (I > >stripped the path lines for this). > > > > cart.pl: Use of uninitialized value at ... Yams4/Cart.pm line > 1894. > > malformed header from script. Bad header=<FORM METHOD="POST" > > >ACTION="/c: ... cart.pl > > unable to include "cart.pl?action=print_search" in parsed file > > >/commerce/shop/test.html > > > >The middle one is curious. It almost looks like an MS-DOS path. > >I couldn't find it in any of the .pm or .pl files. It has to be >there > >somewhere. > > > >The update required a few more files to be changed than what was >listed in > >the Upgrade text file, by the way. > > > >For completeness, and in trying to find the solution for this, I >copied > >over the entire set of .pl and .pm files and made the >appropriate changes > >to the files for location. (Yams:: to Yams4::). > > > >The related items change worked fine, at least as far as the admin >pages > >go - I haven't found how this is displayed just yet though. Cheers, Gaelyne //\ /\\ Gaelyne R. Gasson ga...@vi... || * \ . . / * || 90 Hilliers Rd Phone: +61 8 8322-2716 \\____\X/____// Reynella, S.A. 5161 Fax: +61 8 8387-5810 / * /O\ * \ Australia ICQ: 5069384 \__/ " \__/ http://cbm.videocam.net.au |
From: pat e. <p_...@ho...> - 2000-03-13 14:29:41
|
Gaelyne, what is you $shop_script_root set to in YamsGlobals.pm? -pate >From: Gaelyne Gasson <ga...@vi...> >To: yam...@li... >Subject: [Yams-discuss] Search feature >Date: Sat, 11 Mar 2000 20:00:50 +1030 (CST) > >G'day, > >I was able to install the new version OK, but have run into a problem with >the search feature. Here's what the Error log has to say about it (I >stripped the path lines for this). > > cart.pl: Use of uninitialized value at ... Yams4/Cart.pm line > 1894. > malformed header from script. Bad header=<FORM METHOD="POST" > >ACTION="/c: ... cart.pl > unable to include "cart.pl?action=print_search" in parsed file > >/commerce/shop/test.html > >The middle one is curious. It almost looks like an MS-DOS path. >I couldn't find it in any of the .pm or .pl files. It has to be >there >somewhere. > >The update required a few more files to be changed than what was >listed in >the Upgrade text file, by the way. > >For completeness, and in trying to find the solution for this, I >copied >over the entire set of .pl and .pm files and made the >appropriate changes >to the files for location. (Yams:: to Yams4::). > >The related items change worked fine, at least as far as the admin >pages >go - I haven't found how this is displayed just yet though. > > >Cheers, >Gaelyne > > > //\ /\\ Gaelyne R. Gasson ga...@vi... >|| * \ . . / * || 90 Hilliers Rd Phone: +61 8 8322-2716 > \\____\X/____// Reynella, S.A. 5161 Fax: +61 8 8387-5810 > / * /O\ * \ Australia ICQ: 5069384 > \__/ " \__/ http://videocam.net.au http://vcsweb.com > C64/128 Support * Web Hosting * Web Design > > >_______________________________________________ >Yams-discuss mailing list >Yam...@li... >http://lists.sourceforge.net/mailman/listinfo/yams-discuss ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com |
From: Gaelyne G. <ga...@vi...> - 2000-03-11 09:35:31
|
G'day, I was able to install the new version OK, but have run into a problem with the search feature. Here's what the Error log has to say about it (I stripped the path lines for this). cart.pl: Use of uninitialized value at ... Yams4/Cart.pm line 1894. malformed header from script. Bad header=<FORM METHOD="POST" ACTION="/c: ... cart.pl unable to include "cart.pl?action=print_search" in parsed file /commerce/shop/test.html The middle one is curious. It almost looks like an MS-DOS path. I couldn't find it in any of the .pm or .pl files. It has to be there somewhere. The update required a few more files to be changed than what was listed in the Upgrade text file, by the way. For completeness, and in trying to find the solution for this, I copied over the entire set of .pl and .pm files and made the appropriate changes to the files for location. (Yams:: to Yams4::). The related items change worked fine, at least as far as the admin pages go - I haven't found how this is displayed just yet though. Cheers, Gaelyne //\ /\\ Gaelyne R. Gasson ga...@vi... || * \ . . / * || 90 Hilliers Rd Phone: +61 8 8322-2716 \\____\X/____// Reynella, S.A. 5161 Fax: +61 8 8387-5810 / * /O\ * \ Australia ICQ: 5069384 \__/ " \__/ http://videocam.net.au http://vcsweb.com C64/128 Support * Web Hosting * Web Design |
From: Garth S. <ga...@ap...> - 2000-03-10 16:25:04
|
Yams 0.6.1 was released today. Changes are * introduced simple product search mechanism -user can search for keywords in name of product or in the product description. * introducted related products - at product creation time, related products can be chosen for the new product and these products will be soft sold to the user after the product is placed in the cart * fixed problem with printLabels in Reports.pm where bundle products with shippable products would not show up in the label list. Relevant Yams Links: http://sourceforge.net/project/?group_id=64 http://yams.sourceforge.net http://download.sourceforge.net/yams/yams_0.6.1.tar.gz Garth |
From: pat e. <p_...@ho...> - 2000-03-09 15:25:15
|
Looking at this bug report, I think it should be widened to include non-email notification. My initial thought is to add a notify column and a vendor column to the product table (both potentially NULL). The notify column would hold an int which relates to the id of a notification table like: CREATE TABLE notification ( id integer NOT NULL DEFAULT 0 AUTO_INCREMENT, how enum("email", "fax", "direct"), PRIMARY KEY(id)); The vendor column could be something like: CREATE TABLE vendor ( id integer NOT NULL DEFAULT 0 AUTO_INCREMENT, vendor_name varchar(30), contact_f_name varchar(30), contact_l_name varchar(30), contact_phone varchar(12), contact_fax varchar(12), contact_email(30), notify_string varchar(30), # used to give email, fax, or # other notifcation address notify_format varchar(256), # contains the filename containing # a template for notifications PRIMARY KEY(id)); Then, when an item is sold, an immediate check can be made to determine whether or not to notify by checking for a non-NULL value in product.notify. If notification is needed, the value returned points to which notification routine would be run. The notification routine would then grab the vendor.notify_string and vendor.notify_format values and send the right thing to the right place. Having the vendor table also starts to build the infrastructure to do inventory/vendor maintenance. I've probably overlooked something here (and botched other stuff as well). Please level criticism at me :) -pate ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com |