The requested page "/admin/content/node" could not be found.

I also encounter this issue (#2 - the "not found" error) with Administration Views enabled.

FWIW I'm running Views 7.x-3.0-rc3

I think that there is a wrong link in menu on item "find content". It's "/admin/content/node" but the right link should be "/admin/content/"

same problem here

Same problem - I created an URL alias pointing to an available path displaying a content overview.

subscribing

Subscribing

Could a test be added so menu items which return a 404 aren't included? What that be a good solution?

I solved the problem by fixing the broken view that is called at the path admin/content/node. The view is called admin_content_node (Content). Two things needed to be fixed:

1. The format needs to be set to table (it was showing "missing handler")
2. The field "(User) User: Name (Author)" needs to just be edited and saved (no changes)

Isn't this fixed in the latest 7.x-3.x-dev already...?

I think it is.

I just installed dev and the problem has been fixed.

#8 worked for me. I tried #11 first but that didn't work on my local. #8 worked on local and then I put it live and it works on 7.9.

The Views dev version did not fix the problem as in #11. I guess they meant DEV of admin_menu. But when I tried the dev of admin_menu, the modules page reported a bunch of incompatibilities with Core 7.10, so I went back. I recently upgrade views to 7.x-3.1 with admin_menu 7.x-3.0-rc1 and started getting this error. #8 worked, but only after clearing cache. I found I did not get those errors before make #8 changes if I disabled Administration Views module. Then did a search and found this thread.

Note: you have to do the #8 changes to the view admin_content_comment and possibly similar changes to admin_user_user too.

Thanks for the help!

Thanks. #8 fixed it for me too.

Hi there, just wanted to set this issue as active since it's still present in 7.x-1.x-dev and #8 is a fix but the module itself is still broken (for admin/content/node at least).

Just in case #8 is the definitive way to fix this issue, here's a patch with the view (node view) re exported after doing it.

I hope it helps.

I just realized that #8 only removed the error, but the view is not working (if you see the patch you'll see why). We probably need to re create the view.

Thank you guys.. #8 was helpful!!!

This is fixed in the latest dev version I think. @sun can you confirm? Seems like this issue won't be getting too far.

yeah, pretty sure it is already.

Let me publish a first alpha release right away...

That said, I'd love some help to dig through the queue and check for absolute requirements for getting towards a stable release.

@sun, I would be happy to help out with that. I will take a look tomorrow if you like?

@damiankloip: That would be highly appreciated :)

Others are welcome to help, too, of course! ;)

so i get
The requested page "/node/64/unpublish/ejD3eKudWkM_A_ytLhhupRRYsVBA47cX6VgNsWdx_I8?destination=listings" could not be found.
when i click link of publish/unpublish

got the dev and same result

This issue appears to have resurfaced in Drupal 8: See https://www.drupal.org/node/2647902.

Re-opening because I'm not sure how to process this linkage properly -- please close when it's done.

I don't think this is related to D8, the code is drastically different. Closing again.