IMO, the most natural way to expose this is as an edit tab on an existing view. the project page describes a block based way which is fine but not quite as slick.
IMO, the most natural way to expose this is as an edit tab on an existing view. the project page describes a block based way which is fine but not quite as slick.
Comments
Comment #1
Egon Bianchet commentedI agree. Perhaps it's already possible to achieve that effect, but you'll still need two different views ...
Here's my idea: require a special EditView argument to discriminate between viewing a view (sorry :-D) and editing it.
Consider an hypothetic "employee" view, registered for the url "employee". The first argument could be the nid of the organization node, and the second our magic EmployeeView field.
So, 'employee/3/view' would display all employees of organization #3 like a standard table view, and 'employee/3/edit' would display the edit view, all within the same view.
Perhaps that could make it easier to integrate it inside nodes too
Comment #2
Frodo Looijaard commentedThis was, four years ago, a sensible suggestion. These days, though, Views got much more mature, and using an edit tab on an existing view goes contrary to the way it is designed.