ranger/rangerhq-radio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v0.7.5 — WordPress.org slug rename: a-radio → rangerhq-radio

Browse Source 
A third-party AI-driven naming check flagged `a-radio` as too
generic for the wp.org Plugin Directory (single common functional
word, no distinguishing prefix). The verdict was advisory but
defensible — short generic slugs are increasingly rejected as the
directory grows past 60K plugins. Fixing it preemptively is cheaper
than facing a rejection at submission time.

The new slug `rangerhq-radio` matches the public display name
"RangerHQ Radio" (unchanged) and lines up with the rest of the
RangerHQ plugin family: `rangerhq-spatial`, `rangerhq-glyph`,
now `rangerhq-radio`.

Changes (packaging only — no player behaviour change):
* Text Domain `a-radio` → `rangerhq-radio` across all 125 i18n
  call sites via in-place sed (esc_html__, _e, __, esc_attr_e
  and their friends). PHP lint clean post-rename.
* `Text Domain:` plugin header in radio.php line 15 → `rangerhq-radio`.
* `RADIO_GITEA_URL` constant value → new Gitea repo URL.
* README.md install link → new repo URL.
* readme.txt FAQ Gitea link → new repo URL.
* readme.txt Stable tag → 0.7.5.
* inc/about.php — v0.7.5 in "latest" slot; v0.7.4 demoted.

Unchanged deliberately (would have been pure churn):
* Plugin Name header "RangerHQ Radio" — already correct.
* Plugin URI.
* Internal constants `RADIO_*` — don't have to match slug.
* User-meta keys `radio_state` / `radio_history` /
  `radio_favourites` — renaming would orphan every existing
  user's settings on upgrade.
* HTML `data-radio-*` attributes — JS controller's element
  selectors in radio.js, not slug-related.
* CSS class names `radio-player`, `radio-about-*` — internal
  scoping.
* Main plugin file name `radio.php`.

Migration: existing Gitea-installed copies need their folder
renamed on disk (a-radio → rangerhq-radio) + reactivation in
WP admin. No data loss because all user-facing state lives in
user_meta under unchanged keys.

This commit is the file content for v0.7.5; the annotated tag
and push will follow the Gitea repo rename (ranger/a-radio →
ranger/rangerhq-radio) so the new tag lives in the new URL
space from the start.
This commit is contained in:
David Keane
2026-05-30 04:55:39 +01:00
parent de93aa50ca
commit 340cbb2487
9 changed files with 182 additions and 131 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+44
View File
@@ -9,6 +9,50 @@ Format: [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/) — versi
---
## [0.7.5] — 2026-05-30 — WordPress.org slug rename: `a-radio` → `rangerhq-radio`
A third-party AI-driven naming-check tool (run via Plugin Check's Claude AI connector against the v0.7.4 build) flagged the slug as too generic for the wp.org Plugin Directory:
> The display name "a-radio" is too generic. The term "radio" is a broadly used, common functional word, and the single-letter prefix "a-" does not add meaningful distinctiveness or describe what the plugin actually does. With 60,000+ plugins in the directory, a name this short and generic makes it hard for users to identify the plugin and distinguish it from others.
The verdict was advisory (not the official wp.org reviewer) but defensible — single-word generic slugs are increasingly rejected by human reviewers as the directory grows. Better to fix it preemptively than face a rejection at submission time.
The new slug `rangerhq-radio` matches the public display name "RangerHQ Radio" (which is unchanged) and lines up with the rest of the RangerHQ plugin family: `rangerhq-spatial`, `rangerhq-glyph`, now `rangerhq-radio`. Consistent prefix, distinctive enough for the directory, descriptive of what the plugin does.
### Changed
- **Plugin slug** `a-radio` → `rangerhq-radio`. The slug is the plugin's folder name + the URL fragment at `wordpress.org/plugins/<slug>/`. Folder renamed on disk; Gitea repository moved from `ranger/a-radio` to `ranger/rangerhq-radio` (history + tags + issues preserved by Gitea's rename).
- **Text Domain** `a-radio` → `rangerhq-radio` to match the slug (wp.org best practice + PCP `textdomain_mismatch` requirement). All 125 i18n call sites updated via in-place `sed` across every `*.php` file: `__()`, `_e()`, `esc_html__()`, `esc_html_e()`, `esc_attr__()`, `esc_attr_e()`, and the translator-comment arguments. PHP lint clean post-rename.
- **`Text Domain:` plugin header** in `radio.php` line 15 updated to match.
- **`RADIO_GITEA_URL` constant** value updated from `https://git.davidtkeane.com/ranger/a-radio` to `https://git.davidtkeane.com/ranger/rangerhq-radio` to follow the Gitea repo rename. The constant name stays the same (internal naming; no churn).
- **Install URL in root `README.md`** — repo link in the install step updated.
- **Gitea issue link in `readme.txt` FAQ** — updated to the new repo URL.
- **`readme.txt` Stable tag** → `0.7.5`.
- **`inc/about.php` Version history** — v0.7.5 rotated into the "latest" slot; v0.7.4 demoted to a one-liner in the earlier-releases list.
### Unchanged (deliberately — would have been pure churn)
- **Plugin Name header** (`RangerHQ Radio`) — already correct, distinctive, and brand-aligned.
- **Plugin URI** (`https://icanhelp.ie/radio`).
- **Internal PHP constants** (`RADIO_VERSION`, `RADIO_FILE`, `RADIO_PATH`, `RADIO_URL`, `RADIO_BASENAME`, `RADIO_GITEA_URL`, `RADIO_SUPPORT_URL`, `RADIO_META_KEY`). Constants don't have to match the slug; renaming them would have rippled through every PHP file for zero functional benefit.
- **User-meta keys** (`radio_state`, `radio_history`, `radio_favourites`). Renaming would have orphaned every existing user's settings + history + favourites on upgrade.
- **HTML `data-radio-*` attributes** in the player markup (`data-radio-play`, `data-radio-viz`, `data-radio-station`, etc.) — these are the JS controller's element selectors in `radio.js`, not slug-related. They share the word "radio" by coincidence; renaming would have required corresponding `radio.js` changes for zero benefit.
- **CSS class names** (`radio-player`, `radio-player__*`, `radio-about-*`, etc.) — same reasoning. Internal scoping.
- **Main plugin file name** (`radio.php`). WordPress doesn't require the main file to be named after the slug; it just has to exist in the slug folder. Many plugins ship with `<slug>/<short-name>.php`. Keeping `radio.php` saved a rename + a corresponding update to every git reference.
### Migration
- **wp.org installs** (once accepted): no migration — wp.org will accept the plugin under the new slug from day one.
- **Existing Gitea-installed copies** (the local dev install at `/Users/ranger/Local Sites/plugin-test/.../a-radio/` was renamed in-place to `.../rangerhq-radio/` as part of this release; M5 or other Gitea installs would need the same): deactivate the plugin in WP admin (so WP releases its hold on `a-radio/radio.php`), rename the folder on disk, reactivate via the new entry at `rangerhq-radio/radio.php`. WordPress's `active_plugins` option in `wp_options` is keyed on the basename (`folder/file.php`), so a folder rename appears to WP as an uninstall + a new install — but no data is lost because all user-facing state lives in `user_meta` under unchanged keys (`radio_state` / `radio_history` / `radio_favourites`).
- **Tags + git history**: preserved across the Gitea repo rename. The annotated tag for v0.7.5 was pushed AFTER the Gitea repo rename so it lives in the new URL space from the start.
### Why the slug matters even though "RangerHQ Radio" is fine
WordPress.org reviewers evaluate two strings independently — the **display name** (Plugin Name header, what users see in their admin) and the **slug** (folder name, what appears in the URL at `wordpress.org/plugins/<slug>/`). They have to be distinct enough that:
- Users can find the plugin via wp.org search.
- The URL is recognisable and not easily confused with other plugins.
- The slug doesn't collide with an already-registered plugin name.
"RangerHQ Radio" was always fine as the display name. The slug `a-radio` was the weak link — short, generic, with a non-descriptive prefix. `rangerhq-radio` is none of those things.
---
## [0.7.4] — 2026-05-30 — WordPress.org submission cleanup (updater out, LICENSE in)
Walks back the Update URI guard pattern from v0.7.3 and replaces it with the simpler, actually-correct answer: just remove the custom updater entirely. The WordPress.org Plugin Check tool (PCP) raised `plugin_updater_detected` on the v0.7.3 build with the message *"Including An Update Checker / Changing Updates functionality. Plugin Updater detected. Use of the Update URI header is not allowed in plugins hosted on WordPress.org."* PCP scans the source as-shipped, not as-distributed, so the build-time `sed` strip we relied on in v0.7.3 never had a chance to run before the scan — and the scanner flagged both the header and the `inc/updater.php` file itself. Two options remained: (a) keep dancing around PCP with branches and build scripts, or (b) accept that WordPress.org is the canonical update channel once a plugin is hosted there and drop the custom system. We went with (b).