$builder->buildLexicon($sources['lexicon']);
$builder->pack();
$menu->addOne($action);
$action->addMany($menu,’Menus’);
I have other differences in my build script as well, I attach the action to the menu and create a menu vehicle, you seem to reverse this and create an action,
not sure if this is your prob though. I’ve attached my build script for the Provisioner component for your perusal, hope it helps.
I have other differences in my build script as well, I attach the action to the menu and create a menu vehicle, you seem to reverse this and create an action,
not sure if this is your prob though. I’ve attached my build script for the Provisioner component for your perusal, hope it helps.
$menu->fromArray($array,'',true,true);
$menu->fromArray($array);
MODX Staff
Because when dynamically creating new xPDOObject instances you need to set the primary keys, which xPDOObject::fromArray() will not do unless explicitly told to do so with the third parameter.
Okay I guess my way (or the manual’s way) is the other way around, but I suppose both ways work. I now do it your way because I like it more. Unfortunately it doesn’t solve the problem. I guess the main problem is, that as primary key an empty string for whatever reason is inserted into the table.
Why do we needWhy isn’t a$menu->fromArray($array,'',true,true);sufficient?$menu->fromArray($array);
This tells the install process to use the primary keys of the stored object explicitly; if false, those objects would get newly generated primary keys when inserted instead of the original keys being preserved.
Why do you set xPDOTransport::PRESERVE_KEYS to true?
<?php $_lang['gallerygear'] = 'GalleryGear'; $_lang['gallerygear_desc'] = 'Manage my GalleryGear pictures.';
<?php $_lang['gallerygear'] = 'GalleryGear'; $_lang['gallerygear_desc'] = 'Verwalte meine GalleryGear Bilder.';