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.
The current implementation of hosting_task_menu_access() limits the tasks that can be run on a platform to 'verify', 'unlock', 'delete', 'migrate'.
This makes it impossible to easily create a custom task for platforms. A custom access callback is required.
We don't place this limitation on sites and servers...
Comment | File | Size | Author |
---|---|---|---|
#2 | hosting-2151371-2.patch | 1.04 KB | helmo |
#1 | hostion-2151371-1.patch | 927 bytes | helmo |
Comments
Comment #1
helmo CreditAttribution: helmo commentedComment #2
helmo CreditAttribution: helmo commentedneeded one more condition to actually hide the unlock task on enabled platforms
Comment #3
ergonlogicLooks reasonable, but I wonder if this logic belongs here at all. Shouldn't this be controlled by an access callback in hosting_platform?
Comment #4
helmo CreditAttribution: helmo commentedThen it would have to be split in three parts {site, platform and server) and moved there. I think that would be something for 3.x.
I'll try to commit later today.
Comment #5
helmo CreditAttribution: helmo commentedcommitted 788c41b8123ab3b5cc6df44c375a528a5a3c01aa