Edit Module fails for "pseudo" fields provided via Relationship or Appended Global Text in Views

since there is no patch to review, this should be "active"

This patch fixed the problem for me.

This is also a problem with relationships. I think we could combine this solution with an additional check to see if the field is provided via relationship, and if so, do not make it editable since it belongs to an untraceable entity.

Synatx error in #4. My bad.

Oh jeez. Slow down, brantwynn...

This patch is tested and working on my end. Sorry about the messed up patches in #4 and #5.

I tested patch and it is working on my configuration. I am still trying multiple configurations to test this module how it handles different scenarios.

default node template:
What I found out is that if I use regular drupal node template for displaying nodes I can change node properties such as author and creation date, and all other fields.

panels:
In combination with panels I can't change author of the node nor creation date (adding them from panels "add content" under "node" group of fields and properties).

panels + views
When using panels in combination with views a field "date created" can be edited but author's name (via relationship) can't be - this is because of this patch and because we don't want to change author's name. When adding field content->author's id in views without relationship to author I get "The requested page could not be found." popup window. This is part of node as it is a node property that relates to user. This is still a bug that patch #6 doesn't resolve.

What I would like to accomplish: change node properties such as author of the node and creation date via views. Any suggestions?

Also is there a way to select to which parts of website can use edit module (per content types, views, panels...)?

this patch fixes a similar issue
https://drupal.org/node/1830518#comment-7303322

I can confirm that this patch works for me as well

I can confirm that the patch in #6 works as announced.
Code looks just fine.

Asked for maintainer advice in #1830518: Views integration (use Views' render pipeline to re-render edited fields in Views).

I can confirm that this patch works for me also.

I'm getting the error described here:
https://drupal.org/node/2000830

...but only in webkit-based browsers. As that issue was closed and linked here, I tried patch #6, but it didn't work for me. I'm using a global PHP field, rather than a global text field.

Edit: It worked fine. I just...made a stupid mistake. Patch fixed the problem for me. Thanks!

#6 does work

#6 does the job for me also

I'm also getting this error on views that display a Link field. Disabling Edit or removing the Link field from display makes the error go away.

Please see #2149185: Figure out a way to *start* in-place editing inside a View — on a per-entity basis, just like elsewhere on the problems we need to solve before we can make Edit + Views integration a reality.

This issue is blocked on that issue.

In the 7.x-1.0 branch of Edit, the edit_preprocess_views_view_field function does not exist. I went back to commit cf62974 when this function existed and copied it back into Edit.

I'm not entirely sure how to test of the original problem that the patch in #6 addressed, but, after testing with Edit and Views I've at least convinced myself that this patch doesn't break anything obvious.

Regarding #19, I believe all that functionality was moved to https://drupal.org/project/edit_views

#20 is correct.

This patch is for the earlier version of Edit (revision cf62974) - sets up a whitelist for known problematic fields. To be applied on top of #6. (You can safely ignore, its just a monkeypatch for some specific builds we are trying out and I needed a public place to post it)