The module works well on most pages. On some pages - no obvious pattern - it does not:

The pages loads, and a javascript alert appears saying "The requested page could not be found".
On clearing the alert, the page appears normal.
When I then click on "quick edit", the screen greys-out as expected, but fields remain un-editable.

No errors in Firebug's js error log. No errors in the database log.

Comments

l.damen’s picture

Hey Leopit,

I have the same problem.
I think it has something to do with views.

Do you have a view-block with a relationship to a field?

I have created this problem on the following method:

I created a node.
Then i created a view and added a relationship with a fieldcollection, so i can view the fields of the related field collection. I guess if the block shows non-node related information, edit throws the error.

dmsmidt’s picture

I can confirm the error on some pages with a block-view. But the error is present event after removing the relationships in my view.

It's doesn't seem it's theme and other modules related (disabled all except views and edit).

Can't seem to recreate it on a clean install though. Any other thoughts?

leo pitt’s picture

Yes - the page in question does have a view block on it.

However I have another page with a view block where there is no problem:

PROBLEM:
Content type "Page" with view block.
View block shows fields from content type "Newsletter", uses no contextual filters or relationships.

NO PROBLEM:
Content type "Page" with view block.
View block shows fields from content type "Page", uses a nid contextual filter to basically show a field from the Page in a different theme region.

So perhaps the issues is that Edit get's confused when Views places a field on the page that isn't related to the current node? In my problem case, the page is showing fields both from the Page content type and the Newsletter content type?

gilbot’s picture

This seems to happen when you use global text field in views as well.

saltednut’s picture

I am seeing this problem too. In our case:

The View is of Users. We use a relationship of User: Content authored

Then in the fields we are showing node titles and body teasers using that relationship. (Ie: a view of user generated content)

If I remove the BODY field that uses the relationship, the error goes away.

frikovc’s picture

saltednut’s picture

saltednut’s picture

Status: Active » Closed (duplicate)