RE: [ic] Checkout Receipt failure

["Jamie Neil" <suppressed>]

> -----Original Message-----
> From: suppressed
> [mailto:suppressed Behalf Of Jamie Neil
> Sent: 27 May 2003 16:22
> To: suppressed
> Subject: [ic] Checkout Receipt failure
>
>
> Hi All,
>
> I'm in the process of moving a catalog to a live server, which is
> running a
> fresh install of the latest CVS snapshot (4.9.7-200305260658). The catalog
> worked ok on the dev box (an older 4.9.7 snapshot), but on the new box the
> checkout process seems to be broken.
>
> When you finalise the checkout details, the order goes through ok
> (email is
> received and order is entered into the database), but instead of
> displaying
> the receipt it just returns to the checkout page.
>
> I've checked this on the foundation demo at the icdev site, and the same
> problem occurs.
>
> I don't really want to use the older snapshot as it has a number
> of annoying
> UI bugs. Can anyone suggest a fix?
>
> Jamie Neil
> Versado I.T. Services Ltd.
>

Further to my earlier post, I've dug up some similar experiences in the
mailing list and tried the recommended solutions:

1) Permissions/ownership on etc/receipt.html - chmod 664 and chown interch

2) Position of main or default route in catalog.cfg - the "default" order
route is absolutely the last route listed, and no other routes are included
in other files. The routes database is also empty.

Problem is unchanged.

I then tried removing the "entry" order route which seems to have been added
since the previous snapshot. The comment for this route is "Order desk route
run if entered from admin". Initially removing this route seemed to break
the checkout process, the entries in the log being:

	/cgi-bin/clickgolf/process.html Non-existent order routing entry, skipping.

I couldn't see why removing this route should affect the checkout process. I
couldn't find any mention of the "entry" route in any of the config files
for the catalog, but it must be coming from somewhere.

Thinking "caching", I closed all my browser windows and accessed the site
with a fresh session. This time the order went through with no problems and
the receipt was displayed. Question is, why did it use the "entry" route in
the first place? It should be defaulting to the "default" route. The only
explaination I can come up with is that I used the same browser session to
log into the admin UI and the route was being set there. Can't explain why
the icdev demo does the same thing though :(

Jamie Neil

_______________________________________________
interchange-users mailing list
suppressed
http://www.icdevgroup.org/mailman/listinfo/interchange-users