Closed (won't fix)
Project:
Bibliography & Citation
Version:
2.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Feb 2023 at 19:46 UTC
Updated:
29 Jul 2025 at 16:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
a_khalipau commentedComment #3
a_khalipau commentedComment #4
a_khalipau commentedComment #5
kpaxman commentedI wasn't seeing this in the latest tag, but this seems to have been introduced with #2992234: Deprecated packages in dependencies which has been merged into dev for both 2.x and 3.x but only tagged against 3.x from what I can see.
This does fix the issue for me, but I'm not sure if the fix would affect anything else, so I'm setting this to needs review.
This may be a duplicate of #3385290: Trim given name
Comment #6
mark_fullmerComment #7
mark_fullmerI attempted to reproduce this problem on the 3.0.x-dev branch today and was unable to do so. Steps taken:
1. Create a new Contributor at /admin/content/bibcite/contributor , entering a Middle Name and a Surname, but not a First Name.
2. Create a Reference and associate it with this Contributor.
3. Render this using the (default) APA style citation formatter provided by the module.
4. Observe that there is no duplicative "double period" as described in the issue report.
I also tried populating a whitespace character for the first name, and separately for the middle name.
If this is still a problem, please provide additional steps to reproduce. Also, if it is a problem, it might more appropriately be addressed in https://github.com/ADCI/full-name-parser, which is a dependency of this module.
Comment #8
istryker commentedI can confirm this is a problem in version 2.0.x and D9
I can confirm this is no longer a problem in version 3.0.x on D10
Comment #9
istryker commentedComment #10
benjifisherLooking at the patch from #4, I am pretty sure that this issue was fixed (on the 3.0.x branch) in #3155552: Contributor with no first or middle name results in incorrect processing (e.g., APA format).
At least, the patch here has pretty much the same effect as the change from that issue. It is possible that the symptom of the problem changed from some earlier commit, especially since (Comment #7 here) the problem could not be reproduced on the 3.0.x branch in June, but the other issue was not fixed until July.