[ic] Admin Order Entry

[interchange-users@interchange.redhat.com (Mike Heins)]

Quoting Andrew Baerg (andrew@baerg.ca):
> On Fri, 2002-05-03 at 11:47, Mike Heins wrote:
> > Quoting Andrew Baerg (andrew@baerg.ca):
> > > In case anyone cares about this issue, I have investigated it further
> > > and submitted the following to bug #361:
> > > 
> > > It seems to me that the problem lies in Routing. I have found that
> > > only the default route is ever performed so that if you remove it, as
> > > one of the suggestions states, the last route defined in catalog.cfg
> > > becomes the default and is the only one which is performed(whether
> > > through the admin UI or not).
> > 
> > No. All routes defined in mv_order_route or through the cascade
> > mechanism are performed.
> > 
> > > My temporary solution, which I realize
> > > is a horrible hack but which works without issues, is to define a log
> > > Route which includes both log_entry stuff and log_transaction stuff
> > > and decides which to do based on a variable I pass
> > > it. receipt.html also uses the variable to decide whether to diplay
> > > the admin UI or the customer UI. Anyways, that's my two cents for
> > > what it's worth.
> > > 
> > 
> > I think all you need to do is set in a page:
> > 
> > 	[value name=mv_order_route set="route1 route2 route3"]
> > 
> > You should find all routes executed just fine...
> 
> This is what is in the admin/entry.html page, although it is in the form
> <input type=hidden name=mv_order_route value="route1 route2 route3">,

Bingo.

Since the standard catalog.cfg has this:

	FormIgnore  mv_order_route

that has zero effect.

-- 
3005 Nichols Rd., Hamilton, OH  45013
phone +1.513.523.7621      <mike@valuemedia.com>

Nature, to be commanded, must be obeyed. -- Francis Bacon