-
- 289 Posts
I updated SVN to the latest revision today and now I’m getting the following error.
Errors were encountered during core installation. Please review the installation results below, correct the problems and proceed as directed.
*
Error creating table for class modAccessActionDom
*
Error creating table for class modActionDom
*
Error upgrading table for class modAction
Array
(
[0] => 42000
[1] => 1061
[2] => Duplicate key name ’namespace’
)
*
Error upgrading table for class modAction
Array
(
[0] => 42000
[1] => 1061
[2] => Duplicate key name ’controller’
)
*
Error upgrading table for class modMenu
Array
(
[0] => 42000
[1] => 1061
[2] => Duplicate key name ’parent’
)
*
Error upgrading table for class modMenu
Array
(
[0] => 42000
[1] => 1061
[2] => Duplicate key name ’action’
)
*
Successfully upgraded table for class modMenu
Added new index on `text` for table ``modx_menus``.
*
Successfully upgraded table for class modMenu
Changed `parent` field to `parent varchar` on table ``modx_menus``.
*
Error upgrading table for class modMenu
Array
(
[0] => 42000
[1] => 1075
[2] => Incorrect table definition; there can be only one auto column and it must be defined as a key
)
*
Error upgrading table for class modMenu
Array
(
[0] => 42000
[1] => 1064
[2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ’UNSIGNED NOT NULL PRIMARY KEY FIRST’ at line 1
)
*
Error upgrading table for class modMenu
Array
(
[0] => 42000
[1] => 1068
[2] => Multiple primary key defined
)
*
Successfully upgraded table for class modMenu
*
Config file successfully written.
*
Config file permissions successfully updated.
I upgraded it exactly the same way I have done after updating from SVN. I go to _build and run ’php transport.core.php’ and then run the MODx installer and upgrade.
Any idea what’s going on or how to fix it?
I'm learning more about MODx all the time and loving it.
-
- 289 Posts
Hmm. Thanks for pointing out the other topic, but I think I’ll wait a while and see if it gets fixed. My site still works, so I’m not too concerned about not being able to use the manager.
If worst comes to worst, I’ll just do a fresh install. I luckily still have a working copy of the website in another directory using another database (why I do is another story), so I’d be able to get everything back.
I'm learning more about MODx all the time and loving it.