ikenndac / 500px-aperture-uploader Goto Github PK

Hard-coded strings are bad! Move them out to a .strings file.

An option to have the plugin automatically take you to your uploaded photos in your browser.

Fresh install of v0.5 (tried installing from the github project first, but it wouldn't let me log in). I tried uploading a photo, it went successfully according to the logs but the photo doesn't appear on my portfolio.

I know there's some processing done by 500px before the photo is available, but it's been 90mn and the photo is still not there. It was uploaded as a private photo.

The plugin doesn't clean up the logs folder, so the logs folder can balloon over time.

Since the plugin seems to have gained a lot of traction, it should automatically check for updates.

Errors are either ignored or shown in a bad way.

I always get "Your username or password was entered incorrectly." I have a correct login and password.

Console log shows that the response to your curl auth request is a "Server Error" page.

Additional functionality: The ability to add photos directly to an existing Set, or to create a new Set.

When creating a new Set, the option to mark as private, set a password and customise the URL should be possible.

Photos added to Sets should be markable as Private (i.e. not appear on Public Profile).

Installation fails under Mountain Lion with the following error message

The installation failed with the following error: Error Domain=NSCocoaErrorDomain Code=513 "“500px Aperture Uploader.ApertureExport” couldn’t be copied because you don’t have permission to access “Export”." UserInfo=0x7fe453892e40 {NSSourceFilePathErrorKey=/Users/User/Desktop/Install 500px Aperture Uploader.app/Contents/Resources/500px Aperture Uploader.ApertureExport, NSUserStringVariant=(
Copy
), NSDestinationFilePath=/Users/User/Library/Application Support/Aperture/Plug-Ins/Export/500px Aperture Uploader.ApertureExport, NSFilePath=/Users/User/Desktop/Install 500px Aperture Uploader.app/Contents/Resources/500px Aperture Uploader.ApertureExport, NSUnderlyingError=0x7fe4538935f0 "The operation couldn’t be completed. Permission denied"}

A temporary fix is to navigate to Users/User/Library/Application Support/Aperture/ and ensure user level permissions are set for the "Plug-ins" and "Export" folders.

Running the installer again afterwards works perfectly.

Aperture 3.4 is sandboxed, which causes problems.

An optional detailed export log would be nice, which would be opened either automatically or when the "Done!" Growl notification will be shown.

The log would be a HTML file that contained detailed status about each uploaded photo, including a link to the photo on 500px if the upload was successful or a detailed error description if it wasn't.

Too many people are confused by Aperture's bad error when loading the plugin on a 32-bit system.

A good solution would be to have a separate 32-bit plugin that puts up an alert with instructions on what to do, then lipo it with the 64-bit one at build-time.

…also, EMKeychainItem triggers static analysis warnings.

Use this! https://github.com/ObjColumnist/MCSMKeychainItem

It would be great if tags could be set directly from the plug-in. And even better if they would be initialized with the Aperture tags assigned :-)

Using last 500px-Aperture-Iploader version (0.4) When Aperture finishes uploading tu 500px.com his photos, I suddenly have a crash with notification about a Growl error encountered. I use the "let an alert appear when a cliché is uploaded" feature.

HTML-encode special characters, or declare UTF-8 properly. Probably both.

Attempt to install returns the following error: "Install 500px Aperture Uploader? can't be opended bacuase it is from an unidentified developer.

The plugin should have a nice icon!

Hallo,
I just like to confirm, that the following error described in an already closed issue happens to me frequently :
"When Aperture finishes uploading tuo500px.com his photos, I suddenly have a crash with notification about a Growl error encountered"

I can add to this problem, that it does not happen while the first upload and growl notification. It happens when you upload a second picture, right after the growl notification.

Regards
Martin

People keep asking on Twitter about a "problem" with the plugin which turns out to just be 500px being slow. Make the fact there might be a delay more obvious.

Manually putting the plugin in a hidden folder sucks. Make an installer!

Credit to @benjjamieson for the idea.

Thank contributors, donors, credit third-party libraries etc.

Images need to be at least 3,600px wide to be sold on the store.

Growl notifications during and after export would be pretty nice.