blank screen after update to 2.6.0 from 2.5.1
Moderators: Developer, Contributor
blank screen after update to 2.6.0 from 2.5.1
Windows Server 2012 R2
mantis 2.6.0
PHP 5.5
MySQL
I had to upgrade PHP from 5.3 to 5.5 because of that "guzzle" error thingy, which I did using the web installer in IIS console. Then unpacked the new version of Mantis into a new directory. It went through the install perfectly as far as I can tell, it says GOOD all the way down the line, and the mysql database updated fine with no errors, but when i clicked the Login link all I get is a blank screen with just the header as shown in the attachment. No footer either.
Using active directory auto login with the AdLogin plugin which has worked flawlessly so far, but I don't think it has anything to do with not seeing anything on the page. Any thoughts please? Screenshot is only of the top of the page but the rest of the page is that same flat gray color with no text at all.
mantis 2.6.0
PHP 5.5
MySQL
I had to upgrade PHP from 5.3 to 5.5 because of that "guzzle" error thingy, which I did using the web installer in IIS console. Then unpacked the new version of Mantis into a new directory. It went through the install perfectly as far as I can tell, it says GOOD all the way down the line, and the mysql database updated fine with no errors, but when i clicked the Login link all I get is a blank screen with just the header as shown in the attachment. No footer either.
Using active directory auto login with the AdLogin plugin which has worked flawlessly so far, but I don't think it has anything to do with not seeing anything on the page. Any thoughts please? Screenshot is only of the top of the page but the rest of the page is that same flat gray color with no text at all.
Re: blank screen after update to 2.6.0 from 2.5.1
First thing I did. Event log is clean. So I enabled the Chrome browser F12 and hit refresh and it got a lot of errors from the Mantis code, here is one:
So I'm thinking that CSP is an issue here, and also that jQuery needs to be updated bigtime. I do not have that stuff embedded in our server so it is something in Mantis code, probably in some web.config file. Any clues?
Code: Select all
jquery-1.4.2.min.js:35 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-fI9e0uZCn776er+wVLLndgMnhp43quxPFQpVl1be9Gk='), or a nonce ('nonce-...') is required to enable inline execution.
Re: blank screen after update to 2.6.0 from 2.5.1
Ugh. Please remove my mushu999 account that was erroneously created a while ago, or tell me how to delete it myself. I posted my reply using that account, thus the moderator approval required. Bleh.
Re: blank screen after update to 2.6.0 from 2.5.1
So I'm a bit closer. In Chrome's developer window it said there are 13 errors. I opened an incognito browser tab and loaded the page, and it said I had only 4 errors. So I'm thinking there's some browser extension causing errors on the page, but still not sure why the previous version of Mantis didn't exhibit the same errors. Troubleshooting sucks.
Re: blank screen after update to 2.6.0 from 2.5.1
No idea at the moment. Maybe because you changed source (add headers to prevent CSP violations) or you used a 3rd plugin which added own security headers.mushu wrote:but still not sure why the previous version of Mantis didn't exhibit the same errors.
Re: blank screen after update to 2.6.0 from 2.5.1
Figured it out! Because the new Mantis requires at least version 5.5 of PHP, I upgraded from 5.3 but failed to enable LDAP support, which is a separate operation it seems. Good grief. That's what I get for not being a PHP coder...everything seems to be working great now. I have no clue about the CSP server header and other weird errors, except that perhaps browser plugins had something to do with it. /smh
Re: blank screen after update to 2.6.0 from 2.5.1
HOWEVER I'm still getting errors in the Chrome console, any ideas on these? I think it has something to do with the default theme:
Code: Select all
my_view_page.php:1 Refused to load the image 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAABCAIAAAC32dI2AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAChJREFUeNpi/PHjx+vXr1lYWNjY2JiYmBgwACMj4////xlhAKgeIMAASS0LwKQtQ+QAAAAASUVORK5CYII=' because it violates the following Content Security Policy directive: "img-src 'self'".
ace.min.js:19 Refused to load the image 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAARCAIAAAC0D9CtAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAKZJREFUeNrckj0KxCAUhNcfREuvYBEI2tilS+NBrLyP58wBkiLqPpSwi9mwqTPFIPo+Rh6Dtm1bloVSyhjDGL8OIYRKKeDfNyCY/wzd19MYevVACIE15pxTSrdyGjBNEzic/zOkahxHznkI4Yzhn4AxRmvtnLPWxhg7DHU9APfeK6WGYZBSCiEgbV3XeZ73fW896JmWc/5wrmpMv7dUddW3Z3bnLcAAeoZCNib0zPQAAAAASUVORK5CYII=' because it violates the following Content Security Policy directive: "img-src 'self'".
e.scrollTop @ ace.min.js:19
(anonymous) @ ace.min.js:19
dispatch @ jquery-2.2.4.min.js:3
r.handle @ jquery-2.2.4.min.js:3
trigger @ jquery-2.2.4.min.js:4
triggerHandler @ jquery-2.2.4.min.js:4
(anonymous) @ ace.min.js:19
(anonymous) @ ace.min.js:19
Re: blank screen after update to 2.6.0 from 2.5.1
One more thing I had to do was edit the web.config file in the base program directory and add the following sections:
Which removed more Chrome console errors since IIS doesn't know about the woff/woff2 font formats natively.
Code: Select all
<fileExtensions>
<add fileExtension=".svg" allowed="true" />
<add fileExtension=".woff" allowed="true" />
<add fileExtension=".woff2" allowed="true" />
</fileExtensions>
<staticContent>
<remove fileExtension=".woff" />
<remove fileExtension=".woff2" />
<mimeMap fileExtension=".woff" mimeType="application/font-woff" />
<mimeMap fileExtension=".woff2" mimeType="application/font-woff2" />
</staticContent>
Re: blank screen after update to 2.6.0 from 2.5.1
Fully solved. It was an extension in Chrome: Win 7 Scrollbars available in the Store even. Not updated since 2014, apparently it really messes with Chrome internals. I removed it and now have zero console errors. Just putting all this info in the thread in case it helps someone later!