Cannot upload covers

[Antonio Citati]

Recently when uploading covers of one comic book I always get the following error: The remote server returned an error: (500) Internal Server Error, while sending data. 
This happen only and always with the same title. Attached below the link to this title on Atomic Avenue, all previous cover were my uploads and never had this issue before.
https://atomicavenue.com/atomic/TitleDetail.aspx?TitleID=54943
 

Thank you

[Mark J. Castaneda]

you may be running an older build for CB2020. Download/install the latest program installer from your online account here and let us know if it works out for you: https://www.comicbase.com/mycb/Registrations.aspx

[Antonio Citati]

Mark, I am running buil 3250. And this error happens only and exclusively with the above title. All other covers so far are uploading withouth any issue.

[Mark J. Castaneda]

It's most likely that special (è) in the 2nd word in the title name that's being problematic. I'll let our programming team know about it.

[Antonio Citati]

Yes I agree about that being the probable cause of the issue.
Covers for this title were uploaded without issues on earlier builds, thus it must be some small bug. 
Righ now if right click and "Browse this title on Atomi Avenue" I get:

Titles containing “Martin Mystère le nuove avventure a colori”

So the "è" si somehow changed in "è", and of course the title is not found.

However adding new issues seems to be OK.

Antonio

[Jeff Egan]

Apologies if this is the wrong thread, but the drag and drop cover feature doesn't seem to be working for me. I've scanned the cover (Monstress Volume 3) @ 496x744 - 393K named BK 3.jpg. When I try to drag and drop onto the grid (or the line item cover or the large picture area at the top of the screen), I get the "do not enter" slash circle symbol.

 

[Mark J. Castaneda]

scan you screenshot this message?

[Jeff Egan]

Sorry, it wasn't not an error message. The mouse cursor changes when try to drag the image file from File Explorer over to the ComicBase.

[Jeff Egan]

Okay, so... apologies again. The classic windows solution (reboot) seems to have fixed it. Thanks for your help!