Closed barnabywalters closed 12 years ago
Do you have a pro account? I'm not seeing the url to the photo itself.
u'photo': None
Nope, no pro account. I didn't realise that was required (only reference to it I can find is a mention in the issues for export-flickr).
We're sourcing the original but we need to fall back to the highest resolution.I merged a pull request that does this. Do you mind rerunning the export and see if a URL is present?
Thanks, that's worked great (only errored on one (no idea why) and I didn't want that photo anyway). I had to manually set permissions=1 to make them public (thought it hadn't worked at first).
Now I have the slight problem that I cannot log in to openphoto (my password field has actually gone blank in the op_user table! It worked half an hour earlier)
I think you may have found a bug :) -- Investigating.
Looks to be that way :)
Is there an easy way to generate the value for the password field? Looking at the source shows it's sha('password' . 'salt') but I can't figure out what the salt is/where it comes from exactly.
The default value is in /src/configs/defaults.ini
I assume I should have changed it from "salt_for_passwords"?
Technically, yes :). But you can change it now, generate the password and store it and it'll validate accordingly. The password field is about a 2 day old feature.
Woo hoo! It works. Thanks a lot. Exemplary service :)
When trying to import 93 photos (JSON from flickr-export) I get
FAILED: 500 - An unknown error occurred.
for every single one.Sample output:
It's not a problem with the oauth tokens (I've tried with invalid tokens and get an error 403).
Running under debian (the same server the app is hosted on, if that makes any difference)