search

jonasundderwolf / django-image-cropping

Django helper application to easily and non-destructively crop arbitrarily large images in admin and frontend.
Other
553 stars 131 forks source link

Separated crop widget / image #34

Closed lucaslober closed 10 years ago

lucaslober commented 10 years ago

After following the tutorial steps I found this.

First, in the installing tutorial both images and cropping are in the same admin field. In my case, for cropping an image i have to upload it, save it, reopen the page and crop it, and save it again. I would like to upload the image, crop and save.

Looks like the app do this in the example, crop and image are together.

I attach two images:

1) The functionality I expect image-cropper-expect

2) This is what I have (separated crop widget)

separated fields

Hope this helps

Django==1.5.1 PIL==1.1.7 South==0.8.1 argparse==1.2.1 distribute==0.6.27 django-geoposition==0.1.4 django-image-cropping==0.6.4 django-localflavor==1.0 django-modeltranslation==0.6.1 django-registration==1.0 django-social-auth==0.7.23 django-suit==0.2.1 easy-thumbnails==1.2 httplib2==0.8 ipython==0.13.2 oauth2==1.5.211 psycopg2==2.5 python-memcached==1.53 python-openid==2.2.5 wsgiref==0.1.2

anrie commented 10 years ago

Could be related to your admin skin (django-suit).

Does it work if you use Django's default admin or do you see the same behaviour?

lucaslober commented 10 years ago

Yes, it was django-suit. It's not compatible with django-image-cropping. Thanks. Same happends with #35.

Have you tested django-image-cropping with any django skin? I don't like defaults admin skin.

Thanks

lucaslober commented 10 years ago

on grappelli skin #35 works fine but #34 don't. Admin fields still separated.

anrie commented 10 years ago

This is probably caused by some assumptions concerning the page structure in image_cropping.js and it would surely be nice if we could handle this a bit more abstract so we don't rely on a specific admin skin.

However we are neither using django-suit nor grapelli ourselves at the moment, so this issue is not at the top of our list.

But a patch that addresses this issue would definitely be a welcome addition!