I have spent the last few hours reading issue requests, adding patches, talking to my host company to disable mod security, etc. And yet, I still get the same error.

Steps: Panels 3, Ctools is installed and permissions are all turned on
Create Panel Page
Give it a title,path, etc.
Hit Continue
Select a layout,
hit continue
Open up layout designer
Now, when I open any of the sections, lets say "Region Settings."
A lightbox appears with my regions, no matter what I do in this box, even simply click save I get the following error:
"an error occurred while attempting to process /redesign/panels/ajax/flexible.....blah/blah."

Now, I've modified my modal.js and responsder.js per Merlin's patch for mod security. But nothing changed. I've cleared cache a hundred times. My host company has disabled mod_security...they say. Is there a way to test this? Also, I've noticed some ajax errors in other modules. For example, I can not use the module Fupload, because it hangs on a reload (not ajax error, but js error)...see this ticket for details (http://drupal.org/node/621968).

I've also had to turn off the views javascript/ajax functions because it was causing some random errors, but I haven't had a problem, since turning off views js/ajax.

I'm wondering if these could all be interconnected...but I can't seem to figure out the problem. I'm unable to make a shift/ctrl J call when the lightbox window is open, so I do it, just before hitting "select regions" and I see a bunch of js warnings. I attached a screen shot.

I've tried to give as many details as possible...which may make it more confusing, but if I can provide any other info for you, I'll gladly do it...I've stopped my redesign until I get this taken care of...so any help is appreciated!

Oh yeah, I'm not seeing any watchdog errors, just a slew of js parsing notices, which I've disabled for the time being...but no ajax or obvious errors appearing when I reenact this scenario.

Thank you
Bryan

Comments

merlinofchaos’s picture

merlinofchaos commented

Two things to look at.

1) Apache error_log (or php error log) which might show some kind of an error on the server side when this box comes up.
2) Using firebug, what does the server actually send back when you receive the warning box?

bhylenski’s picture

bhylenski commented

When you say,

2) Using firebug, what does the server actually send back when you receive the warning box?

I'm not sure how to do this, Once the error appears, I'm unable to do anything except close the window. Firebug doesn't respond with anything. I attached a file with a list of JS errors, just before the window error/popup appears.

Please let me know if this is what you were talking about.

Also, my error logs within my cpanel don't display any sort of error. I'm using interactiveonline as my host provider and they're pretty good a resolving issues for me, but they say Mod Sec is disabled, now I'm just waiting to hear back from them about apache errors. Any advice or further info would be great. Is there any other info I can get for you, or look into....I can give you temp admin access if you think it's something wrong with my panel setup.

Let me know, again, thanks for all of your assistance.

Bryan

merlinofchaos’s picture

merlinofchaos commented

With firebug installed in firefox, hit F12 to get the firebug console. Then click whatever it is that fails. Close the window. In the firebug console you should see a POST request -- click on it to expand it and examine the contents that the server returned in the request.

bhylenski’s picture

bhylenski commented

Okay, Merlin

I've been away for the weekend, now I'm back on top of this...I've been trying to create photo galleries as well, using Fupload and/or Node Gallery, but I'm unable to upload images because of a strange ajax error on upload...I'm getting a very similar error now within panels, based on what you told me to do above with Firebug...so I believe all three of my issues are related to this error message?

I have updated my other tickets as well with this same message, any input would be welcome, I have very limited experience with Ajax.

My other tickets are:
http://drupal.org/node/621968
http://drupal.org/node/631670

As for the error...I load the page where I'm about to upload the images or submit the panel and in the case of the panel.... I get a popup with an ajax error, firebug's message is displayed below, it's not exactly the same as the one for the images, just a few line differences in the code, but the error itself is the same. As for the images, when I click submit, the page redirects to itself and either hangs or reloads the page with no changes, hence no images were uploaded...firebug gives the following error:

$(element_settings.element).parents("form").ajaxSubmit is not a function

Then when I opened the details I got the following info..(with lines of code where error was)

anonymous()                                                                     ahah.js?L (line 99)

anonymous(Object originalEvent=Event mousedown which=1 view=window)    jquery.j...val/seq/1 (line 1)

anonymous()                                                           jquery.j...val/seq/1 (line 1)

$(element_settings.element).parents('form').ajaxSubmit(options);\n              ahah.js?L (line 99)
bhylenski’s picture

bhylenski commented

Couldn't get it to work...probably something to do with the install. So, I scrapped the whole drupal install and started again...now FUupload is working, panels, ajax, everything...so I will be using views gallery with Fupload for photo gallery and panels to output all of the content in my format...panels is now working well, thank you for your help...looks like it was an issue with my original install.

Better to start over now, then keep pounding my head against the same wall.

Cheers

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

Ok, I have seen #4 and it is almost always a problem with themes or other modules introducing new versions of jQuery. The latest Panels -dev does protect itself against that, and that is about the best I can do to fix that conflict.

Status: Fixed » Closed (fixed)

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