Andy Baker

Alternatively - maybe temp_upload_dir isn't intended to be 'temp' at all - in which case why not just use upload_to? Speaking of which - unless I've missed something 'upload_to' doesn't...

I've updated https://github.com/DjangoAdminHackers/django-filebrowser-browse-upload-field I went with a simpler solution of not using temp uploads at all. There are drawbacks to this (it will clutter up the upload_to dir with images...

> the temp upload dir is there, because upload_to doesn't need to exist when the file is being uploaded OK. My simpler solution works for my use case (I never...

> we used a signal for moving the file. I spent a while trying to decide where I would put this functionality. I think I settled on the pre_save method...

I'm trying to think of a generic solution. Aside from my other doubts about signals - this means that any model that uses FileBrowseUploadField has to write - or at...

contribute_to_class is looking pretty plausible. I should have something working tomorrow. Related question - should upload_to etc accept callables the same as FileField?

I've actually ended up using contribute_to_class to attach the signals automatically. There wasn't another way I could find to trigger this action after the model was saved (ModelFields only have...

Callables work. What doesn't work is the upload when you use inlines and the dynamic 'add another'. To fix this I'll need to move the javascript out of the field...

> Also adding *.meta to .gitignore would be appropriate, since Unity generates those for you. Nooooo! Meta files definitely need to be committed. Allowing Unity to regenerate them can end...

Can confirm this is what @PereUbu7 says it is. We're using lineOffset to draw rectangles in London and the descrepancy between north/south rectangles and east/west is pretty close to the...