Content Like Adds AJAX Like Feature for Drupal Content

The contributed module Content Like 1.0.0 adds an AJAX-based like and unlike feature for Drupal content. Harish Kumar announced the release in a LinkedIn post, with Hapus Infotech identified as the supporting organisation. Drupal.org lists version 1.0.0 as the initial stable release, created on 23 June 2026 at 09:58 UTC.

The release gives site builders a configurable content engagement widget rather than requiring a custom like counter. It supports selected node bundles and custom block bundles, so administrators can decide where the like widget appears. The module also uses lazy builder rendering to reduce cache-related liked-state issues.

Content Like supports both authenticated users and anonymous visitors. For logged-in users, it stores the Drupal user ID with the liked entity. For anonymous visitors, it creates a browser cookie named content_like_anon_id and stores a hash of the anonymous ID rather than the raw cookie value in the database.

Duplicate-like prevention is handled through a custom database table with a unique key across entity type, entity ID, liker type, and liker ID. The design prevents the same authenticated user or anonymous cookie visitor from repeatedly liking the same content. That structure makes duplicate prevention part of the module’s storage model, not only its front-end behaviour.

The module provides an administration page at /admin/config/content/content-like. From that page, administrators can select which content types and custom block types should have the like feature enabled. Checked bundles display the widget when rendered, while unchecked bundles do not.

Theme support is included through default Drupal Twig templates and custom Twig templates. Sites that print the standard render array can display the widget through {{ content }}. Themes that print fields manually can output the widget by checking content.content_like and printing {{ content.content_like }} when available.

Drupal.org lists the 1.0.0 release as compatible with Drupal 10, 11, and 12. The module requires the Node and Block Content modules and provides the Administer content like settings permission for users who should manage where the feature appears. The 1.0.0 release page lists the Composer command composer require 'drupal/content_like:^1.0'.

In the LinkedIn announcement, Harish said the release helped him work through the Drupal contributed project workflow, including project setup, Git repository management, tagging, and publishing a stable release. The post frames the release as both a module contribution and a contributor milestone. Further development plans were not specified.

Drupal.org marks Content Like as not covered by Drupal's security advisory policy. The notice states that the project may have publicly disclosed vulnerabilities. The advisory status leaves risk assessment to site maintainers before production use.