Posted by davipilot on August 17, 2012 at 3:17am
4 followers
Jump to:
| Project: | Backup and Migrate |
| Version: | 7.x-2.4 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
I received the following warning during an upgrade from D6 to D7 test on my localhost. So far it doesn't seem to be causing any issue, but I have no clue what the warning is telling me in order to think out any implications it may have downline.
Warning: rename() [function.rename]: Cannot rename a file across wrapper types in backup_migrate_update_7200() (line 380 of ...\sites\all\modules\backup_migrate\backup_migrate.install).
Anyone else run into this and have any problems?
Comments
#1
I have this same issue as well/
Notice: rename() [function.rename]: Unable to find the wrapper "private" - did you forget to enable it when you configured PHP? in backup_migrate_update_7200() (line 380 of /home/timemast/public_html/drupal7/sites/all/modules/backup_migrate/backup_migrate.install).
If anyone knows how to resolve this please help
#2
I think this is because you need to have a Private files directory setup. If you go to Configuration -> Media -> File system and set a directory path for private files, this might solve this issue.
#3
Yes this is because in D7 the b&m files are stored in the private file directory, but if you're doing an update from drupal 6 that directory won't exist yet. It's a bit of a chicken and an egg situation as there really isn't a mechanism for B&M's update script to wait until after that setup has been done before transferring the files. The good news is you can always just move the files by hand from your public files directory to your private directory after the update or even leave them where they are if you don't care about them going forward (though for best security practice you should remove them if you don't need them).
Any ideas as to how I can do this upgrade more smoothly would be appreciated.
#4
You could probably use Drush to set the private file directory before your run the B&M update script:
drush vset --always-set file_private_path 'sites/default/files/sitename/private'Or write another script that does both the drush command above and also copy the files.