>From my own experience it could also be that something is wrong with the >dialog configuration. For example, if there is no tab with controlType=tab on >the first level, it will throw the exact same error message as if there was no >dialog at all. Here's a few things to ensure that a dialog (should) be working: * No space at the beginning or end of name - often from copy-paste errors * If it is i18nized and using messages, make sure the messages.properties can be resolved and the i18nBasename is correct. If this is not the case, you will not get a 500 error, but your dialog will open and close again immediately. * The first tab (content node) has to have a property controlType=tab * Avoid name-clashes with pre 2.0 STK dialogs(/components/templates). No matter where the dialog is in a hierarchy, the name has to be unique. If you modify stkHomeProperties for your own project and still keep the original stkHomeProperties, you will have to rename your copy to myProjHomeProperties. With STK 2.0 this would not be necessary any more since the id of dialogs are defined by their module name already - however, as a best practise when developping several projects I would still put some kind of project identifier in the names. * Typos and missing letters! Writing something like "controlTyp" will indeed not help you either :D
HTH -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=b9b19fd2-37a0-49af-b830-ebc67dd7312a ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
