Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I think the reason it wasn't implemented was that the bulk operations that have been implemented are somewhat simple and don't require any feedback from the user, whereas a backup requires the user to chose the name of the backup.
Not impossible, probably not even all that hard, just haven't got to it yet.
VBO is the major part that I didn't put an excessive amount of effort into so far, it still needs some superficial love.
Actually, as it turns out, backups get automatically named if no custom name is provided, so this should be relatively simple. I'd still like to add the ability to provide a name on a site-by-site basis at some stage, but that can be a follow-up issue.
Comments
Comment #1
anarcat commentedno
Comment #2
ergonlogicComment #3
decipheredI think the reason it wasn't implemented was that the bulk operations that have been implemented are somewhat simple and don't require any feedback from the user, whereas a backup requires the user to chose the name of the backup.
Not impossible, probably not even all that hard, just haven't got to it yet.
VBO is the major part that I didn't put an excessive amount of effort into so far, it still needs some superficial love.
Comment #4
anarcat commentedCouldn't we have a default name for backups?
Comment #5
decipheredActually, as it turns out, backups get automatically named if no custom name is provided, so this should be relatively simple. I'd still like to add the ability to provide a name on a site-by-site basis at some stage, but that can be a follow-up issue.
Comment #6
decipheredSuper simple.
Repo: http://drupalcode.org/sandbox/deciphered/2001932.git/shortlog/refs/heads...
Patch: http://drupalcode.org/sandbox/deciphered/2001932.git/patch/63e8d562f75d0...
Comment #7
ergonlogicFixed in 83e5d2b.