Blank page at first connection

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Bking
    Junior Member
    • Jul 2018
    • 5

    Blank page at first connection

    Hello,

    My instalaltion went well.

    But when it goes to the end of the installation I have a blank page.

    We have in the EspoCRM browser tab and at the bottom © 2018 EspoCRM.

    But no display ...

    Thank you for your help and forgiven my english.
  • yuri
    Member
    • Mar 2014
    • 8440

    #2
    Hi,



    Also check file permissions: https://github.com/espocrm/documenta...-based-systems
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

    Comment

    • A. Conrads
      Junior Member
      • Aug 2018
      • 12

      #3
      Hi,
      I have the same issue with Firefox 60.0 and EspoCRM 5.3.2 on a Bitnami-Google-Cloud-Stack.

      After clearing the cache and rebuilding via ssh ("INSTALL-DIRECTORY"/htdocs$ sudo php clear_cache.php and "INSTALL-DIRECTORY"/htdocs$ sudo php rebuild.php) it´works, but just in one Firefox window, after some reloads (F5).
      When I open a new tab (e.g. Calender + Leads), I get the same blank screen in the new tab.

      With Chrome everything works just fine. Seems to be a browser problem...

      Comment

      • tanya
        Senior Member
        • Jun 2014
        • 4308

        #4
        Could you check on your browser, whether demo works fine?
        Also press F12 and check in browser console on errors

        Comment

        • A. Conrads
          Junior Member
          • Aug 2018
          • 12

          #5
          Hi tanya,
          thanks for looking into this matter. Strangely, the demo seems to work fine with Firefox.


          I've tried F12 in Firefox with my installation and found an error:

          Code:
          [FONT=courier new]unreachable code after return statement  espo.min.js:206:12 [/FONT]
          With Chromium I got the following message, but with Chromium/Chrome everything seems to work without any problems:

          Code:
          [FONT=courier new][Violation] Forced reflow while executing JavaScript took 30ms
          
          [Violation] Forced reflow while executing JavaScript took 31ms
          
          espo.min.js,qr=1534141274.pagespeed.jm.CfpX1x0i4a.js:1 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
          add @ espo.min.js,qr=1534141274.pagespeed.jm.CfpX1x0i4a.js:1
          (anonymous) @ espo.min.js,qr=1534141274.pagespeed.jm.CfpX1x0i4a.js:1
          each @ espo.min.js,qr=1534141274.pagespeed.jm.CfpX1x0i4a.js:1
          each @ espo.min.js,qr=1534141274.pagespeed.jm.CfpX1x0i4a.js:1
          on @ espo.min.js,qr=1534141274.pagespeed.jm.CfpX1x0i4a.js:1
          e.bindDateHandlerToEl @ VM131:2
          e.bindToEl @ VM131:7
          e.setElement @ VM131:2
          e.renderSkeleton @ VM131:4
          e.setElement @ VM131:7
          e.setElement @ VM131:2
          t.renderView @ VM131:4
          t.initialRender @ VM131:4
          t.render @ VM131:4
          (anonymous) @ VM131:6
          each @ espo.min.js,qr=1534141274.pagespeed.jm.CfpX1x0i4a.js:1
          each @ espo.min.js,qr=1534141274.pagespeed.jm.CfpX1x0i4a.js:1
          r.fn.fullCalendar @ VM131:6
          (anonymous) @ VM124:728
          
          [Violation] 'setTimeout' handler took 133ms[/FONT]

          Comment

          • tanya
            Senior Member
            • Jun 2014
            • 4308

            #6
            There are not valuable messages.

            Comment

            • A. Conrads
              Junior Member
              • Aug 2018
              • 12

              #7
              Maybe there is something wrong with a return statement in the JavaScript file "htdocs/client/espo.min.js". The Firefox error message pointed to a specific function statement, which I highlighted:

              Code:
               [...] function Ta(a, b) {
                      var c, d = 0, e = {
                        [B]  [U]height: a[/U][/B]
                      };
                      for (b = b ? 1 : 0; 4 > d; d += 2 - b)
                          c = R[d],
                          e["margin" + c] = e["padding" + c] = a;
                      return b && (e.opacity = e.width = a),
                      e
                  } [...]
              Since I'm not exactly a big coder, especially when it comes to JavaScript, I hope someone finds himself more knowledgeable than me to solve the problem. Nevertheless, I'll keep trying to find the bug. Hopefully it's just a missing curly bracket or a semicolon...

              Comment

              • A. Conrads
                Junior Member
                • Aug 2018
                • 12

                #8
                It seems like the same issue has been solved in another thread:

                Hello, We have been getting a lot of clients that have been getting a white screen on portal login. I haven't seen this until today. I cannot replicate this


                I deactivated pagespeed in "/apps/espocrm/conf/htaccess.conf" by adding the following lines at the end of the file:

                Code:
                <IfModule pagespeed_module>
                  ModPagespeed off
                </IfModule>
                Now EspoCRM works fine with Firefox. Blank-page problem solved. Even if the espo.min.js-error in Firefox still exists...

                Comment

                Working...