I've been playing around a bit with Dashboard and I like it but I'd like it to be a tab on the user page. That is, example.com/user/#/dashboard. I could probably move it over there with menu_alter but I don't want to get into trouble down the road. I saw an issue where there was talk of having multiple dashboards and such and that could involve more paths... Is there a "future proof" way to move it over there?



#2 user-page-tabs.png26.08 KBMichelle
Members fund testing for the Drupal project. Drupal Association Learn more


techsoldaten’s picture

@Michelle - in terms of the future, we are going to have multi-dashboard support in the next release. This will let users click on a link to 'add a tab,' which will create a new dashboard for them to place widgets. The code for it is all there, I just need to reimplement it.

In terms of displaying this on the user page - one thing I have not put too much effort into is effective use of tabs in the module. Right now, it is really geared to work on the redesign staging sites, which has some tab support built in at the theme level. I will dig in on this question more tomorrow, but - is there a way you would like to see them work? Would love some feedback at this point.


Michelle’s picture

26.08 KB

I like to centralize all the stuff that's for my user on one "page". It's not literally the same page as we're talking about local task menu tabs, not js tabs, but it gives the appearance of all being in the same place. Unfortunately, there are several modules that put their user facing stuff off on its own. Privatemsg is one I can think of offhand and, obviously, Dashboard is another.

This is what my user page looks like:

So I'd like to add to that a "homepage" or "dashboard" (not sure which name my users would understand more, yet) that takes them to their dashboard(s). By centralizing modules like this on the user/#/* path, the tabs create a sort of user control panel where they can get to their profile, messages, bookmarks, etc all in one spot.

It would be awesome if the module would put it there by default but, if that's not possible, a way to move them there on a site by site basis would be very helpful.



rbosscher’s picture