15560
Reporter: omeyn
Assignee: bko
Type: Task
Summary: Drupal menu import should include non drupal urls
Priority: Major
Resolution: Done
Status: Closed
Created: 2014-04-28 11:20:34.37
Updated: 2014-05-14 15:20:12.177
Resolved: 2014-05-11 19:34:35.219
Description: We have made Drupal by-pass menu links validation that don't have a "node in Drupal but indeed links pointing to GBIF web layer. This has been working so far but we need that to be exportable/importable so the menu structure will be something deployable in the future.
Done when links like:
1) participant/list on java web;
2) newsroom/summary#signup (links with anchor)
are exportable/importable.
]]>
Author: bko@gbif.org
Created: 2014-05-07 11:52:25.482
Updated: 2014-05-07 11:52:25.482
As of r2847 the menu import works for these 2 types of special menu links, only when enabled via Web UI. If gbif_navigation module is enabled together with gbif_tweaks via Drush en the result will be incomplete.
For now the new theme enabling sequence is:
$ drush en gbif_pages
$ druch vr
$ drush en gbif_tweaks
And go to admin/module and enable the gbif_navigation module.
This issue will be kept open until I can debug Drush and sort out the difference.
Author: bko@gbif.org
Created: 2014-05-11 19:34:18.833
Updated: 2014-05-11 19:34:18.833
The difference of menu importing between Drush and UI turns out to be that Drush doesn't have $_SERVER['Document_Root'] variable which is used in our environment settings for including settings files. These settings affect correct analysis of non-Drupal and external URLs.
Reorganising the settings file solves the issue. This will require updates to the deployment script.