Seeing this.

Notice: Undefined index: reusestyle in manualcrop_preprocess_image() (line 717 of /docroot/sites/all/modules/manualcrop/manualcrop.module).

This is fixed by doing this… (I THINK)

        // Use the reuse style to load the crop selection.
        if (_manualcrop_is_own_effect($styles[$style_name], FALSE)) {
            if(isset($styles[$style_name]['data']['reusestyle'])) {
                $style_name = $styles[$style_name]['data']['reusestyle'];
            }
        }

Comments

matthijs’s picture

matthijs
Primary language Dutch
commented
Assigned: Unassigned » matthijs
Status: Active » Fixed

Weird that you have an empty "reusestyle" key (please verify your image style settings), but I added the check anyway... Thanks for reporting!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

wildweaselmi’s picture

wildweaselmi commented

Just wanted to let you know, I just did a fresh install of Open Atrium 2 and I had the same error. Performing the suggested solution worked for me. Thank You acb for posting this.

electrokate’s picture

electrokate commented

This also worked for me. Thanks!

Anonymous’s picture

Anonymous (not verified) commented

Just came up against this same issue in my website. Any workaround besides editing the code ? Has anyone figured out why this is happening ? If I change image styles will it resolve this or is this just a straight up bug.

Anonymous’s picture

Anonymous (not verified) commented

I tried the code it didn't fix it for me. Do I need to replace any line or delete any lines for this snippet to work ?

Anonymous’s picture

Anonymous (not verified) commented

I think I figured out the issue. When I tried the code it did not solve the issue for me. I reverted my code to the original way and then started to configure the image styles with different (non panopoly styles) it solved the issue. It seems to be something with the panopoly image styles in custom content types.

Anonymous’s picture

Anonymous (not verified) commented

I actually found more out about the issue. It seem like the content page still has this issue. Once I changed the image style on my custom content types it resolved the issue for them. This bug still happens even with different image styles in the content page. Possibly a panels specific bug. If I find more I will let everyone know what I find.

Looks like the best workaround is create a custom content type and choose a image style other than panels styles. Large or medium etc. It fixes this issue without code modifications. The content page seems to have this issue so I suggest not using it. Create a new main content type and the workaround works fine.

Anonymous’s picture

Anonymous (not verified) commented

Upon further investigation I found this issue directly relates to the WYSIWYG. Using the editor causes this issue even in custom content types with selected image styles other than panopoly styles. It looks like this is related to updating media / WYSIWYG issue that I recently experienced as well.

The update causes the WYSIWYG for panopoly to get removed for some reason. This is what causes this issue. The 2 issues should be linked somehow. I have managed to reproduce this error many times now so it can be replicated. If someone experiences the media update with WYSIWYG removal issue they will after be able to reproduce this error.

delacosta456’s picture

delacosta456 commented

hi
Yes i confirm it is media update with WYSIWYG error cause on my own side i always proceed mode update 1 by 1 so after update that module the error started showing

Anonymous’s picture

Anonymous (not verified) commented

I'm glad someone else confirmed the error as well I though it was a reproducible issue.

delacosta456’s picture

delacosta456 commented

hi alex_drupal_dev ..
A patch have been uploaded here Patch for manualcrop.. but not working for me .. can you please give a try on your side and let me know if ok please. thanks

Anonymous’s picture

Anonymous (not verified) commented

Sure will do. :)Try out the new version. It looks like this got rolled into Dev.

delacosta456’s picture

delacosta456 commented

hi alex_drupal_dev ..
Truly the dev solve the problem.. hope it won't be temporal.