There is a behavioral difference between Dataverse v6.5 and Dataverse v6.11 that appears to be a bug. After uploading a thumbnail image to a dataset, it cannot be viewed from either the dataset page or the dataverse page.
![]()
![]()
![]()
This issue occurs because getThumbnailUrl() in Dataset.java checks that thumbnailFile is not null:
public String getThumbnailUrl() {
return thumbnailFile != null ? SystemConfig.getDataverseSiteUrlStatic() + "/api/datasets/" + this.getId() + "/logo" : null;
}
However, after uploading a thumbnail image, thumbnailFile is explicitly set to null:
Java
public Dataset setNonDatasetFileAsThumbnail(Dataset dataset, InputStream inputStream) {
[....]
dataset = DatasetUtil.persistDatasetLogoToStorageAndCreateThumbnails(dataset, inputStream);
dataset.setThumbnailFile(null);
dataset.setUseGenericThumbnail(false);
return merge(dataset);
}
I think that the getThumbnailUrl() method should check !useGenericThumbnail instead of thumbnailFile != null.
Hmm, do you think the behavior changed to due #12403 which was included in 6.11?
Yes, sure. Before these changes , the file was accessed from the ThumbnailServiceWrapper.java without checking the contents of thethumbnailFile variable.
String url = SystemConfig.getDataverseSiteUrlStatic() + "/api/datasets/" + dataset.getId() + "/logo";
Now, it checks for null first in the Dataset.java file:
return thumbnailFile != null ? SystemConfig.getDataverseSiteUrlStatic() + "/api/datasets/" + this.getId() + "/logo" : null;
Gotcha. Thanks.
For the dataset page, I can see the dataset-thumbnail as the author but not when I'm logged out:
![]()
Do you see the same?
Thanks,
In my case, I do not see the logo in both cases. Only I can see the logo from the "Thumbnails + Widgets" edition page .
Interesting. Are you thinking about creating an issue or pull request?
Ok, I will create the issue and the pull request.
Thanks! ![]()
Created the issue: #12666 and pull request #12667
Wow, both! Thanks!
Hi @Philip Durbin ๐ Should I do something more with the bug or the pull request?
@Juan nope! It's in the "ready for QA" column on our board.
The CI tests are failing, but it's not your fault. I'm pretty sure we fixed that testCreateSoftwareDatasetNative thing.
You could rebase the branch to get the tests to run again.
Perfect, after running the rebase there are not failing tests.
Last updated: Oct 02 2026 at 18:51 UTC