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...

CommentFileSizeAuthor
#2 hosting-2151371-2.patch1.04 KBhelmo
#1 hostion-2151371-1.patch927 byteshelmo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

helmo’s picture

Status: Active » Needs review
FileSize
927 bytes
helmo’s picture

FileSize
1.04 KB

needed one more condition to actually hide the unlock task on enabled platforms

ergonlogic’s picture

Looks reasonable, but I wonder if this logic belongs here at all. Shouldn't this be controlled by an access callback in hosting_platform?

helmo’s picture

Then 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.

helmo’s picture

Status: Needs review » Fixed

committed 788c41b8123ab3b5cc6df44c375a528a5a3c01aa

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

  • Commit 788c41b on 6.x-2.x, 7.x-3.x, dev-sni, dev-helmo-3.x by helmo:
    Issue #2151371 by helmo: Allow custom platform tasks.
    

  • Commit 788c41b on 6.x-2.x, 7.x-3.x, dev-sni, dev-helmo-3.x by helmo:
    Issue #2151371 by helmo: Allow custom platform tasks.