Error in the Warhammer 4th ed Character Sheet?

Hi, today an error occured in the Warhammer Fantasy 4th ed character sheet. Annyone else has this problem, and if your are a creator can you fix it please? The problem is that the background picture is gone/corrupt showing picture below.

 I have the same Problem

The background image link have stopped working, so I'd suspect the image was linked to some random place on the internet, and hasn't been uploaded to github. The author will need to track down a new version of the image and upload it to github, and change the URL linking to it.

Is there a way for us to just remove the background image entirely?  

Yeah, someone have submitted a fix for it <a href="https://github.com/Roll20/roll20-character-sheets/pull/5803" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/5803</a>

Andreas J. said: Yeah, someone have submitted a fix for it <a href="https://github.com/Roll20/roll20-character-sheets/pull/5803" rel="nofollow">https://github.com/Roll20/roll20-character-sheets/pull/5803</a> How do i fix, it, i need an idiots guide.

Yeah, same. Really hope the author fixes this issue. I have two games running and some of my players can't even see certain things.

A temp fix is that you can disable the background image manually using the browser's right-click "Inspect" element on the background, navigate to &lt;div class="charmancer tab-pane charsheet" style="display: none;"&gt;&lt;/div&gt; and un-check the background-image found in the .charsheet class. This only works for the person disabling the background-image and it will return to the default upon reloading the game. You could also create a stylus script to style the sheet however you like. (ie no background image)&nbsp; Only works for you, but it's an option to override a sheet's default styling. toggle it on/off on your warhammer game @-moz-document url-prefix("<a href="https://app.roll20.net/editor/" rel="nofollow">https://app.roll20.net/editor/</a>") { .charsheet { background-image: none !important; } }

Since a fix is submitted, all you have to do is wait. It will appear either today or next tuesday, depending on whether it got in for this weeks update window.

Okey, thanks to both of you two for the answers.

I caught this post and merged in the submitted pull request to fix it. Should be fixed within the next hour. - Cassie

Thanks for the help.