In this page: admin/panels/panel-page/userprofile/edit/content
When I click to add/edit content of panels, empty popup-window appears and separated error message in it's own little window. Error message says only that "An error occurred.".
Firebug says also:
missing } in XML expression
[Break on this error] #mini-panel-user_basics div.panel-row-1 div.panel-col-1 { width: 20%; }\n
content (line 7)
POST http://rihmasto.fi/kehitys/panels/ajax/add-content/1/row_1_1403 (2788ms)jquery.js (line 2)
ParamsHeadersPostResponse
Response Headers
Request Headers
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>403 Forbidden</TITLE>
</HEAD><BODY>
<H1>Forbidden</H1>
You don't have permission to access /kehitys/index.php
on this server.<P>
<HR>
<ADDRESS>Apache/1.3.33 Server at rihmasto.fi Port 80</ADDRESS>
</BODY></HTML>
So how to solve the problem? :o
toni
| Comment | File | Size | Author |
|---|---|---|---|
| #33 | 100317-panels-http-error.png | 23.81 KB | Joar |
Comments
Comment #1
michelleMoving this to panels. I don't know js so am not any help with panels js errors.
Michelle
Comment #2
sdboyer commentedThis javascript error has reared its head in a number of circumstances, and we've yet to track down the source of it. Lemme start with the obvious, though - the root URL for the drupal site that contains the panels module is http://rihmasto.fi/kehitys, NOT http://rihmasto.fi, correct?
Comment #3
cnolasco commentedHello I had the same problem and solved it by installing the module jquery_update .-
Greetings
Comment #4
anahowa commentedI have the same problem
installing the module jquery_update doesn't help. :(
Comment #5
nipsy commentedEven the convoluted jQuery versioning issues with jquery_update and associated conversations haven't provided anything useful for this.
Anyone with any ideas at all? Also FYI, this was not on a secure page and it was given and ID (both of these are in the Panels2 documentation as potential issues)
:-|
Comment #6
merlinofchaos commentedvolokettu: The problem you're getting looks like a misconfiguration on your server; that's apache refusing to even give access to the server. I have no idea why it would be doing that, but that doesn't appear to be something Panels can do anything about.
For the rest of you: Saying you have the same problem doesn't help debug the problem. I'm sorry you're having the issue, but if all you've got to say is a line of "I have this problem too" then you're not helping.
Comment #7
merlinofchaos commentedComment #8
Limay commentedI had the same problem. It resolved when I downgraded the module Advanded Profile from Dev to Beta 3. I don´t know why happen this. Dev version of Advanced Profile shows 2 warnings: http://drupal.org/node/246191 Maybe this is related to the problem with Panels.
Comment #9
michelle@Nefer: Couple things...
1) Don't use the dev version of advprofile. As the project page says, it's in the middle of a bunch of changes.
2) That error was a typo on my part and nothing to do with panels or javascript.
Michelle
Comment #10
barth commentedI also experienced this problem. I'm not a programmer, but I eventually pulled out this error:
uncaught exception: Security Error: Content at https://example.com/admin/panels/panel-page/home_page/edit/content may not load data from http://example.com/panels/ajax/add-content/3/top.
which pointed me to Secure Pages. Once I disabled secure pages on admin pages, the content window loaded fine, so perhaps this issue is related to an https/http issue?
Comment #11
michelleI don't think it's an https thing as I've never used that and I've been hit by this error.
Michelle
Comment #12
udig commentedGuys,
Couple of observations:
1. Agree with Michelle - same phenomena on my local test environment - no https.
2. I narrowed this behavior to specific element which was causing the message to appear on any other element I tried to add/edit. Whenever I add the 'Couloir Slideshow' block on my panel this message appears (after saving the panel). Once it's out the panel goes back to it's normal behavior.
3. Tried to add another 'Couloir Slideshow' (different) block - strangely enough the panel is working o.k. meaning that it seems to be the specific instance of the first block that is causing the issue.
4. Just a thought - my site is non English site (Hebrew). Does that rings a bell to anyone?
5. Based on the above I would suggest that anyone who bumps into this issue will try to narrow down the problem to the specific content item (block?) that is causing the message to appear. Then let's cross the info...
(merlinofchaos - I hope this was not just another "I have this problem too..." whining :) )
Udi.
Comment #13
sdboyer commentedIt wasn't just another whine :)
1. Yep, I've observed it without https.
2. Unfortunately, I've seen the error on the display content editing form as well as the context form, and some other spots as well, so the problem's a little bit more widespread.
3. This is helpful, though. Errors that are only quasi-repeatable are...well, special.
4. Nope. Least, I don't think so.
5. See #2.
Nevertheless, thanks for the detailed points, and it does help to at least have this up for reference when I can finally jump on it. Now that I've got my AJAX debugging server, maybe I'll actually be able to root this one out once I finish some other panels business.
Comment #14
moonray commentedI've gotten the same error. Disabling Secure Pages (and making sure you change https to http) makes panels function properly again. Re-enabling Secure Pages makes it stop working again.
The error identifies not being able to fetch data from http when the main page is on https.
Comment #15
nath commentedI started getting that message as well. I don't use https but I also don't know what change on our site was responsible. I haven't yet managed to get it to work again.
Comment #16
merlinofchaos commentedQuick notes:
udig: Your error report was useful. +1 and thank you for being informative.
If you're using 'secure pages' and that was the problem, this has been in the Known Issues text file for quite some time.
Comment #17
nath commentedI'm sorry but my problem seems to be something different. I will open a new issue.
Comment #18
taldrup commentedWORKAROUND for "An error occurred." with editing panels.
I had this problem suddenly show up after adding securepages to my site.
I understand this workaround may not work for everyone as there may be another cause for this issue.
But it worked for me so here is what I did:
1. I went to admin/settings/securepages.
2. In my secure pages config I have the radio button "Make secure only the listed pages." checked.
3. Make sure you check "Switch back to http pages when there are no matches
4. I added admin/panels/panel-page/* and admin/panels/panel-mini/* to the "Ignore pages:" textbox and the problem went away.
Comment #19
merlinofchaos commentedFYI that workaround has been in the KNOWN_ISSUES.txt file that ships with Panels for quite some time. I think a lot of people don't see this file, though.
Comment #20
kay.beissert commentedI don`t know if this will help but I found a solution in saving the pannel before editing. I `ve tried in on three installations (online and local) and it works for me.
Thank you
Comment #21
steveoliver commentedI had this same problem...until I assigned proper permissions in access control. D'oh!
Comment #22
agapetry commentedSaving prior to editing also worked for me, after all the other workarounds didn't (or didn't apply).
My usage is with Advanced Profile Kit. No Secure Pages. No permissions problems. I was getting “an error occurred while attempting to process the pane configuration modal form” on every attempt to add or edit content in the User Profile panel page. Then I clicked the "Save" button (on both Settings tab and Content tab) before the edit attempt. I only had to do that once; now I can add or edit content without issue (and couldn't reproduce the error if I wanted to).
Comment #23
ambereyes commentedActually, I think I figured it out.
I had already successfully created panels and og_panels w/o incident till I installed og_blueprints. Og_blueprints has a known error that prints out at the top of every page.
Suddenly i started receiving the "An error occurred ..." message whenever I tried to add content to a mini-panel. In Firebug, the server response "seemed" right just as others have noted - namely merlinofchaos I think.
But I noticed something else in the response ... the og_blueprint warning message.
Hmmm, so I turned off errors to the screen ... and the message still displayed. So I turned off the module ... and Voila the problem was solved.
I had noticed that almost everyone who reported this problem also mentioned as an aside that they were experiencing other problems in addition to the "An error occurred ..." message.
So I think that what is happening is that the "fix" everyone is reporting is the fix for their real error, and once that is fixed, the panels javascript is able to parse the response properly from the server.
So maybe one way to truly solve this problem is to make panels less vulnerable to errors in other modules. I am not a ajax expert, but maybe searching for the start of the expected output instead of assuming that what you receive is always in direct response to your post. Now, I have no idea how to do any of this ... but I am hoping someone else will take this idea and run with it.
Katrina
www.ambereyes.net
Comment #24
sdboyer commentedWouldn't that be embarrassing, if it was one one of my modules causing an issue in one of my other modules. Although, I haven't had this problem in my blueprints sandbox. But I'll poke at it and see if I can't get it to complain.
I am starting to feel that a fair part of the problem boils down to Panels' current ajax handling being brittle.
Comment #25
dtabach commentedI have two identical sites (same DB and files) running in the live server and in the local server. This error happens in the live server, but everything goes fine in the local server.
Live server (where the error occurs):
Drupal 5.10
Configuration file Protected
Database schema Up to date
File system Writable (public download method)
GD library bundled (2.0.28 compatible)
Job queue There are no queued jobs.
MySQL database 4.1.22
PHP 4.4.7
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Web server WebServerX
jQuery Update Installed correctly
The current installed version of jQuery is 1.2.6
Local server (Mac MAMP PRO 1.7; no errors):
Drupal 5.10
Configuration file Protected
Database schema Up to date
File system Writable (public download method)
GD library bundled (2.0.34 compatible)
Job queue There are no queued jobs.
MySQL database 5.0.41
PHP 5.2.5
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Web server Apache
jQuery Update Installed correctly
The current installed version of jQuery is 1.2.6
Panels version in both sites is 5.x-2.0-rc1a.
Comment #26
Saulo commentedHello dtabach!
In my case, disabling the ModSecurity (mod_security) of Apache, it worked.
SecFilterEngine Off
SecFilterScanPOST Off
The above entries in the .htaccess will disable the ModSecurity (mod_security) module for the domain.
Comment #27
mutazmq commentedGuys, I got of the problem when I commented out this line in template.php :
drupal_add_js(drupal_get_path('theme', 'plutado_blue') .'/js/jquery-1.2.6.min.js', 'theme');
I think there is conflict between the jquery files so pay attention to the modules that pay attention to use different versions of this file.
Comment #28
sdboyer commentedDo not change across major versions, please.
Comment #29
alienseer23 commentedSaving worked for me as well using Drupal 5.12, Panels 5.x-2.0-rc1a, and APK 5.x-1.0-alpha5. I clicked "save and proceed" on all of the tabs, beginning with "settings" and then I just clicked "save" on the content tab, and now I can add and edit! Thank You for posting your work-around!
Comment #30
buzzlightyear commentedok,
we had the same problem, and it started when we moved to a new server. I think It's basically got to do with apache.
could you please post your phpinfo here (local and live server)?
Update: it worked when I used IE instead of Mozilla FF.
try it!
Comment #31
lias commentedYes, IE worked when Firefox wouldn't launch the window. Thanks!
Comment #32
esmerel commentedNo changes to be made to 2.x code.
Comment #33
Joar commentedI have the same problem. When i go to "Content" and click the dropdown and choose "Add content" a loading popup pops up and after a few seconds i get an alert (see attachment
100317-panels-http-error.png).A curl to the address that is requested (an ajax address with encoded colons (:) in the URI) results in this:
It's the same result if i curl with unencoded colons (:)
If i remove the colons (both encoded and decoded), this is what i get:
I believe it's the colons (:).