> setting up customized error pages isn't the problem. the problem
> is having a database field which says on obsolete redirect to
> product x. the only way to populate that field would be manually.
> and with 30,000 products that's quite a task.
> you could probably redirect to the correct category pretty easily
> but that's about it.
Assuming that some user administers new products as they become available,
and that they are a domain expert, why not have the new product facility
include some form of 'obsoletes products' dialog that causes the replacement
field to be populated with this new product's identifier.
Of course, this doesn't solve the retro-update problem.
An alternative might be to build some smarts into your engine such that
dynamic suggestions can be constructed from browsing/searching behavior -
for example, "this product is now obsolete, but other users interested in
this found ...[some list]... interesting". Depending on how you model this,
how your products are structured, and the buying behavior of your customers,
it _can_ get round the retro-fit issue to some extent - at least it's an
alternative to the 'not found option'.
cheers, & best regards,
- Senior Consultant | voice: +44 (0) 1273 608 311 -
- Intergral Ltd. | mobile: +44 (0) 7971 563 992 -
- Premier House | fax : +44 (0) 7970 652 695 -
- 11 Marlborough Place | -
- Brighton BN1 1UB, UK | -
- http://www.intergral.com/ -
- mailto:[log in to unmask] -
"Whatever is done from love always occurs beyond good
and evil" - Friedrich Nietzsche