Problem/Motivation

I recently try the Project Browser module (version 2.0.0-beta1) on a fresh installation of Drupal CMS (version 11) (running with PHP 8.3). While testing the "Browse projects" feature, I noticed that one of my modules Opquast Checklist does not appear in the list.

Steps to reproduce

  1. Install a fresh Drupal CMS (version 11) site with PHP 8.3
  2. Check that project_browser module (v2.0.0-beta1) is enabled
  3. Go to the "Browse projects" tab
  4. Clear all filters
  5. Search for the "Opquast Checklist" module

Expected behavior

The opquast_checklist module should appear in the results, as it is compatible with Drupal 11 and listed on Drupal.org.

Actual behavior

The module is missing from the list in the Project Browser UI. When all filters are cleared, I see 4,861 results available, whereas Drupal.org lists 5,918 compatible modules for Drupal 11 under the same conditions.

Questions / Suggestions

  • What could explain the discrepancy in the number of modules shown between Drupal.org and the Project Browser?
  • Are there specific rules or metadata requirements that a module must follow to be included in the Project Browser list?
  • Would it be helpful to document these prerequisites more clearly — e.g., in the README or the Project Browser handbook — so that maintainers can ensure their projects are discoverable?

Thanks

Comments

martygraphie created an issue. See original summary.

martygraphie’s picture

martygraphie commented
Category: Support request » Bug report
chrisfromredfin’s picture

chrisfromredfin
he/him/his
Primary language English
Location Portland, Maine
commented

The real reason for the discrepancy is that we are actually doing a nightly migration to a Drupal 9 site which hosts the endpoint for the project browser module data. New modules may take a while to show up, or something may fail in the migration.

(In addition to other things, like our filters - we will not show modules that are not compatible with the version of Drupal that's running, and we only show ones by default that have security coverage, etc.)

I will see if Fran can take a look at the migration to check on this.

drumm’s picture

drumm
he/him
Location NY, US
commented

You can see the project is migrated at https://www.drupal.org/jsonapi/node/project_module?filter[field_project_...

How project browser is setting up filters for querying might be filtering out the project for some reason.

fjgarlin’s picture

fjgarlin commented

https://www.drupal.org/jsonapi/node/project_module?filter[field_project_...

That initially had field_core_semver_maximum: 11000000, that's why it wouldn't show on Drupal 11.1.3.

I re-triggered the semver range calculation and we now have: 

field_core_semver_maximum: 12999999,
field_core_semver_minimum: 8000000

So the project should appear now.

The reason for the 12999999 is is because release 2.0.5 of that project has core_version_requirement: ">=8" and we have D12 as max value here.

I think that the issue can be closed as there are no changes required in Project Browser.

jeremy.declerck’s picture

jeremy.declerck
Location Antwerp 🇧🇪
commented

I can also confirm this is working now.
The altcha module was not showing up before, but is now.

martygraphie’s picture

martygraphie commented

Hi,
I confirm this is working now.
Thank you for your analysis. This will indeed help other maintainers understand why their module isn’t showing up in project browser.
Sincerely,
Marc

chrisfromredfin’s picture

chrisfromredfin
he/him/his
Primary language English
Location Portland, Maine
commented
Assigned: Unassigned » fjgarlin

Fran - I am leaving this open for you, in case there is anything that needs to change on the infra side. But if there's not, or you are tracking it in a separate issue, please mark this Fixed. I have assigned credit.

fjgarlin’s picture

fjgarlin commented
Assigned: fjgarlin » Unassigned
Status: Active » Fixed

I reviewed the logic on our end and it really seems ok, so I am going to close this issue. If it were to happen again, I'll implement a workaround that is a one-line change, but only if it's needed.

Status: Fixed » Closed (fixed)

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