We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36632
    • 202 Posts
    I have an Advanced 2.2.1 upgrade. The Manager login still displays the pre-2.0 login panel. This has been going on since a 2.1.3 upgrade to 2.0.0.

    I cleared the core/cache/ Cleared my browser cache. Cleared cache in Manager. Flushed Sessions.

    Viewing the Manager files, they all got updated. So..... what can I do to manually replace the login screen files? I don't see where Setup writes over manager/index.php (which is what I think the fault lies).

    Be nice to show my client that the login is no longer that boring grey.
      • 22303 MODX Staff
      • 10,725 Posts
      If using advanced, make sure all of the core files are writable by the PHP process; otherwise, it will fail to update those files when installed.
        • 36632
        • 202 Posts
        All of them are writeable, and always have been. The server is IIS7.5 - would that make a difference? The Manager is writeable... I wonder if I could just manually upload a few files to correct place in Manager...
          • 22303 MODX Staff
          • 10,725 Posts
          I would not recommend using anything on Windows that depends on is_writable() checks, like the Advanced installer. Have you tried using the Traditional?
            • 36632
            • 202 Posts
            Can't. MODX Support did Rhe original install for client.

            I know how to covert trad to adv. how to do it the other way around? Just upload traditional and move core to wwwroot do you think?
              • 22303 MODX Staff
              • 10,725 Posts
              Should work, though you'll need to update the config.core.php files manually with the custom core path in the root, manager/ and connectors/ directories.
                • 36632
                • 202 Posts
                The core/ is outside the wwwroot. Couldn't I just rename the core/ to harden, move it to the wwwroot, and change the name of connectors/ and manager/ ?

                That way the core/ will probably inherit the permissions of wwwroot and it'll be less of a hassle?

                Advice please! Thank you as always.