Add a Footer menu to the built-in system menus

Still a valid issue in Drupal 7.4. I'm not sure if this goes under string freeze or not, so not adding backport to D7 tag.

This patch adds a new menu called "Footer Menu" and puts it in Bartik's footer region. I wasnt sure what default link(s) to put in there, so for now I just put a "home" link, but that is something to discuss. Also, I tweaked a function in Bartik's template.php to hide titles from blocks in the footer region like we do already in the header region. I think that the same assumption is valid.

#594660: Rename default menu names just landed.

We want to rename the internal menu name to just 'footer'.

There's a follow-up patch required in aforementioned issue though, which will prefix the system block identifiers with 'menu-'.

Re-rolled against HEAD and simplified interface texts.

Applying patch throws up the below error

error: patch failed: core/includes/menu.inc:1755
error: core/includes/menu.inc: patch does not apply
error: patch failed: core/modules/menu/menu.install:51
error: core/modules/menu/menu.install: patch does not apply

#4: drupal8.footer-menu.4.patch queued for re-testing.

@Shyamala: That's odd, sent the patch for re-testing, to prove what you're saying. In any case, please also double-check yourself that your local 8.x checkout is up to date.

The patch applys. No error occurs, code updates well.

• Applied patch and cleared cache, but the Footer menu did not apply.
• Checked in admin/structure/menu, menu not listed.
• Check in Bartik setting page, there is no option for Footer menu.

Is there anything else I need to do?

@Shyamala, have you run all database updates? A particularly interesting one is from this commit: http://drupalcode.org/project/drupal.git/commit/3666987

So I thought about what would be a good use-case for a footer menu link in core, and came up with:

"Contact" :)

Attached patch adjusts Contact module accordingly, enables Contact module for the Standard installation profile, and also adds a database update for Menu module to inject the new menu into custom menus on existing sites (which is required to make it editable in the UI like all other menus).

That said,

+++ b/core/modules/contact/contact.module
@@ -90,7 +90,7 @@ function contact_menu() {
     'type' => MENU_SUGGESTED_ITEM,

Contact module exposes the "Contact" menu link as a suggested item only. This means that the link is initially disabled.

We could change this item into a normal item, but that would get us into quite some scope-creep.

Instead, we adjust the Standard profile to enable it during installation.

Incorporated the suggestion from #12; i.e., Standard profile enables the Contact link in the Footer menu.

Apparently, the menu system does not provide a facility to do that yet, so I quickly had to invent one.

Small adjustment to the menu update.

+++ b/core/includes/menu.incundefined
@@ -3345,15 +3346,32 @@ function menu_link_maintain($module, $op, $link_path, $link_title) {
+      $result = db_query("SELECT * FROM {menu_links} WHERE link_path = :link_path AND module = :module AND customized = 0", array(':link_path' => $link_path, ':module' => $module))->fetchAll(PDO::FETCH_ASSOC);

why doesn't this use the DBTNG syntax? ... I'm sure there is some coding standard that I'm just not familiar with, but I thought I'd ask just in case

Otherwise I love this patch ... applied cleanly and after a fresh install I had a contact link in my shiny new footer menu. RTBC from me

The code is running a targeted query against the menu link table, which does not need the db_select() syntax. Also, the added query is using exactly the same approach as the existing $op 'update'. If that was bogus, then it would have to be changed in a separate issue anyway. :)

So I'm counting one RTBC here. Any further? :) Perhaps even an issue status change? ;)

Just installed using drush si and footer menu was there at the footer, but contact link was disabled.

I guess that's "Needs Work"

@barraponto: I'm relatively confident that Drush is not up to speed with regard to D8 at this point. At least, it does not work (more or less at all) for me.

Also, your review directly contradicts #15, which says that the link appeared just fine after performing a manual installation using Standard profile. Can you double-check? :)

Ok, I applied the patch from #14 (still applies cleanly) and manually installed using standard profile.
Still shows footer menu in the footer region, leaves contact link disabled :/

FWIW, I'm running PHP 5.4.8, MySQL 5.5.28 and Lighttpd 1.4.31. I'm using php-fpm (shouldn't matter).

Hmmm, is menu.inc loaded by the time standard_install runs?

Alright, sorry, confirmed your manual testing results, and fixed them:

1. Fixed Simpletest does not support tests for installation profiles.
2. Added Standard installation profile test.
3. Fixed missing user access to contact form after installation.
4. Fixed menu link has to be marked as customized after toggling hidden.
5. Removed entirely needless menu_router_rebuild() from standard.install.

Now the expectation is covered by automated tests. This is the first test for an installation profile in core, since testing of installation profiles was not possible before.

Alrighty:

Standard installation profile   7 passes, 0 fails, and 0 exceptions

Are we done? :)

Confirm menu contact link is there after installation, even for anonymous users. Are we sure we want to leave this open by default, for possible abuse by spammer bots?

btw, I didn't read the installation profile test stuff (don't know simpletest). leaving it "needs review" for someone else to read it. but good work sun :)

Voila! It's works awesome.

1. Downloaded the latest version of Drupal 8
2. Applied the patch
3. Installed using Standard Profile

The contact link on the footer showed up!

This sounds like a good idea, but it's a new feature, and thus subject to thresholds, which we are over atm. :(

Why all the changes to menu_link_maintain() and not just menu_link_save() in the install profile?

Contact module registers a "Contact" link already, which we are putting in the footer menu by default.

That's a suggested item though and thus not enabled by default. We do not want to create a duplicate Contact link in that menu.

In order to not create/save a duplicate menu link, the existing menu link needs to be known and loaded, and it must be passed along to menu_link_save(), so that the existing mlid and plid is known and the existing link can be updated. The menu [link] system does not provide API functions for that.

However, the menu link system provides an API function that generally has the exact purpose of allowing code (not humans) to maintain a menu link: menu_link_maintain()

The important detail about it is that it only touches a menu link if it hasn't been customized. So this is exactly the API function that is needed, but it didn't support enable/disable operations yet. This patch here adds that tweak, so Standard profile can enable the default "Contact" link in a one-liner.

#21: platform.footer.21.patch queued for re-testing.

Merged HEAD.

#30: platform.footer.30.patch queued for re-testing.

I don't really like suggested items or menu_link_maintain() very much, but this patch isn't responsible for either of those so it's not really fair to hold it up on it.

I do think a new menu makes some sense and contact is a good use-case for it. I could see legal module adding a link there by default too.

Committed/pushed to 8.x. Could use a change notice.

Thank you! :)

Change notice: http://drupal.org/node/1845756

Follow-up: Contact module still has some help text referring to the Contact-link being in the Tools-menu: #1873416: Contact module help text incorrect.