RE: Extra product fields in template

> I feel your pain. =20
> Miva's internals do not read fields it=20
> does not know. You could build a small module that would=20
> open the products table and retrieve your extra values and=20
> put the values into variables like the other product variables. =20

My pain is growing exponentially.

We have about 13,000 different products, and the only way we can manage =
them
is through various systems I've developed that use ODBC to manipulate =
the
data directly.

While it is technically possible for me to change everything to use =
these
Custom Fields tables, I'm still stuck with having to use a Varchar(254) =
data
type for every additional field.

I didn't think it was too wild to hope that MM would have simply read =
EVERY
column from the table and put it in vars. Unless/until someone creates =
a
MM5 mod for this, MM5 is becoming less attractive.

Robert

RE: Extra product fields in template



Why don't you modify the product table in the same way as you did in v4? It
does not really matter if you use xBase, MivaSQL, or MySQL, you still can
design the tables manually in any way you wish.

Ivo Truxa

| http://miva.truxoft.com
| Advanced Miva Merchant modules



-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of R. Bradley
Sent: Saturday, May 07, 2005 12:55 AM
To: [email protected]
Subject: [m5u] RE: Extra product fields in template

> I feel your pain.
> Miva's internals do not read fields it
> does not know. You could build a small module that would
> open the products table and retrieve your extra values and
> put the values into variables like the other product variables.

My pain is growing exponentially.

We have about 13,000 different products, and the only way we can manage them
is through various systems I've developed that use ODBC to manipulate the
data directly.

While it is technically possible for me to change everything to use these
Custom Fields tables, I'm still stuck with having to use a Varchar(254) data
type for every additional field.

I didn't think it was too wild to hope that MM would have simply read EVERY
column from the table and put it in vars. Unless/until someone creates a
MM5 mod for this, MM5 is becoming less attractive.

Robert

RE: Extra product fields in template



> Ivo wrote:
> Why don't you modify the product table in the same way as you=20
> did in v4? It does not really matter if you use xBase,=20
> MivaSQL, or MySQL, you still can design the tables manually=20
> in any way you wish.

The problem isn't modifying the tables; that's easy. The original (and
remaining) problem is how to get those new field values to appear on =
screen
via the new templates. The OP was asking this, and it appears that =
there is
no way.

Robert

RE: Extra product fields in template



Hmm, why there should be no way to display the extra fields?
Simply use &mvt:product:yourField; wherever you want to display it.

Ivo Truxa

| http://miva.truxoft.com
| Advanced Miva Merchant modules



-----Original Message-----
From: R. Bradley

> Ivo wrote:
> Why don't you modify the product table in the same way as you
> did in v4? It does not really matter if you use xBase,
> MivaSQL, or MySQL, you still can design the tables manually
> in any way you wish.

The problem isn't modifying the tables; that's easy. The original (and
remaining) problem is how to get those new field values to appear on screen
via the new templates. The OP was asking this, and it appears that there is
no way.

Robert

RE: Extra product fields in template



> Ivo wrote:
> Hmm, why there should be no way to display the extra fields?
> Simply use &mvt:product:yourField; wherever you want to display it.

It would SEEM that way, but it doesn't work. For example, using:
&mvt:product:keywords;
when I have added a keywords field to Products results in no display.

Robert