We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 29500
    • 2 Posts
    Hi,

    I’ve got a little problem that doesn’t let me use the manager... Install worked fine (I included the german language file from these forums but otherwise nothing was changed) and I can see the normal page and even edit it.
    You get this message "Please wait while MODx loads the page..." in the manager and this is ok but it doesn’t go away and stays there sad So I am not able to use the manager.

    Does anybody know a workaround?

    Oh, I forgot to mention that I used Firefox 1.05 under FreeBSD and Firefox 1.5 RC2, Opera 8.5 and IE 6 under Windows XP SP2... Everywhere the same error. Cannot tell you about the web server right now...

    BTW: The demo on opensourcecms.com works fine for me!
      • 18397
      • 3,250 Posts
      Can you try with the English language file? It could be that the German language file has not yet been updated but I’m not sure.

        • 29500
        • 2 Posts
        Strange... Now it’s working. Although I might add that it used to work with the german version. Whatever laugh I will just stick to the english version and be happy for a while smiley
          • 23985
          • 4 Posts
          Hmm ... I’ve just migrated from Etomite (0.6) and have the same problem under Firefox 2.0 ... it seems somewhat random though - I’d get it for a while then I close it, open a new window, re-open the manager page and it all works ... *shrug*

          I seem to recall a similar problem when I was on Etomite though (and attempting to reload would kick you back out to the login page) - and that was under Firefox 1.5 ... I never had this problem under IE though.

          Any ideas where to look for potential clues?
            • 25663 MODX Staff
            • 12,272 Posts
            This behavior could be caused by an overloaded shared server I’d suspect.
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 23985
              • 4 Posts
              I guess an overloaded server could do it but I seriously doubt that’s the case for me, the server in question is very lightly loaded (both the MySQL server and the Apache server) ... I also never got the problem (either in Etomite or MODx) using IE, it only ever seemed to happen under various versions of Firefox :-/
                • 27147
                • 53 Posts
                I’m also having this problem - on two different hosts, with Opera and IE.
                To recap: I login, get the ’Please wait...’ box, and it never goes away. Also, the document tree doesn’t load. I can navigate around the manager but can’t interact with the main frame.

                Host1: MODx 0.9.5 (en) / Apache 2.0.55 / WinXP SP2 (local)
                Host2: MODx 0.9.5 (en) / Apache 2.2.unknown / Linux 2.6.11 unknown distro (shared hosting)

                I have two user accounts in MODx and it doesn’t matter which one i login with.
                It happens with Opera 9.02, 9.10 and IE 6, IE 7 but not Firefox 1.5.0.10.

                Here’s the weird thing: it only happens when I login from this computer. Cache purge and reboot have no effect.

                Ideas anyone?
                  • 17883
                  • 1,039 Posts
                  Here’s the weird thing: it only happens when I login from this computer. Cache purge and reboot have no effect.

                  Javascript disabled? Perhaps some restrictive settings in your Firewall?
                    • 27147
                    • 53 Posts
                    I had a look at the code and found that hideLoader() was not being fired, even though it’s called both onload and by a setTimer.

                    I then put an alert() in the top of the inline script block in header.inc.php and found that that didn’t fire either. So looks like a problem with onload.

                    Then I put an alert() in mootools.js and that made the problem go away, even when I took out the alert().

                    I’m no javascripter so I’m hoping that someone more knowledgeable can tell me what’s going on. It looks like I had a bad copy of mootools.js in my cache which blocked document.onload. And yet I had emptied my browser cache in both Opera and IE.

                    It seems from other posts (see this thread also) that this is a continuing, though rare, problem in MODx and it’s a bad one because it completely breaks the interface. I hope someone can find a way to fix it for good. Does 0.9.7 use this code?
                      • 25663 MODX Staff
                      • 12,272 Posts
                      Shuriken ... the manager in 097 will be overhauled quite a bit, but will also be based heavily on the legacy code. 097 will primarily be to introduce the new API and get developers accustomed to working with MODx.

                      Could you please test the latest SVN trunk to see if you’re experiencing the same problem?
                        Ryan Thrash, MODX Co-Founder
                        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me