[DX] Convert /node to a View

[quicksketch]

Sub-issue of #151. We should convert the main listing provided by node module to a view.

Drupal.org issue: https://drupal.org/node/1806334

[DirectorHaas]

Just checked this out. Simple VBO seems to be working. Question: so what we want here is the exported to code versions of all the Views that have issues opened, yes?

Seems straightforward enough, so is the status of this still good for someone to do the Views click around and export these to custom views code?

Thinking the answer is yes, getting verification before spending evening / weekend time. Thank you!

[DirectorHaas]

Also looks like VBO are primarily for Content, not user (or taxonomy?)

" Content: Bulk operations
Provides a checkbox on each row and a form for executing bulk actions on nodes."

So something like add relationship:
"RELATIONSHIPS
User: Representative node"

Will need to get a little creative w/ it? Asking again if were 99% ready to move on the views and any special format we need to have the exported views/custom code. Thanks!

[quicksketch]

Also looks like VBO are primarily for Content, not user (or taxonomy?)

For now we're looking at converting admin/content (#150) and admin/people (#149) to views. Both nodes and users should be VBO-capable at this point.

Asking again if were 99% ready to move on the views and any special format we need to have the exported views/custom code.

For this issue, it's pretty straight-forward I think. When you export the view using the Config Manager, it'll export it into a JSON file. Just drop this file in /core/modules/node/config. After exporting, you'll need to manually open the file and add two lines to the JSON file to make it act as a "default" config:

  "storage": 4,
  "module": "node",

This will prevent the /node view from being possible to delete (though you can still disable it) and makes the "revert" option show up in the Views interface. See the config files in /core/modules/image/config for examples.

[DirectorHaas]

Thanks for the info. Noticed everything is really shaping up.

When it's fairly stable, interested looking into converting contrib modules like Feeds, maybe Wordpress_Migrate, and also looking at best ways to get D6 / D7 data into Backdrop.

May be wishful thinking but, hey, why not.

[DirectorHaas]

Spending some evening w/ this view "Issue #150: Convert admin/content to a View." Things seem straightforward except for the drop-down in the last col for EDIT/DELETE. Maybe overlooking something there, trying to use a Global: drop-button, may need to hack the exported views code to put in an edit and delete dropdown.

More importantly, and perhaps it's just a permission, but not seeing a "Views" to "Export" option or did it move around where it's not to be seen! Heh.

Thank you.

[DirectorHaas]

I should have commented this in the other thread, since it is about admin/content instead of admin/node, but the Views->Export function could be useful for both, may just be hidden?

[quicksketch]

The pages for exporting directly within Views were removed because just about everything is exportable now. Rather than making separate interfaces, all exporting/importing for the entire site is done at the Configuration management interface. Although it lacks an individual export, you can download the entire zip and then pull out the config you want. Although it's generally easier just to pluck the config file you want out of the files/config_*/active directory. The concept of "exporting" generally is dead, since all configuration is always in an exported form to start with. You just need to copy the export to a module's config directory to have it imported on module install.

[DirectorHaas]

Just tried a test, neat! I should have been following everything more closely, been working w/ Apps, not Drupal-y stuff for much of last year. Pretty cool. Thanks again!

[tarekdj]

PR: backdrop/backdrop#656
Ready!

[klonos]

Is this issue here still relevant? /node currently redirects you to the home page, and AFIK we have a layout and a default view for it.

[laryn]

@klonos You're right. See @docwilmot comment in the old PR: backdrop/backdrop#656 (comment)

[klonos]

...yeah, lets close it then 😄

[klonos]

While testing the PR for #3343, we've accidentally discovered that this was never actually done. The promoted view provided by Backdrop core only provides a block and a feed display, whereas there should be a page display as well (which should have /node for its path).

We should also adjust node_page_default() to use a views_embed_view() + call watchdog_deprecated_function(), and remove it later in 2.x.

[izmeez]

It's not clear if this was finalized in another issue or remains open: replace /node with a view. The last few comments suggest it was agreed upon and then forgotten. There's an old PR and the patch only applies partially and will need work if this issue is still alive.