- Issue created by @Finn Lewis
- Status changed to Postponed: needs info
9 months ago 7:04am 13 March 2024 Hi Finn Lewis
Update issue title since we don't use AcademicPuma.
Could you provide an example of such reference to let us check this issue?- π¬π§United Kingdom Finn Lewis
Hi AardWolf!
Thanks for the reply.
The link to the commit I included above is where you swapped AcademicPuma to Seboettg
https://git.drupalcode.org/project/bibcite/-/commit/d9976bb3de1d619b1f73...
That was 03 August 2023
The current 2.0.0-beta3 is from 5th July 2023 and includes the AcademicPuma package: https://git.drupalcode.org/project/bibcite/-/blob/2.0.0-beta3/composer.j...
The current 3.0.0-beta3 is also from 5th July 2023 and includes the AcademicPuma package: https://git.drupalcode.org/project/bibcite/-/blob/3.0.0-beta3/composer.j...
It would be great if you can tag new releases with the swap from AcademicPuma to Seboettg.
Many thanks,
Finn
- πΊπΈUnited States dane powell
I got this error after upgrading to 3.x-dev as well. I think it's partially a problem with bibcite migrations, because a piece of content that was previously listed in biblio with the month as "July-September" got created in bibcite with the date published "July-September", which is invalid.
This seems to be only a problem with this date format; normally-formatted dates seemed to be imported correctly.