I've got a bit of an odd setup, will try to briefly explain:

I've got a view which lists 'vehicles' (table - using flipped table so vehicles are columns) .. within that I have a field of 'Jobs' (one row), which is actually another view (using Views Field View) called 'Jobs' which uses contextual arguments (ie: the vehicle) to list only jobs that apply to the vehicle (column).

This all works well, I'd tried to implement passing exposed filters from the parent view to the 'child' views, however gave up on this and just implemented some javascript which achieves the same thing.

Now, the issue. Each 'job' has a 'status' field, this is the editable field. When there's only a few (ie, upto 3 or so) jobs listed on the page, the editable field works fine, status is updated etc.

When there is more than a few (and under testing there's been up to 30), only the first few editable fields will actually work. Trying to update any other editable fields will throw:

An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /system/ajax
StatusText: Service unavailable (with message)
ResponseText: EntityMalformedException: Missing bundle property on entity of type node. in entity_extract_ids() (line 7501 of /home/poc/public_html/includes/common.inc).

As a work around I can just filter the results down so there are never more than a few jobs listed, however this isn't a viable solution.

If interested you can reproduce the error on this live site:
http://poc.purplec.com.au/dispatch-log?date%5Bvalue%5D%5Byear%5D=2012&da...

User: dotest
Pass: test123

The above authenticated user has access to edit nodes etc. Please use the above link .. You'll find the error will always occur when trying to edit the field in the 4th column, the first 3 will work. This always occurs .. you can try filtering by other dates where different amount of jobs come up however the issue is always the same, the first few editable fields are fine, the rest throw an error.

Any feedback on this issue would be greatly appreciated, or even suggestions on a better way to implement this as I'm thinking the 'views within views' approach may be (one of) the cause of my woes. I'm open to any suggestions on how to build this as its more of a 'proof of concept' / 'test development' project. Display Suite has been mentioned, but I'm not hugely familiar with it.

Comments

enap’s picture

enap commented

Just for further clarification, the issue doesn't occur when its only job listing 1 view and theres loads of editablefields .. For example: http://poc.purplec.com.au/job-ref/1 (listing all jobs for truck nodeid 1) ..

All editable fields work and there are alot more than 3 .. so I'm certainly leaning towards the view within views causing the issue. Only seems to occur after more than 1 (or 2) of the nested views are loaded. If you filter the dispatch-log page to only 1 vehicle (so only one column/nested view), seems to work OK..

Still not sure how to go about resolving this.. any suggestions?

enap’s picture

enap commented

Had a rethink & recreated my view in a different way avoiding nested views .. working fine now. :)

emcniece’s picture

emcniece commented

Woah, it's the nested views that kills this? Thanks for the pointer... I've been going crazy trying to troubleshoot this inside 5-layer nested views/panels. Will try that out.

thihathit’s picture

thihathit commented

using 'master' display on child views might fix this. at least that fixes in my case. the problem is indeed nested views

jacobupal’s picture

jacobupal commented

I have AJAX errors in 2025 and the various interactions which cause this seem to be: VBO, Pagination and Exposed Filters

Here's the console error when using exposed filters:

An AJAX HTTP error occurred.
HTTP Result Code: 404
Debugging information follows.
Path: /views/ajax?field_question_value=&title=&flagged=All&status=0&flagged_1=0&uid=&field_question_triage_value_op=empty&field_question_triage_value=All&ajax_form=1
StatusText: Not Found
ResponseText: {"message":""}',
name: "AjaxError",
stack: "
  @[webroot]/core/misc/ajax.js?v=10.3.1:196:32
  @[webroot]/core/misc/ajax.js?v=10.3.1:1921:3
  "

By the looks of it, the request URL probably needs cleaning up to work?