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

    I keep getting error with Modx 0.9.5.... I can’t log into the server..... it keeps giving a popup windows telling me that there’s and 500 Internal Sever error

    My client has a space at godaddy...

    I could log in without any problem with Modx 0.9.5 Beta... its was working really good... and then i updated to this final release.... i cant even log in .... i can see the site without any problem... but if i need to make any changes ....i can’t log in....

    Thanks in Advance..

    let me know if you need more info

    This is the error that i get.... before it happens

    « 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 `database_name`.modx_manager_log(timestamp, internalKey, username, action, itemid, itemname, message) VALUES('1169355288', '1', 'admin', '76', '-', '-', 'Reource management') 
    






      • 33372
      • 1,611 Posts
      Hmm... Well GoDaddy doesn’t allow PHP directives in your .htaccess flie, so make sure that you haven’t got any of those. You need to set register_globals to off using a php.ini file instead.

      That error looks as if you somehow lost the auto-increment values in your manager_log table. Why don’t you try emptying that table? You can back it up first if you care to keep that data.
        "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
        • 4849
        • 15 Posts
        Quote from: ZAP at Jan 20, 2007, 11:17 PM

        Hmm... Well GoDaddy doesn’t allow PHP directives in your .htaccess flie, so make sure that you haven’t got any of those. You need to set register_globals to off using a php.ini file instead.

        That error looks as if you somehow lost the auto-increment values in your manager_log table. Why don’t you try emptying that table? You can back it up first if you care to keep that data.

        Thanks zap

        As for the PHP directive.. they do allow it in .htaccess... its working perfectly... the FRUL is also working perfectly..... their register global are off by default.....

        yes you are right.. instead of emptying the table ... all i did was just changed the "id" to auto increment... and that solved the problem...

        But i would like to know ... what procedure do i need to follow in order to transfer my local db to production db...... the backup option in modx doesn’t work with the godaddy sql server.... since i am using MySQL 5.0 for the development... and i guess these guys must be using a lower version..... when i transfer.... they start spitting out all kind s of errors..... I use the local phpmyadmin to backup the db....

        What really worries me is that ... when i transfer this db to the production site (godaddy)... all the id values in all the tables don’t have the extra value of "id" to auto increment.......

        Am i doing something wrong huh

          • 28042 ☆ A M B ☆
          • 24,524 Posts
          Check all the options in the form when you do the backup, there are quite a number of them, including a checkbox to include the auto-increment values, as well as an option to create a dump compatible with various versions of MySQL.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 4849
            • 15 Posts
            Quote from: sottwell at Jan 21, 2007, 05:57 AM

            Check all the options in the form when you do the backup, there are quite a number of them, including a checkbox to include the auto-increment values, as well as an option to create a dump compatible with various versions of MySQL.
            Thanks scott

            I did all kinds of experiment with the SQL..... tried with and without auto increment selected...... still the extra column in "id" doesnt have the auto increment on them...

            The site is working fine even without this (expect for the above error which is corrected now)

            Its just that i hope it doesn’t break the site later on....

              • 22303 MODX Staff
              • 10,725 Posts
              If that auto increment was messed up, I can almost guarantee you the rest of the tables will have the same problem. This typically happens when going from 4.1+ (including 5+) to 3.23. There are compatibility modes when using mysqldump, which you need to take advantage of when doing such migrations. But ultimately, IMO, if you have a host running that old of a MySQL database, well, I’ll spare you the obvious...