Media Field Gallery provides an enterprise-ready, no-code solution for displaying media fields within Drupal Views. It transforms standard media references into interactive, responsive galleries supporting Images, Video, Audio, and Documents (PDF/DOCX) with built-in preview capabilities.
Validated against PHPCS (Drupal Standards) and Drupal Practice to ensure clean, maintainable code.
Vetting Request:
I am the lead maintainer and am seeking "vetted" status to opt this project into the security advisory policy and remove the security warning for my users.
Project link
https://www.drupal.org/project/mediafield_gallery
Comments
Comment #2
vishal.kadamComment #3
avpadernoThank you for applying!
Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.
The important notes are the following.
Keep in mind that once the project is opted into security advisory coverage, only Security Team members may change coverage.
To the reviewers
Please read How to review security advisory coverage applications, Application workflow, What to cover in an application review, and Tools to use for reviews.
The important notes are the following.
For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues.
Comment #4
vishal.kadam1. FILE: mediafield_gallery.info.yml
core_version_requirement: ^9 || ^10 || ^11A new project should not declare itself compatible with a Drupal release that is no longer supported. No site should be using Drupal 8 nor Drupal 9, and people should not be encouraged to use those Drupal releases.
2. FILE: mediafield_gallery.module
For a new module that aims to be compatible with Drupal 10 and Drupal 11, I would rather implement hooks as class methods as described in Support for object oriented hook implementations using autowired services.
It would require increasing the minimum Drupal 10 version supported, but Drupal 10.1 is no longer supported.
The usual description for a .module file is “Hook implementations for the [module name] module”, where [module name] is the module name given in the .info.yml file.
3. FILE: templates/media-item.html.twig and templates/overlay.html.twig
Strings shown in the user interface must be translatable. That holds true also for strings used in template files.
4. FILE: templates/overlay.html.twig
Twig code needs to be correctly indented. Drupal uses two spaces for indentation, not four spaces or tabs.
5. FILE: src/Form/MediaFieldGallerySettingsForm.php
ConfigFormBase::__construct() requires two parameters. See the change record.
With Drupal 10 and Drupal 11, there is no longer need to use #default_value for each form element, when the parent class is ConfigFormBase: It is sufficient to use #config_target, as in the following code.
Using that code, it is no longer needed to save the configuration values in the form submission handler: The parent class will take care of that.
For this change, it is necessary to require at least Drupal 10.3, but that is not an issue, since Drupal 10.2.x is no longer supported.
New modules, which are compatible with Drupal 10 and higher versions are expected to include type declarations in property definitions, and use constructor property promotion.
6. Fix the warnings/errors reported by PHP_CodeSniffer.
Note: I would suggest enabling GitLab CI for the project, follow the Drupal Association .gitlab-ci.yml template and fix the PHP_CodeSniffer errors/warnings it reports.
Comment #5
vishal.kadamI am changing priority as per Issue priorities.