We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 10223
    • 9 Posts
    Preview window is turned off.

    For some other info the error started happening when the domain for the site was activated.
      • 33372
      • 1,611 Posts
      Were you accesssing the site via IP address before? If so, check your configurations and clear the site cache. It almost sounds to me as if your session variables are freaking out in some new and unique way, but clearing the site cache may resolve that for you.
        "Things are not what they appear to be; nor are they otherwise." - Buddha

        "Well, gee, Buddha - that wasn't very helpful..." - ZAP

        Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
        • 10223
        • 9 Posts
        I was accessing the site via some obscure web address and it was possible using ip too. Now neither the obscure web adress, the ip or the domain can login to the manager.

        As for clearing the site cache I have used the button located under "Site > Clear Cache" a number of times with no success.

        The manager that I currently have logged in is using the obscure web address.
          • 33372
          • 1,611 Posts
          Line 1287 of that file adds an alert to the system log. Is your system log by chance totally overloaded with billions of errors? If at some point you were getting stuck in an error loop and the database table filled up with megs and megs of errors, I could imagine this causing a timeout error.

          You can empty this table in the backup manager or via the system events log page (or using phpMyAdmin, etc.).

          If you do find a ton of errors in there, let us know what they say.
            "Things are not what they appear to be; nor are they otherwise." - Buddha

            "Well, gee, Buddha - that wasn't very helpful..." - ZAP

            Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
            • 10223
            • 9 Posts
            I have solved the problem.

            As it turns out it was something I actually knew about but forgot about it until you got me into phpmyadmin.

            The reason for the error was that all the auto_increment settings disappeared from my database due to the fact that I went from mysql 5 on one server to mysql 4 on the other server.

            The error that basically was the root to the evil was this:
            « MODx Parse Error »
            MODx encountered the following error while attempting to parse the requested resource:
            « Execution of a query to the database failed - Duplicate entry '0' for key 1 »
                  SQL: INSERT INTO `primabager_dk_-_modx`.modx_manager_log(timestamp, internalKey, username, action, itemid, itemname, message) VALUES('1168306903', '1', 'admin', '114', '-', '-', 'View event log')
                  [Copy SQL to ClipBoard]
             
            Parser timing
              MySQL: 	0.0009 s	(1 Requests)
              PHP: 	1168306903.4466 s	 
              Total: 	1168306903.4475 s	 


            Thanks very much for the help.
              • 33372
              • 1,611 Posts
              Aha! Glad you figured it out. That makes perfect sense (now that we know what it is)...
                "Things are not what they appear to be; nor are they otherwise." - Buddha

                "Well, gee, Buddha - that wasn't very helpful..." - ZAP

                Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
                • 10223
                • 9 Posts
                Stuff like this always does smiley