Handle menu hierarchy
2440media2 - October 9, 2009 - 14:28
| Project: | Node Export |
| Version: | 6.x-2.18 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
First off, this is a great module, nice work.
Looking at the export file the plid is exported correctly, but mlid is always 0 for every node, so upon import, the hierarchy isn't built correctly and in my case some of the pages were becoming children to admin_menu links because the plid matched a previously existing mlid.
I know that there is an option to wipe out the imported menu links, but when importing about 200 pages nested about 4 levels deep, trying to rebuild the hierarchy by hand can be quite time consuming. So hopefully there is a fix to maintaining the hierarchy upon import.
Thanks.
#1
I am not aware of a solution to this. This module isn't designed to export a whole site structure - the bulk functionality is kind of an afterthought and a lot of things like book and menu structures, and reference fields, do not get imported properly on the new site.
If you have a good understanding of drupal's api, database, menus, etc.. you might be able to think of a way around this, if so... let me know how :P Imagine if you forget to export one node in a hierarchy - what happens to the hierarchy? It seems like you would need a totally different approach to the whole export - you might write a module to export the menu structure, which would use node export to attach the nodes into it's own export. Or perhaps an option to node export to 'also export dependencies' or soemthing like that and it would add in any nodes you forgot.
#2
This is closely related to http://drupal.org/node/601458 and a suitable strategy to solve one issue may prove effective for the other.