Unexpected Menu record properties, invalid namespace / action controller

[pixelchutes]

I'm not sure if this is an issue with MODX 2.3 compatibility, if something is perhaps hard-coded preventing setting the action & namespace properties of the menu record in the transport file, or simply user error. I will document this here in case it is a valid bug.

In my component's *.config.php file, I have configured a single menu record:

    'menus' => array(
        'justatest' => array(
            'text' => 'justatest',
            'parent' => 'components',
            'description' => 'justatest.ex_menu_desc',
            'icon' => '',
            'menuindex' => 0,
            'params' => '',
            'handler' => '',
            'permissions' => 'edit_document',

            'action' => array(
                'id' => '',
                'namespace' => 'justatest', // This shows up as 'core' after transport file install
                'controller' => 'home', // This did not appear to work either
                'haslayout' => true,
                'lang_topics' => 'justatest:default',
                'assets' => '',
            ),
        ),
    ),

My goal is this:

But what I keep getting is this:

Am I perhaps doing something incorrect in my menus configuration array above?

[enminc]

I just noticed this

Note: in MODX 2.3, actions are no longer necessary (or possible to set up through the manager interface for that matter) and instead of creating the action, you pass your Menu to the right namespace and give it an action name, which is the name of your controller.

Could maybe have something to do with it.
http://rtfm.modx.com/revolution/2.x/developing-in-modx/advanced-development/custom-manager-pages

I am dealing with my own menu issues and don't know the actual answer to your issue but ran across this info and thought it might relate

[pixelchutes]

Exactly, I get the feeling it's a 2.3 issue related to the change you've highlighted above. I am not sure how the action assignment is currently handled, or if it can be backwards compatible to play nice with both 2.2 and 2.3.

[BobRay]

MyComponent is probably not completely 2.3 compliant (which figures, since 2.3 hasn't been released).

I think 2.3 will probably be backward compatible with respect to menus and actions (3.0 may not be).

I don't see how the namespace could be reset to core, since Bootstrap sets it to whatever is the config file, and ExportObjects sets it to the value for the actual object in the DB when creating the transport.menus.php file. I can't reproduce that problem in 2.2.14. Take a look at your transport.menus.php file and see what's there. It's very unlikely that MODX would change the value of that field when creating or saving the object.

With respect to the number you see for the controller, I see this sometimes too in 2.2.14. It's the ID of the action and works fine in 2.2.14.

BTW, you should be able to customize the transport.menus.php file and then remove 'menus' from the 'process' member of the config. (just to be sure, edit both config files). That way, your changes won't be overwritten when you run ExportObjects. I have not tested this, though.