Related: #1824110: Create a new node type filter handler that only displays non product display types.

Right now the node listing is provided by the commerce_kickstart_content_ui module, even though it belongs in Backoffice.
So let's create a commerce_backoffice_content module that will include the handler listed above, and the relevant view.

The view will also need to use the System display plugin from the Admin views project (we should just copy it into our module). That plugin ensures that child paths still work properly after we override the parent one (the node listing).

CommentFileSizeAuthor
#6 bad-admin-views-no-donut.jpg228.27 KBtgeller
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jsacksick’s picture

Status: Active » Needs review
jsacksick’s picture

Tagging

jsacksick’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

tgeller’s picture

In another queue, I raised the question of whether Admin views should be simply included in the distribution. (Not only is the "System display plugin" useful, but also the Content and User views. Unless those are the same thing.)

I'll wait for the response from bojanz at #1889414: Content view has disappeared in default installation! before creating an issue for it.

tgeller’s picture

FileSize
228.27 KB

Note that simply installing Administration Views over Commerce Kickstart 2 causes problems -- see attached screenshot.

bojanz’s picture

We already have our own content view. We don't need the one provided by Admin views.
A nice to have is the "People" view, since we don't have that one. I believe that has an issue somewhere in the queue.