[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date
][Minivend by thread
]
[item-price] bug using SQL Postgres access: FIXED
****** message to minivend-users from Mark Stosberg <mark@summersault.com> ******
(Answer below)
> ****** message to minivend-users from Mark Stosberg <mark@summersault.com> ******
>
> I'm using the Minivend with Postgres with the same results Jonathon
> Spaeth had with the prices coming up $0.00 using the [item-price] tag.
> (Jonathon, did you ever get over that hump?) Here's an added twist in my
> situation that may be of interest.
> I originally had two fields in my products database with prices. They
> were called
> retail and mftw. the mftw field held the actual price. both are of type
> float8.
> Without using the "PriceField" or "Database products NAME" options in
> catalog.cfg, minivend picked up the retail field when using the
> [item-price tag]. I added in the
> Pricefield and "Database products NAME" attributes to point the mftw
> field, but this made no difference. This seemed like a bug to me.
>
> So I rebuilt my database, naming the mftw field "price", and
> explicitly made it first in the database, since the retail field had
> been first before. I also disabled the "Database products NAME" and
> "PriceField" attributes now that I had an explicit price field in my
> database. To my chagrin, minivend STILL picked up the retail field into
> the [item-price] tag. Is this a bug as it seems, or have I misconfigured
> something?
>
> -mark
The "bug" here turned out to be frustratingly simple. I didn't realize
that was already "PriceField" setting in my catalog.cfg file, and so
when I added a second one above the first in the file, it was superseded
by the erroreous one at runtime.
to minivend developers: How about if Minivend were to warn you when you
have two copies of a variable in the catalog.cfg file, when only one can
be used?
-mark
http://flip.summersault.com/
-
To unsubscribe from the list, DO NOT REPLY to this message. Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list