EZ Likes integrates a lightweight, self-hosted sharing system with Drupal-powered websites using a configurable Drupal module. It supports automatic injection of a Share action button on full-view-mode node pages that use Layout Builder, per-visitor engagement tracking in the `ez_likes_events` table, admin analytics with sortable columns, content-type and title filters, per-node event detail popups, and one-click CSV export.

This module is different from existing Drupal engagement modules since it requires no contributed dependencies beyond Drupal core and never destroys data on uninstall—tables are renamed to a preserved backup and automatically restored on reinstall. It provides per-path inclusion and exclusion rules with wildcard support, a configurable button color with automatic dark, tint, and shadow variants, and full accessibility with `aria-label` and `aria-live` regions on all interactive elements.

Recent security updates:
- Implemented strict path-based visibility rules with exclusion rules taking highest priority.
- Added robust validation for configuration fields (enabled content types, included/excluded pages, button color).
- Ensured all interactive elements use proper ARIA attributes and live regions for accessibility.
- Prevented direct database access by using Drupal’s database API with parameterized queries.
- Restricted analytics report access via the `access ez likes report` permission.
- Sanitized node titles and paths before rendering in admin reports and CSV exports.
- Avoided logging of raw URLs or paths that could expose sensitive content structures.
- Updated Composer constraints for Drupal 9, 10, and 11 compatibility.
- Verified PHP syntax, Composer metadata, and whitespace checks.

Project link

[https://www.drupal.org/project/ez_likes](https://www.drupal.org/project/ez_likes)

Comments

aman.kumar2 created an issue. See original summary.

vishal.kadam’s picture

vishal.kadam
Location Mumbai
commented
Issue summary: View changes
Status: Needs review » Closed (duplicate)
Related issues: +#3615162: [3.0.x] SearchUnify Drupal Connector

It appears there are multiple project applications created using your account.

Since a successful completion of the project application process results in the applicant being granted the necessary role to be able to opt projects into security advisory coverage, there is no need to take multiple applications through the process. Once the first application has been successfully approved, the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers, which in turn results in longer wait times for everyone in the queue.

With this in mind, your secondary applications have been marked as Closed (duplicate), with only one application left open. If, in the existing application you were asked to apply with a different project, please edit the issue summary of that application to change the project description and the project link.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.