I had a conflict with panels module that prevented me from adding new panel panes to panel pages which I tracked down to image assist.

Specifically, 

if ($(this).is('textarea.teaser:not(.teaser-processed)')) {
      Drupal.behaviors.teaser(context);  
    }

was causing the conflict.

I resolved the problem by setting img_assist to not apply to panels pages.

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented
Status: Active » Postponed (maintainer needs more info)

Could you please elaborate a bit more on what exactly was the problem and why you needed to fix it, as well as how and why you fixed it that way?

Jody Lynn’s picture

Jody Lynn
she/her
Primary language English
CreditAttribution: Jody Lynn commented

Steps to reproduce:

Enable img_assist and the latest dev or alpha of panels (either one).
Make a panels page.
Go to the content tab and add a new pane. The ajax window pops up.
Choose 'custom content' (for example) from the panel pane choices.
Submit the new content.

I would get a white screen with what looked like a serialized array of data listed, presumably json data meant to be received via ajax. The pane is not saved.

I tracked this down to an img_assist js conflict by disabling one at a time the modules which were adding js to that page.

However now I'm not positive because what I had believed fixed it is no longer working. Javascript conflicts get confusing. I will check into it a bit further.

sun’s picture

sun
Primary language German
Location Karlsruhe
CreditAttribution: sun commented

Any updates?

Jody Lynn’s picture

Jody Lynn
she/her
Primary language English
CreditAttribution: Jody Lynn commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Sorry, it's still mistifying me and now I'm not convinced it is related to img assist necessarily. I'll close the issue to get it out of your hair and reopen if I unravel it any further.

bcobin’s picture

bcobin CreditAttribution: bcobin commented

Yes! It was Image Assist! I had the same problem with adding custom panels and it was disabling Image Assist on Panel pages that seems to have fixed it. Thank you SO much - I was going nuts here...

lunen33’s picture

lunen33 CreditAttribution: lunen33 commented

I was able to fix this by going to admin>settings>image assist.

Go to the access settings link. Then change the image assist to display only on selected pages. In my case I just used: node/*. Once this was fixed, I still had problems with the html format being grayed out as discussed here: http://drupal.org/node/332039. I found a work around for that too. It's listed on the linked page.

jrabeemer’s picture

jrabeemer CreditAttribution: jrabeemer commented

I can confirm this fix. Just whitelist only nodes and comment forms. By default, img_assist attaches to all textareas which kills JS event binding in panels2 popup code in Drupal 6/Acquia.