Problem/Motivation

On pages like https://www.drupal.org/sa-contrib-2025-101, there is a sidebar block that uses the legacy credit data “Contributing organizations for this advisory” that needs to be replaced.

Proposed resolution

Build the View in D10, so it is ready to be embedded when security advisories are ported. Until then, the content can be included from an API that provides the View’s output.

The View has links to distinct organization pages that are either an attributed customer or organization for someone credited on the advisory. D10 does not have URL aliases/etc yet, so the links will be raw new.drupal.org/node/nid links, which is okay as they redirect, and won’t need further adjustment as more functionality migrates.

In D7, include the contribution record ID in Drupal.settings for JS to make a frontend request to get the View output and place it on the page. This avoids writing more logic in D7.

Issue fork drupalorg-3543926

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

drumm created an issue. See original summary.

drumm’s picture

Issue summary: View changes
fjgarlin’s picture

We might not even need a view for this as we can access the contribution record in a jsonapi format: https://git.drupalcode.org/project/contribution_records/-/blob/1.0.x/src...

This might already have all the data we need.

fjgarlin’s picture

Version: 1.0.x-dev » 7.x-3.x-dev

fjgarlin’s picture

Assigned: Unassigned » drumm
Status: Active » Needs review

MR https://git.drupalcode.org/project/drupalorg/-/merge_requests/394/diffs ready for review.

Can be tested at: https://drupal:drupal@fjgarlin-drupal.dev.devdrupal.org/sa-contrib-2025-027

If this is merged, the view block can be removed and also the underlying view too.

  • drumm committed 864c466f on 7.x-3.x authored by fjgarlin
    [#3543926] feat: Replace “Contributing organizations for this advisory”...
drumm’s picture

Status: Needs review » Fixed

I moved this to a fresh block implementation so we’re not relying on the old block being placed. This is deploying soon.

Status: Fixed » Closed (fixed)

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