/homebox-page/ is currently hard-coded (see for example homebox,module). It should instead be configurable on a global settings page or even be removed so that each homebox can get its individual path without limitations.
This Drupal 7 issue even suggestest do add token support: #1165106: Token support for path alias
Something similar flexible is requested here: #2165845: Homebox page path user/uid/title
Not yet sure if that's possible and makes sense, but we should think about the pros and cons.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | Screenshot_20220216_1041.png | 5.99 KB | avpaderno |
| #6 | Screenshot_20220216_1031.png | 68 bytes | avpaderno |
Comments
Comment #2
anybodyComment #3
anybody@Drumm and other maintainers, what do you think? In my opinion we shouldn't assume Homebox to be "below" the user profile. For example, we have a project where the homebox becomes the front page if the user is logged in. And I guess there are also other cases, for example admin dashboards, where it may be helpful to optionally add a tab to the user profile, but allow the user to choose the path without any prefix.
Of course, we'll have to check it doesn't collide with an existing path and path is clean, but that's also already solved in other modules,
Comment #4
anybodyComment #5
anybodyComment #6
avpadernoIf I create a Dashboard Homebox entity to which I assign the dashboard path, and I select the Visible menu item option, when I visit /homebox-page/dashboard/1, I see the following page content. (I didn't add yet blocks to the Homebox entity.)
It seems that all those tabs are for the Homebox entity, while View, Shortcuts, and Edit are tabs for the user profile.
Since the Homebox entities are per user, their parent route should be
/user/{user}.Comment #7
avpaderno(It seems the screenshot tool got the wrong browser page.)
Comment #8
avpaderno(I deleted the wrong screenshot. I apologize for the noise.)
Comment #9
anybodyThank you @apaderno, @Grevil and me discussed a new strategy for the page / route handling. We'll give some updates on this soon.
Comment #10
grevil commentedWe think the new homebox page options could look something like this: #3264690: Redesign the homebox page settings
Of course, the current custom path logic needs to get fixed first. :)
Comment #11
grevil commentedI will hijack this issue for implementing the logic behind the new homebox page settings.
See our progress here: #3264557: Plan for 2.0.0-alpha1 bugfix release
Comment #12
grevil commentedComment #13
grevil commentedAlright, the page routing is properly implemented in #3264557: Plan for 2.0.0-alpha1 bugfix release, the "path" option will be replaced with a "path-alias" option, more information about this can be seen here: #3264969: Create a path alias for the dashboard pages
Comment #14
grevil commented