The browser console reports a 400 error when attempting to retrieve the logo. The dspace log issues a warning,
Invalid mime type "Unknown": does not contain '/' at: org.springframework.http.MediaType.parseMediaType(MediaType.java:634)) because for some reason, the logo is assigned a bitstream_format_id = 1 (Unknown) in the bitstream table. As I mentioned, this is the same sample image I have used for new items, so it *should* work. The frontend and backend are as 'plain vanilla' as they can be. My apache setup is identical to the one in the documentation, but I have to wonder if there is a httpd configuration problem? ~~Bill On Mon, Jul 15, 2024 at 4:46 PM DSpace Technical Support < [email protected]> wrote: > Hi Bill, > > Similar to your other posting, I tried this out in vanilla DSpace 7.6.2 > using the Docker setup described at > https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7. I was able to > upload logos into both a Community and a Collection, and had no issues > viewing them. > > The fact that your issues are specific to Communities & Collections makes > me wonder if you've somehow customized the Community & Collection forms? > If so, my guess would be that you may have customizations that are no > longer valid/working for DSpace 7.6.2 (and you may want to revert them, see > if that fixes the bugs, and try them again). > > As always, I think the best step is to try to follow the Troubleshooting > Guide to look for errors as well (though I'm guessing you may have already > tried that based on your other email): > https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove) > > Hopefully if someone else hits this issue, they will also report it. But, > right now, I cannot find a way to reproduce this in 7.6.2, so I suspect > it's something on your end (either custom code, or some issue in your > upgrade process). > > Tim > > On Thursday, July 11, 2024 at 11:28:42 AM UTC-5 [email protected] wrote: > >> In DSpace 7.6.2, site admins can successfully upload a community or a >> collection logo. However, the bitstream is assigned a bitstream format = >> 1, unknown, and thus cannot be viewed. I have tested this behavior with a >> number of bitstreams with the same result. I have tested with >> known-to-work bitstreams (that is, existing community/collection logos). >> Also, these same bitstreams can be be uploaded to items, and the format >> will be recognized and assigned correctly. >> >> There are no errors or warnings in any logs; all the data in the >> bitstream table is accurate, except for the bitstream_format_id. >> >> My workaround is to UPDATE the bitstream table with the correct format. >> Is anybody else experiencing problems with this? >> Regards, >> ~~Bill >> > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/1b7fa2b1-1a86-4e45-bed7-0bab80cd290an%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-tech/1b7fa2b1-1a86-4e45-bed7-0bab80cd290an%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- ______________________________________ Bill Tantzen University of Minnesota Libraries 612-626-9949 (U of M) 612-325-1777 (mobile) -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CADgrb7HkEtX2fimcdJ22QPw79P%2BUzwjRp1Zn92LjAhd3UQn9DQ%40mail.gmail.com.
