AJAX HTTP error when trying to add content to a region [#1514030]

Comment #1

thomas1977 CreditAttribution: thomas1977 commented 4 April 2012 at 08:08

From outside this seems connected to the 3.1 issues mentioned in the release notes for 3.2:

"3.1 included some bad IPE logic that made it impossible to add new panes to any region; this release fixes that bug."

I went directly from 3.0 to 3.2 - does this have anything to do with the issue still being present?

Would it be safe to downgrade to 3.0 until the issue gets ironed out?

Log in or register to post comments

Comment #2

snowfire CreditAttribution: snowfire commented 4 April 2012 at 14:38

I get the same error when trying to add content to a panel:
An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /ProcessInstruments/?q=panels/ajax/editor/select-content/1/right
StatusText: Internal Server Error
ResponseText: test
test

new drupal install - 7.12, panels 7.3.2, wisiwig and ckeditor disabled. windows server running php5.
any ideas what could be causing this?

Log in or register to post comments

Comment #3

thomas1977 CreditAttribution: thomas1977 commented 4 April 2012 at 14:52

@ snowfire

Just for the record: I'm running windows server as well. Don't know if this has got anything to do with it.

Log in or register to post comments

Comment #4

snowfire CreditAttribution: snowfire commented 4 April 2012 at 15:47

@thomas1977
- I disabled the admin overlay, and I can now add content.
found another error with 403 and flexible layout.

Log in or register to post comments

Comment #5

thomas1977 CreditAttribution: thomas1977 commented 4 April 2012 at 16:45

Tried switching off the overlay module, but that doesn't make any difference in my setup. Wonder what's going on...

Log in or register to post comments

Comment #6

Co-operatives UK CreditAttribution: Co-operatives UK commented 6 April 2012 at 20:59

Same problem here - on a windows server as well. Tried disabling the overlay but that had no effect.

Log in or register to post comments

Comment #7

thomas1977 CreditAttribution: thomas1977 commented 7 April 2012 at 12:56

@ Co-operatives UK

Just out of curiosity: did you have a clean install with 3.2, or did you (like I did) update from 3.0 or 3.1 to 3.2?

Log in or register to post comments

Comment #8

rarioj CreditAttribution: rarioj commented 10 April 2012 at 12:04

To get it to work, I had to remove line 86 in the file panels/includes/add-content.inc.

So the final function will look like this:

function template_preprocess_panels_add_content_link(&$vars) {
  $vars['title'] = filter_xss_admin($vars['content_type']['title']);
  $vars['description'] = isset($vars['content_type']['description']) ? $vars['content_type']['description'] : $title;
  $vars['icon'] = ctools_content_admin_icon($vars['content_type']);
  $vars['url'] = $vars['renderer']->get_url('add-pane', $vars['region'], $vars['content_type']['type_name'], $vars['content_type']['subtype_name']);

  $vars['image_button'] = ctools_ajax_image_button($vars['icon'], $vars['url'], $vars['description'], 'panels-modal-add-config');
  $vars['text_button'] = ctools_ajax_text_button($vars['title'], $vars['url'], $vars['description'], 'panels-modal-add-config');
}

Log in or register to post comments

Comment #9

thomas1977 CreditAttribution: thomas1977 commented 10 April 2012 at 12:46

@ rarioj

Thanks. However, I'm not too fond of the idea of having to hack module core files. Bad experiences in the past. I'd much prefer an update that fixes the issue.

Log in or register to post comments

Comment #10

rarioj CreditAttribution: rarioj commented 11 April 2012 at 00:18

Me neither. But the cause of the error seems to be the someone leaving out debug message (CMIIW). Thus, I provided the quick fix.

Log in or register to post comments

Comment #11

merlinofchaos CreditAttribution: merlinofchaos commented 12 April 2012 at 17:07

Status:

Active

» Fixed

Removed the message and pushed.

This error is partly because your site is using the PHP setting to print errors to the screen; this can cause issues with AJAX in general and you should turn this off. And while that message should not be there, it's way too easy to get a notice or a warning that would break AJAX this way.