edoburu / django-any-imagefield Goto Github PK

Hi everyone. Basically I get this error in admin:

TypeError at /admin/work/poster/add/
render() got an unexpected keyword argument 'renderer'

However, if I comment field in the model, everything works fine. The image field is not shown of course.

Any ideas?

Hi,

I" migrating an application from django 1.11 to 2.1+, this application uses AnyImageFied for pictures management,

I've noticed an incompatibility in wigdets; for now, an addional parameter is required for Widget.render() method: renderer

I'll propose a PR for this...

Thanks !

Hi. So the issue is this. The code:

class Images(models.Model):
    top_image = AnyImageField('Image', upload_to='top_images')

In Admin site I expect it to show "Top image" as the label for the field, on the left side. Instead I see just "Image".

Is it a bug or am I missing something?

Thanks ahead.

My Python3.4 Django1.8.5

When click this url
http://127.0.0.1:8000/admin/news/post/add/

Alert Error
python3.4/site-packages/any_imagefield/forms/widgets.py in render, line 19

model.py (error)
news_images = AnyImageField(upload_to='news_images/', default='news_images/None/no-img.jpg')

model.py (not error)
news_images = ImageField(upload_to='news_images/', default='news_images/None/no-img.jpg')

Is there any work-around to get image dimensions automatically into the model like stock Django does with the width_field= and height_field= options?

I'd like to create a new file/image library app that does more than just provide a browser and enhanced admin form widgets for file/image selection and upload.

I'd like the library to store additional metadata like alt text, cache file size (useful when using S3 storage backend and querying file size on a list of files is slow) and type, etc.

I'd like to either contribute, an integration class to django-any-imagefield or for django-any-imagefield to have some better hooks that would allow me to use a private integration class (e.g. import the backend class from a setting).

My image/file library would use a storage name field as its primary key, and provide a descriptor on the resulting FieldFile object that is returned when you access foo.my_file_field, that would lookup the corresponding metadata from the library via foo.my_file_field.name.

I just wanted to check in with you if this sounds feasible and worthwhile, and if you could point out any likely pitfalls I might encounter?