Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: 1.5
-
Fix Version/s: Unscheduled
-
Component/s: Technical infrastructure
-
Labels:None
Description
We're using CiviCRM and collecting user's names, addresses, etc.. using the CiviCRM profile management stuff.
We've recently had about 6 complaints from users who are noticing that the 'view user profile' and 'edit user profile' pages don't match up as far as the CiviCRM data is concerned.
A user goes to the '/user/NNN' page and views his "constituent information" and sees one set of data.
He selects "edit" and then the "constituent information" tab and sees a different set of data. Data that corresponds presumeably to some other user entirely.
This problem exhibits both under 1.4 and 1.5.
We do have other things going on on the site, naturally, but nothing that should be getting in the way of CiviCRM and it's management of "constituent information".
These screenshots show the problem clearly. They do contain actual user personal information, and I'd like them deleted on close of this ticket 
Attachments
Activity
the bug is still open. It is marked as "Fix" for 1.5 which means that we will fix this bug in the 1.5 code base. u should download a new revision after we close the bug
I just fixed a few issues which are related to this issue (IMO). can u please download the latest code base (7265) and see if that solves the issue. If not i'll need ssh access to your server and the ability to edit the files to debug and fix the issue
thanx
lobo
7265 doesn't seem to be a working version. the drupal module has a syntax error in it.
This is a a data consistency problem, there were multiple 'Home' locations and multiple 'address' for the same location. we will add unique indexes in 1.6 to prevent this in future
mysql returns results in different order for similar queries. fixing this might be challenging 
Verified fixed as of 4.0.7, European Code Sprint 12/2011.
This is marked as 'fixed in 1.5' so I installed the latest build (rev7076) on our stage server.
The problem still occurs.