Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
At the moment we have only one route that is not related to dashboard in UI module. Move that to crm_core so we can rename ui module to crm_core_dashboard
Proposed resolution
Move crm_core.manage route and it's menu link from crm_core_ui to crm_core.
Comment | File | Size | Author |
---|---|---|---|
#18 | move_non_dashboard-2703637-18.patch | 7.06 KB | thenchev |
#18 | interdiff-2703637-18.txt | 445 bytes | thenchev |
#15 | move_non_dashboard-2703637-15.patch | 7.07 KB | thenchev |
#15 | interdiff-2703637-15.txt | 2.29 KB | thenchev |
#13 | move_non_dashboard-2703637-13.patch | 5.04 KB | thenchev |
Comments
Comment #2
thenchev CreditAttribution: thenchev at MD Systems GmbH commentedComment #3
thenchev CreditAttribution: thenchev at MD Systems GmbH commentedMoved the route and menu link.
Comment #4
CTaPByK CreditAttribution: CTaPByK at MD Systems GmbH commentedLooks ok. RTBC.
Comment #5
BerdirNot quite.
If the goal is to make crm_core_ui an optional dashboard module, then we need to ensure that that's actually the case with this issue (it becoming optional)
For that, we should update our dependencies to no longer depend on it and also no longer enable it in test.
I'm expecting at least some test fails because we don't take over the /crm-core route. If nothing else, then I'm expecting some breadcrumb test fails. Actually more than that, crm_core_contact and activity will both fail hard without that route.
This might have to wait until we know what we will happen with #2703641: Port crm_core_ui_dashboard() (not actually implemented, just defined).
Comment #6
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedI discussed this with @berdir a bit. Let's also move "crm_core.dashboard" route too. This will prevent major problems, but we will need to create custom access check for it. We will do that in the follow-up.
Comment #7
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedAlso, rename the route as it is not dashboard any more. "crm_core.overview" or something along those lines.
Comment #8
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedFollow-up: #2704095: Create custom access check for /crm-core
Comment #9
thenchev CreditAttribution: thenchev at MD Systems GmbH commentedMoved crm_core.dashboard and renamed it. Removed all dependencies i could find.
Comment #11
thenchev CreditAttribution: thenchev at MD Systems GmbH commentedThis should fix the test fails. Created permissions.yml in crm core for the overview route. I guess we can later change that in the followup...
Comment #12
mbovan CreditAttribution: mbovan at MD Systems GmbH commentedLooks good.
One dot extra at the end. I see it was the same before though...
I guess we already have some tests for those menu links/routes?
Comment #13
thenchev CreditAttribution: thenchev at MD Systems GmbH commentedNeutralized the dot and also a comma.
Comment #14
BerdirTest is a good point, I can't see any tests that directly access /crm-core.
Lets add that to some existing contact tests and then click on the menu link that should be there instead of going to crm-core/contacts directly. We will also need to give the user we do it with the new permission.
Comment #15
thenchev CreditAttribution: thenchev at MD Systems GmbH commentedExpanded test coverage, fixed menu links for contact and activity.
Comment #16
BerdirThanks, good thing I requested test coverage then ;)
Not sure if the links really need to contain CRM there, seems repetitive. But that's a different issue and not very important.
Comment #17
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedBefore we removed this this implicitly added dependency to crm_core. That is not the case any more. It seems that all submodules need to explicitly depend on crm_core.
Comment #18
thenchev CreditAttribution: thenchev at MD Systems GmbH commentedUpdated dependency for crm_core_contact since it seems that all the other submodules are directly or indirectly dependent on crm_core
Comment #19
CTaPByK CreditAttribution: CTaPByK at MD Systems GmbH commentedDependency is added so i think we can back status to RTBC.
Comment #21
slashrsm CreditAttribution: slashrsm at MD Systems GmbH commentedCommitted. Thanks!