What steps does it take to reproduce the issue?
Update to dataverse version 6.9
-
When does this issue occur?
After the update when accessing any dataset or collection page
-
Which page(s) does it occurs on?
Any
-
What happens?
The payara log shows a new [INFO] entry of the form:
css is a filename/extension Dataverse doesn't know about. Consider adding it to the MimeTypeDetectionByFileExtension.properties file.|#]
-
To whom does it occur (all users, curators, superusers)?
To sysadmins checking the payara logs
-
What did you expect to happen?
No entries should be created in payara log
Which version of Dataverse are you using?
v6.9
Any related open or closed issues to this bug report?
No
Are you thinking about creating a pull request for this issue?
Yes. In our case the patch is
--- org.file 2026-01-07 10:05:13.545763190 +0100
+++ ./src/main/java/propertyFiles/MimeTypeDetectionByFileExtension.properties 2026-01-07 10:05:54.581414557 +0100
@@ -1,5 +1,6 @@
7z=application/x-7z-compressed
ado=application/x-stata-ado
+css=text/css
dbf=application/dbf
dcm=application/dicom
docx=application/vnd.openxmlformats-officedocument.wordprocessingml.document
If this is relevant to anybody else, we could provide a PR to add the line to suppress the log-entry. There might be other options to do so that we don't know about. If that is the case we are happy to learn about them.
What steps does it take to reproduce the issue?
Update to dataverse version 6.9
When does this issue occur?
After the update when accessing any dataset or collection page
Which page(s) does it occurs on?
Any
What happens?
The payara log shows a new [INFO] entry of the form:
css is a filename/extension Dataverse doesn't know about. Consider adding it to the MimeTypeDetectionByFileExtension.properties file.|#]
To whom does it occur (all users, curators, superusers)?
To sysadmins checking the payara logs
What did you expect to happen?
No entries should be created in payara log
Which version of Dataverse are you using?
v6.9
Any related open or closed issues to this bug report?
No
Are you thinking about creating a pull request for this issue?
Yes. In our case the patch is
If this is relevant to anybody else, we could provide a PR to add the line to suppress the log-entry. There might be other options to do so that we don't know about. If that is the case we are happy to learn about them.