Bug 53873 - Address edits during checkout don't stick
Address edits during checkout don't stick
Product: Red Hat Web Site
Classification: Red Hat
Component: Store (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Web Development
Web Development
Depends On:
  Show dependency treegraph
Reported: 2001-09-20 11:12 EDT by Jay Turner
Modified: 2015-01-07 18:51 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-20 16:14:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jay Turner 2001-09-20 11:12:23 EDT
Description of Problem:
I changed the address2 and email address for the billing address during
checkout.  After clicking 'Continue' the screen refreshed and I was still
presented with the original information.  Checking the database I found a
couple of things.  First, the email address change that I made was
reflected in a 'B' site record, but the address2 changes was not reflected
in that record.  Second, the site_info record creation was horribly broken.
 Here's what happened.  A copy of the original 'B' record was made and the
email address updated.  The amended copy was then written to the site_info
table (short of the missing change to address2, we are correct to this
point.)  Then another copy of the original site_info record was made and
written to the site_info table unmodified.  So, the newest 'B' site_info
record was one that was a copy of the original, hence the information not
showing correctly in the checkout process.

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
Comment 1 Jay Turner 2001-09-20 16:11:21 EDT
Issue is resolved in webqa.  Just awaiting a push to resolve this on the live site.

Note You need to log in before you can comment on or make changes to this bug.