An Error Occurred At /admin/build/views/ajax/config-item
connections all over the world. Join today Download & Extend Drupal Core Distributions Modules Themes ViewsIssues An error occurred at /admin/build/views/ajax/config-item/view_name/default/field/value Closed (duplicate)Project:ViewsVersion:6.x-2.8Component:CodePriority:NormalCategory:Bug reportAssigned:UnassignedIssue tags:viewsFivestarviews 2.3devel themerReporter:drastikCreated:March 29, 2009 - 19:20Updated:February 24, 2011 - 03:29 Log in or register to update this issue Jump to:Most recent comment Most recent attachment As of today, using most current versions of everything, fivestar 1.13, views 6.x-2.3, voting api 6.x-2.0-rc2 . I've seen posts that this was an issue in the past, not sure if it's because of the newer views version. I also tried switching to the lastest dev versions and did not work. This error occurs after I've set the Node -> Voting Results relationship and I'm trying to add the Field for Voting API Results -> Value. When I add the field or try to edit it I get this message as a pop up alert. "An error occurred at /admin/build/views/ajax/config-item/view_name/default/field/value"Files: CommentFileSizeAuthor #14 error-view.jpg268.56 KBprasannah.ganeshan #9 error-messages.jpg141.47 KBprasannah.ganeshan Comments Comment #1 gunzip CreditAttribution: gunzip commented April 1, 2009 at 11:47pm same here it happens when i try to add a field "Voting API results: Value". the error follows: Fatal error: Call to a member function get_handlers() on a non-object in /.../sites/all/modules/views/handlers/views_handler_field.inc on line 252 Log in or register to post comments Comment #2 markdorison CreditAttribution: markdorison commented April 2, 2009 at 2:10pm I am encountering the same issue. Log in or register to post comments Comment #3 dids CreditAttribution: dids commented April 7, 2009 at 5:11pm I also got the same problem, everything updated to latest dev. Log in or register to post comments Comment #4 kappaluppa CreditAttribution: kappaluppa commented April 27, 2009 at 9:37pm Same here. Just upgraded to 6.x-2.5 Actually, I'm not using the Voting API. This just happens with views when I try to update default configurations on anything that requires "Update" to be clicked. Log in or register to post comments Comment #5 ogrady CreditAttribution: ogrady commented April 29, 2009 at 2:15pm I get the same error trying to make edits to or add any view (Drupal 6.10, Views 2.5). Any request req
connections all over the world. Join today Download & Extend Drupal Core Distributions Modules Themes ViewsIssues An error occurred at /admin/build/views/ajax/add-item/VIEW_NAME/default/field. Closed (duplicate)Project:ViewsVersion:6.x-2.11Component:CodePriority:NormalCategory:Bug reportAssigned:UnassignedReporter:osmanCreated:July 9, 2010 - 01:05Updated:May 10, 2011 - 09:54 Log in or register to update this issue Jump to:Most recent attachment After upgrading my drupal instance and views, I begun to get these error messages from Views UI: An error occurred at /admin/build/views/ajax/add-item/PDF/default/field. Error Description: { ... https://www.drupal.org/node/417570 }An error occurred at /admin/build/views/ajax/config-item/PDF/default/field. Error Description: { ... } Error description is encoded JSON data. After decoding it I realized it is the HTML list of all available fields I can use with the views. Other than nothing really related with the error message. Before the upgrade, the instance was Drupal 6.16 https://www.drupal.org/node/849008 with Views 6.x-2.10. Now it is Drupal 6.17 with Views 6.x-2.11 Along with Drupal core and Views module I updated CCK, Filefield, Imagefield and Link modules too. I found a similar issue posted last year for version 6.x-2.6 #417570: An error occurred at /admin/build/views/ajax/config-item/view_name/default/field/value comment #16 But since then the code changed and it doesn't apply to this version. I compared 6.x-2.10 and 6.x-2.11 with WinMerge. check_plain function got my attention due its compatibility with PHP 5.3. Any ideas, solutions? Thanks,Files: CommentFileSizeAuthor #14 drupal_error.jpg265.52 KBljrweb Comments Comment #1 dawehner CreditAttribution: dawehner commented July 9, 2010 at 1:12am Status: Active ยป Postponed (maintainer needs more info) This does not really means a lot. If you look at the other issue you should have seen that this error is caused often by php errors. So i hope you can enable php logging and provide the error message. Log in or register to post comments Comment #2 osman CreditAttribution: osma
connections all over the world. Join today Download & Extend Drupal Core Distributions Modules Themes ViewsIssues Reason for lots of users seeing "An error occurred https://www.drupal.org/node/752290 at /admin/build/views/ajax/(field)/(view)/default/field/(name)" ActiveProject:ViewsVersion:6.x-2.11Component:MiscellaneousPriority:NormalCategory:Bug reportAssigned:UnassignedIssue tags:jquery views fupload add another item form jsonReporter:piersgCreated:March 25, 2010 - 01:01Updated:March 20, 2012 - 14:45 Log in or register to update this issue Jump to:Most recent attachment There are a lot of people on this site reporting problems with an ajax error message box when attempting to add fields, modify settings etc when editing a an error view. Most solutions given involve turning off ajax/javascript editing in /admin/build/views/tools but this is an unsatifactory solution. I have solved this problem for me but this involves changes to drupal core files. The basic reason is that drupal_to_js does not produce valid json. The ajax callback then fails and the message box is shown. Read on... Program flow: I have a an error occurred field in a view. I click it to modify it, and a jquery mod catches the click and the code in views/js/ajax.js runs. The ajax code at line 247 in ajax.js changes the URL from xxx/nojs/xxx to xxx/ajax/xxx, adds the "throbber" and some other CSS stuff, and runs an ajax call to xxx/ajax/xxx. The code in views/includes/admin.inc is then called. This generates the HTML to modify the views page. This is then passed to views_ajax_render in views/includes/ajax.inc to render into json and send to the browser. This in turn is done by drupal_json() which itself sets the header and runs drupal_to_js in /includes/common.inc. Still with me? The problem is that drupal_to_js does not produce valid json. The JSON specification is detailed at http://www.json.org/. There is a json validator at http://www.jsonlint.com/ which fails the json returned by drupal_to_js. The two main problems are as follows: The first is that drupal_to_js "use(s) HTML-safe strings, i.e. with <, > and & escaped." (common.inc line 2434). This means that < is replaced by \x3c, > by \x3e and & by \x26. However these s