WordPress / WordPress/plugin-check

Plugin Namer tool doesn't detect exact/near-exact existing plugin names in the directory

Open
#1,386 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Team] Plugins Checks Good First Issue
Dominant language
PHP
Stars
362
Forks
126
Avg merge
1d 23h
Merged PRs (30d)
22

Description

Tested name: "LessFlux Image & Video Optimizer – WebP, AVIF, CDN & Lazy Load"

This is an already-published plugin on wordpress.org live.

Expected: Namer tool flags it as an existing plugin / slug conflict.

Actual: Verdict "Generally Allowable." Only flagged "LessFlux" as a trademark term, suggested slug lessflux-image-video-optimizer (unaware less-flux already exists).

Kindly refer below screenshot:-

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report in the Plugin Namer tool with the exact published plugin name and inspect the existing-name and slug-conflict detection entry points. Done means the tool flags the existing WordPress.org plugin and recognizes the corresponding slug conflict instead of returning “Generally Allowable.”

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.