Additions:
This issue is resolved in Aperture 2.1 and later, which is available from Software Update.
Deletions:
This issue is resolved in Aperture 2.1 and later.
Edited on 2008-03-28 14:28:10 by FraserSpeirs
Additions:
This issue is resolved in Aperture 2.1 and later.
Edited on 2008-03-04 14:45:58 by FraserSpeirs
Additions:
Aperture 2.0.0 and 2.0.1 shipped with a bug in the export plugin system which can cause FlickrExport to abort its export before any images are uploaded. A bug has been filed with Apple and a workaround was delivered in FlickrExport 1.0.8.
The problem is export file names. FlickrExport doesn't present controls to the user to set the file name on export, because the actual name of the file is irrelevant when uploading to Flickr. In Aperture 1.5, if an export was going to produce two files with the same name (for example, a Custom Name preset with no counter or index), Aperture would automatically append the file name with (1), (2), etc.. Aperture 2.0.0 does not do this and, instead, presents this error and aborts the export.
Aperture 2.0.1 will present one error dialog for every conflicting file. You should dismiss each of these.
- FlickrExport 1.0.7 for Aperture and earlier, running under Aperture 2.0.0 (3A86) and Aperture 2.0.1 (3B17).
Deletions:
Aperture 2.0.0 shipped with a bug in the export plugin system which can cause FlickrExport to abort its export before any images are uploaded. A bug has been filed with Apple and a workaround is being prepared. The problem is export file names. FlickrExport doesn't present controls to the user to set the file name on export, because the actual name of the file is irrelevant when uploading to Flickr. In Aperture 1.5, if an export was going to produce two files with the same name (for example, a Custom Name preset with no counter or index), Aperture would automatically append the file name with (1), (2), etc.. Aperture 2 does not do this and, instead, presents this error and aborts the export.
- FlickrExport 1.0.7 for Aperture and earlier, running under Aperture 2.0.0 (3A86)
Edited on 2008-02-25 22:28:39 by FraserSpeirs
Additions:
Edited on 2008-02-25 22:25:49 by FraserSpeirs
Additions:
Edited on 2008-02-25 22:18:25 by FraserSpeirs
Additions:
Symptoms
When exporting with FlickrExport, after clicking the Export button, Aperture will respond with a dialog box containing the following text:Error Writing Image to DiskAperture was not able to write image data to disk for “Foo.jpg”. A file of the same name may already exist in the target directory (/Users/fspeirs/Library/Application Support/FlickrExport/ResizeCache/Foo.jpg), or you may not have permission to write files to this location, or there may be insufficient disk space.
The export will be cancelled.
Cause
The problem is export file names. FlickrExport doesn't present controls to the user to set the file name on export, because the actual name of the file is irrelevant when uploading to Flickr. In Aperture 1.5, if an export was going to produce two files with the same name (for example, a Custom Name preset with no counter or index), Aperture would automatically append the file name with (1), (2), etc.. Aperture 2 does not do this and, instead, presents this error and aborts the export.Resolution
Starting with version 1.0.8 of FlickrExport for Aperture, if you hold down the Command key∞ while choosing FlickrExport from the Export submenu, FlickrExport will present the file naming controls. Use these controls to choose a file naming preset that contains a counter, index or is otherwise guaranteed to produce unique file names.Products Affected
- FlickrExport 1.0.7 for Aperture and earlier, running under Aperture 2.0.0 (3A86)
Edited on 2008-02-25 21:08:53 by FraserSpeirs
Additions:
Categories
Deletions:
CategoryFEAperture
Oldest known version of this page was edited on 2008-02-25 21:07:24 by FraserSpeirs []
Page view:
Aperture 2 File Name Conflicts
Aperture 2.0.0 shipped with a bug in the export plugin system which can cause FlickrExport to abort its export before any images are uploaded. A bug has been filed with Apple and a workaround is being prepared.
CategoryFEAperture
CategoryAperture
CategoryAperture2