Rename plugin to "Inline Glossary by Progress Planner" and reprefix to inline_glossary#55
Open
tacoverdo wants to merge 1 commit into
Open
Rename plugin to "Inline Glossary by Progress Planner" and reprefix to inline_glossary#55tacoverdo wants to merge 1 commit into
tacoverdo wants to merge 1 commit into
Conversation
…o inline_glossary
Prepares the plugin for its WordPress.org release by changing the slug and all
identifier prefixes, and updating the display name.
Identifier changes (all forms):
- Namespace/classes: PP_Glossary -> Inline_Glossary
- Constants: PP_GLOSSARY_ -> INLINE_GLOSSARY_
- Functions/CPT/meta/options/hooks/ids: pp_glossary -> inline_glossary
- Text domain, handles, CSS classes, block name, HTML ids: pp-glossary -> inline-glossary
- Main file renamed: pp-glossary.php -> inline-glossary.php
- Display name: "Glossary" -> "Inline Glossary by Progress Planner"
Deliberately left unchanged:
- The --glossary-* CSS custom properties (not part of the pp_glossary prefix).
- The CPT admin menu label ("Glossary").
- External URLs pointing at existing resources that a code change cannot rename:
the GitHub repo (progressplanner/pp-glossary), the two changelog issue links,
and the hosted blueprint import (research/pp-glossary.xml).
Verified: composer lint, composer phpstan, and composer check-cs all pass.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
@tacoverdo , do we want to migrate the data for the existing installs: #56 ? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the plugin for its WordPress.org release by changing the slug, all identifier prefixes, and the public display name.
Display name
Glossary→ Inline Glossary by Progress Planner (plugin header,readme.txttitle,README.md, phpcs project name).Identifier renames (all four casing/separator forms)
PP_GlossaryInline_Glossary@packagePP_GLOSSARY_INLINE_GLOSSARY_*_VERSION,*_PLUGIN_DIR,*_PLUGIN_URLpp_glossaryinline_glossary*_settings, meta_*_data, filters, field/nonce idspp-glossaryinline-glossaryinline-glossary/glossary-listMain file renamed:
pp-glossary.php→inline-glossary.php.Deliberately left unchanged
--glossary-*CSS custom properties — they use aglossaryprefix, notpp_glossary, so they're outside the scope of this rename and changing them is unnecessary.CPT admin menu label (
Glossary) — that's UI copy, not an identifier.External URLs that a code change can't actually rename, kept pointing at the real resources:
GitHub Plugin URI→github.com/progressplanner/pp-glossarygithub.com/ProgressPlanner/pp-glossary/issues/...progressplanner.com/research/pp-glossary.xmlIf/when the GitHub repo and that hosted XML are renamed, update these four references in a follow-up.
The post type (
inline_glossary), post meta key (_inline_glossary_data), and option (inline_glossary_settings) are stored in the database. Any existing install on the old identifiers will orphan its data on upgrade. This is fine for the pre-.org-release rebrand (no.orgusers yet), but any test/staging site with real entries needs a data migration before activating this build. No user-facing changelog entry was added since no version has shipped to.organd there's nothing for an end user to act on.Verification
composer lint,composer phpstan, andcomposer check-csall pass.🤖 Generated with Claude Code