Bug #1465
closedusing references in dpw causes duplicate reference ids
0%
Description
I created a new package with the dpw, and added several
contacts/owners/assocParties from other packages as well as adding some
manually. When i tried to validate the document, it failed because at least two
of the elements had been given the same id. Here is the xml produced:
<creator id="1081179008226">
<individualName>
<salutation>mr</salutation>
<givenName>chad</givenName>
<surName>berkley</surName>
</individualName>
<organizationName>NCEAS</organizationName>
<positionName>Programmer</positionName>
<address>
<deliveryPoint>735 State St. #300</deliveryPoint>
<city>Santa Barbara</city>
<administrativeArea>CA</administrativeArea>
<postalCode>93121</postalCode>
<country>US</country>
</address>
<phone phonetype="voice">8054039515</phone>
</creator>
<associatedParty id="1081179008226">
<individualName>
<salutation>mr</salutation>
<givenName>chad</givenName>
<surName>berkley</surName>
...
Updated by Chad Berkley about 20 years ago
this bug only seems to happen when you try to use references to include more
than one contact/owner/assocParty. If I just use one, this doesn't happen.
Updated by Dan Higgins about 20 years ago
I can reproduce this bug by 'copying' a reference. Apparently the id is simply
copied also! (Still need to find the actual code.)
Updated by Dan Higgins about 20 years ago
A new ID was not being created when a party reference was edited and copied (as
opposed to editing of the reference itself). The fix was to set the
'referenceIdString' in the PartyPage class to null when the choice to copy the
info is made. This causes the getRefID method to reset the ID in the copy.