The online store i'm setting up for my client deals with clothes. We start off by branching the visitor either to the spring-summer section or the fall-winter section. Spring clothes have a reference number beginning with 'E', winter items' reference codes begin with 'H'. Some products, however, are meant to be available from both (an item that's "summer" as well as "fall", let's say) and their ref code begins with 'EH'.
This translates into making, in some instances, two copies of the same product (or the same subsection, whatever). But there's a catch: actinic does not accept duplicate product reference number. But why isn't this #### software smart enough to handle two logical references to the same product? And what is the way around this limitation, aside from having to change the database itself?
pissed off lazyeye
This translates into making, in some instances, two copies of the same product (or the same subsection, whatever). But there's a catch: actinic does not accept duplicate product reference number. But why isn't this #### software smart enough to handle two logical references to the same product? And what is the way around this limitation, aside from having to change the database itself?
pissed off lazyeye
Comment