Posted by mailleux on March 13, 2011 at 9:30pm
2 followers
| Project: | Project |
| Version: | 6.x-1.x-dev |
| Component: | Releases |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | needs review |
| Issue tags: | 6.x-1.0 blocker |
Issue Summary
I use 5.x-1.3 and spent a couple of hours trying to figure out why the migration was loosing all the release information. I use postgres 8.3, but I believe that is not the problem.
While looking at step 6002, I fount line 427 suspicious:
if (file_exists($file->file_path)) {This does not check for the existence of files in the place where releases are placed. As a result no file is migrated. I tried changing it to (project_release.install line 427):
if (file_exists(file_create_path($file->file_path))) {This way all my file definition moved. I assume this will affect other user that use the release mechanism.
Comments
#1
+
#2
Patch attached. Data loss is self-speaking critical.