Closed (cannot reproduce)
Project:
Panels
Version:
6.x-3.9
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Apr 2011 at 21:03 UTC
Updated:
20 Dec 2011 at 22:28 UTC
I'm getting an AJAX error whenever I try to modify a region in Page Manager.
While this is bothersome, what's really irking is that this is not new. This issue has been all over the internet for years:
http://drupal.org/node/532260
http://stackoverflow.com/questions/5265134/drupal-views-ajax-error-alert...
It's not a jQuery thing, as I haven't updated jQuery...but even solving this particular bug is not the point.
This stacktrace is completely unreadable and ultimately useless. It's hard to believe that after years of people reporting some kind of ugly CHAOS AJAX the error callbacks haven't been addressed. It's trimmed after a certain length, contains a lot of noise from escaped text that the user does not need to see, and is ultimately unhelpful in actually helping one to determine what the issue is. A lot of improvement could come from just adding an OnError: callback that at least captures the response and processes it a little, replacing url entities and the like, before vomiting on the screen all over the user that has no cup. Panels is one of the most widely used Drupal modules. The error messages should be a little more than an unprocessed JSON object dump in an alert.
Comments
Comment #1
Letharion commentedHello!
Unfortunately, this issue has remained open, without activity, for a very long time. I hope you can understand that between maintaining the module, work, and other obligations, the maintainers are very busy. This leads to not all issues being answered.
In order to figure out which bugs that are still present, I'm going over all low activity bug reports that has not been touched for 6 months, and marking them "Postponed, needs info". In many cases, I expect the bug to have been solved by a newer version of Panels..
If you can still reproduce this issue with the latest dev version of Panels, please just reset it's status to active, and we'll try to work it out. Please remember to post any new information that may be relevant, such as any attempts of your own at debugging.
Regards, Letharion
Comment #2
Letharion commentedA month has passed, and I'm going over the issue queue ones more. Some issues have been closed for other reasons, some re-opened, but this issue has remained silent for the past month.
Because of this, I'm doing a bulk close of a number off issues. I'm sorry that it happened this way, but the issue queue has had to few contributors, and to many questions.
Again, as said in the previous comment, feel free to re-open the issue by setting it to active, if you still need help.
Regards, Letharion.