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

    after a smooth upgrade from 2.2.14 to 2.3.1, clicking on Extras > MIGX I get the following error message:
    Fatal error: Class 'IndexManagerController' not found in #####/core/model/modx/modmanagerresponse.class.php on line 185
    Before upgrading MODX I had upgraded MIGX (via Package Manager) to the newest version, compatible to MODX 2.3.

    What can I do?


    BTW: After the upgrade to MODX 2.3 I got the Warning about an error updating the table for the class modResource, saying
    Array
    (
    [0] => 42000
    [1] => 1061
    [2] => Duplicate key name 'cache_refresh_idx'
    )
    I assume this is harmless - is it?

    This question has been answered by multiple community members. See the first response.

    • discuss.answer
      Try re-installing MIGX. You can take it a step further and uninstall it then re-install it if that doesn't work.
        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
        • 4172
        • 5,888 Posts
        yeah, you need to reinstall MIGX (and maybe other Extras) after upgrading, because of different CMP-action-handling in 2.3
        The menu needs to be recreated for 2.3
          -------------------------------

          you can buy me a beer, if you like MIGX

          http://webcmsolutions.de/migx.html

          Thanks!
        • I've had this happen with various add-ons every time I upgrade. Usually just a reinstall fixes them, sometimes I have to uninstall and reinstall.
            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
            • 22427
            • 793 Posts
            Thank you both; reinstalling MIGX helped.

            But I'm clueless how to recreate the menu for my custom table.

            I found the entry with no parent, and was able to move it into the topnav (where it was before). Clicking the item in the topnav gives the error
            "Could not find action file at: controllers/default/index.php".

            Editing the menu item, I found Namespace set to core (why?) and Action set to 84, obviously the former ID of the action. Besides the correct &config parameter and the Parent now set to topnav, the other fields are empty.

            In 2.2.14 there was a Main Menu list and a list of Actions left to it; so you could associate a menu item to an action. But now there is no Actions list anymore.

            In the Documentation I tried to understand the section "Custom Manager Pages in 2.3", but not beeing a Developer I do not catch what to do.

            In the section "Action List" I read:
            Before MODX 2.3 each action has its own ID, but as of MODX 2.3 actions have been deprecated and are no longer used. Instead, as of Revolution 2.3, the action name is passed in the a parameter directly.
            and, further down,
            For backwards compatibility, the MODx.action variable is still present in 2.3, but instead of IDs it contains the controller names as usual. This variable will be removed in 2.4 or 3.0 though, so do NOT rely on it for too long.

            Now please help me: What should I do?
              • 4172
              • 5,888 Posts
              action: index

              namespace: migx
                -------------------------------

                you can buy me a beer, if you like MIGX

                http://webcmsolutions.de/migx.html

                Thanks!
              • discuss.answer
                • 22427
                • 793 Posts
                Thanks Bruno, that's it.
                In fact I remember now these values. But after the upgrade to 2.3.1 I could not view them anymore, and my short-term memory is getting worse from day to day... (I'm sorry if I sounded a bit ranting, it was not intended.)