I've searched the issue queue and haven't found this exact problem.

When I try to Save a node, i get the error "The path is already in use." *most* of the time. This message doesn't appear when a) the node being saved is the *last* one that appears on the page or b) on the *second* save attempt. However, even when the error doesn't appear, the saved data is sometimes wrong. For instance, one time (at band camp...) taxonomy terms from the *last* node were applied to the node i was saving. Note that I've only added 2 text fields - taxonomy is not even a view field. This hasn't happening since though - in my most recent tests, when Saving does work (second attempt or last node in view) the saved data seems to be correct.

Here's my setup: editview 6.x-1.x-dev (same results with beta1), drupal 6.16, views 6.x-2.8

This might be related to #417404 but I don't get any "array_shift" error messages or log entries.

Comments

Nick Robillard’s picture

This is the issue i was referring to - #417404: D6 Fatal Error - warning: array_shift()

lindsayo’s picture

I'm getting this, too. I don't think it's related to that issue you referenced. My caching is turned off (and I'm using the most current versions of the modules in question).

I am using a nodeference field as part of my Editview.

dustobub’s picture

I can also replicate this issue. I am using Auto Node Title and Unique Field but I haven't experienced any issues related to those two modules. I haven't been able to narrow the issue down very much though.

CCK 6.x-3.x-dev
Drupal 6.19
Views 6.x-2.12
Editview 6.x-1.0-beta2

Thanks,
Dustin

Rory’s picture

Version: 6.x-1.x-dev » 6.x-1.0-beta3

I too experience this as referred to by Nick.

"When I try to Save a node, i get the error "The path is already in use."
This message doesn't appear when:
a) the node being saved is the *last* one that appears on the page, or
b) on the *second* save attempt."

CCK 6.x-2.9
Drupal 6.20
Views 6.x-2.12
Editview 6.x-1.0-beta3

Thanks very much! Such a great module!
Rory

Rory’s picture

When I agree it happens "on the *second* save attempt"... this is within a single page load. Reloading the page makes the issue reappear for each node.

Once I have successfully updated a node in the editview page, I can continue to update that node without the issue if I don't reload the page. But if I reload or visit the editview page again, edit that same node, the issue appears once more.

evlad’s picture

Issue summary: View changes

got this error too. all similar to #5
any updates on this issue?
trying to edit ubercart product price field.
can this to be related to cck nodereference module?