You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On book description, I can see that it is taking Publisher Year from the m4b's file metadata Recorded Date, which contain YYYY-MM-DD
Upon opening up in "Details" section, the Publisher Year section is empty.
In metadata.json the YYYY-MM-DDT00:00:00.000Z is recorded in the publishedYear section. (publishedDate is null)
This screenshot shows this in detail.
What did you expect to happen?
Publish Year in Detail pop up will have the same information which is displayed in the main page.
Steps to reproduce the issue
Import a m4b with metadata as below: (ffprobe output)
date : 2022-10-12T00:00:00.000Z
Open the book item in Audiobookshelf
Edit the Details
Audiobookshelf version
2.17.4
How are you running audiobookshelf?
Debian/PPA
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Chrome
Logs
No response
Additional Notes
No response
The text was updated successfully, but these errors were encountered:
What happened?
On book description, I can see that it is taking Publisher Year from the m4b's file metadata Recorded Date, which contain YYYY-MM-DD
Upon opening up in "Details" section, the Publisher Year section is empty.
In metadata.json the YYYY-MM-DDT00:00:00.000Z is recorded in the publishedYear section. (publishedDate is null)
This screenshot shows this in detail.
What did you expect to happen?
Publish Year in Detail pop up will have the same information which is displayed in the main page.
Steps to reproduce the issue
Audiobookshelf version
2.17.4
How are you running audiobookshelf?
Debian/PPA
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Chrome
Logs
No response
Additional Notes
No response
The text was updated successfully, but these errors were encountered: