I’ve been working with Drupal quite a bit lately, and am continually impressed by the powerhouse of tolls that it provides, either out of the box or with a selection of modules. However, I’ve also noticed that there are occasionally some “little things” missing in some of the most powerful plugins.
This morning I once again encountered the single shortcoming in the otherwise impressive “Backup and Migrate” module. I use this module so that I can dev on my local machine and push my changes out to my sandbox site for the client to approve easily and quickly. The tiniest improvement in this module would make it even that much simpler.
Here’s what happens. When I “Restore” from a Backup and Migrate backup, my temporary path is overwritten with the one in the backup. This makes sense of course, but means that before I can restore again, or do any uploads, I much manually reset the path. Bleh. It would be fantastic if before restoring, B&M module sequestered this piece of information from the existing DB, then placed it back after the update. I expect this would require the ability to save something in the filesystem (since the DB is being overwritten) or in an untouched table on the DB. Probably a simple workaround is possible…has anyone else solved this issue?
Update: The info is stored in the DB, table variable, key file_directory_temp. I think I’m going to try to write a routine that grabs this and saves it to session or something, then replaces it.