Closed (fixed)
Project:
Drupal.org customizations
Version:
7.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Dec 2014 at 21:13 UTC
Updated:
29 Nov 2024 at 17:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
pwolanin commentedHere's a start, but still needs testing and the role-based access added.
Not sure where the tabs come from either?
Comment #2
drummThe tabs are in drupalorg_crosssite; and we don't have a clean way to permission them, so far every tab has been available to everyone. The menu system, I think a local task, will be nicer; the menu system will be better at handling permissions.
Moving the whole set of Views to a Feature would not be a bad thing.
Comment #3
pwolanin commentedOk, well not sure about featurizing. Here's a version with the tab and role-based access.
Comment #4
greggles+1 for this idea. Thanks for working on it pwolanin!
Comment #5
drummComment #7
drummComment #8
drummNow deployed: https://www.drupal.org/security/unpublished
Comment #9
pwolanin commentedThanks - though I don't see the tab?
Comment #10
gregglesYeah, the tab is not visible, but the url seems to work.
Comment #11
yesct commentedneeds work for the tab, unless @drumm wants a separate issue for that.
Comment #12
gregglesIt's also "needs work" because it doesn't contain any content.
Comment #13
pwolanin commentedApparently the terms to exist in the table when the content is unpublished
Comment #14
drummViews joins on the
taxonomy_indextable to know which nodes have the security announcement terms. This table is only maintained for published nodes, so it won’t show anything.#2461167: Create Security announcement content type would move this from a term to a content type, making the View possible without any trickery.
Comment #15
drummhttps://www.drupal.org/project/drupalorg/issues/3475098 actually did this. Marking flxed for crediting the work done here.