Hi,

mlid is stored in menu_minipanels options in menu_links table.

  else {
    // Store mlid for later use in uniquely identifiying menu configs in the
    // Javascript.
    $form_state['values']['options']['menu_minipanels_hover']['mlid'] = $form_state['values']['mlid'];
  }

First, this is duplicating data, as mlid has its own column in menu_links table.
Secondly, when using Features to export menu_links, we don't want to export any incremental numeric id, as we cannot assure the same id will be assigned next time we install the feature.
Thus, mlid should not appear in options column of menu_links table.

I suggest that, instead of saving it in the menu_link form, this mlid should be inserted in the options array where it's necessary only.

Regards,

David

Comments

damienmckenna’s picture

Assigned: Unassigned » damienmckenna

I'm definitely going to look into this.

damienmckenna’s picture

Status: Active » Postponed

I'm not sure how this can be done right now, but if anyone has any solid ideas please let me know. There isn't any way to remove the mlid from the data structure from before it exports, the data structure doesn't show the mlid from within hook_menu_link_alter(), so right now I think we're stuck with an unfortunate problem :-(

damienmckenna’s picture

Assigned: damienmckenna » Unassigned

Taking this off my todo list for now.