12.2: free launch — Module #1/#2 teaser copy + promo-code unlock - #2
Merged
Conversation
…in, bump Tested-up-to, fix stale GmbH author
Plugin Check flagged real issues: (1) load_plugin_textdomain() is discouraged
for wp.org-hosted plugins (auto-loaded translations, no manual call needed) —
removed along with the now-unused Domain Path header (no languages/ folder
exists). (2) readme.txt 'Tested up to: 6.6' was stale, bumped to 7.0 per the
check's own current-version signal. (3) 'Author: TetaPi GmbH' was a stale
reference the owner already asked removed from landing copy (10.2) — same
fix here, no legal entity to claim yet. (4) CI itself defaulted the expected
plugin slug to the GitHub repo directory name ('wordpress-plugin'), which
also trips the trademarked-term check ('plugin' is restricted in real wp.org
slugs) — pinned slug to 'tetapi' (matches Text Domain) and excluded
.github/CLAUDE.md from the check since neither ships in the real submission
zip (packaged separately in 12.3).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…-code unlock Owner decision 2026-07-14: launch 100% free, zero payment code. Reframes premium teaser copy in readme.txt + the settings page as "Module #1 ($25) / Module #2 ($52) — coming soon" (no donation wording). Adds a simple promo-unlock mechanic: Tetapi_Premium::is_licensed() flips true only if the site owner enters a code matching a SHA-256 hash in a hardcoded, owner-maintained list — no payment, no license-server call, gift-only. Also preps wp.org readiness: FAQ entries on pricing/unlock, Screenshots section placeholder. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Tetapi_Premium::is_licensed()flips true only when the site owner enters a code matching a SHA-256 hash in a hardcoded, owner-maintained list (includes/class-tetapi-premium.php). No payment, no license-server call — gift-only, local to that site. Default stays "always false" until a hash is added.== Screenshots ==section placeholder (actual images are 12.3, owner-executed).Note for the manager: docs/changelog location
This repo (
teta-pi/wordpress-plugin) no longer has its owndocs/— itsCLAUDE.mdsays canonical docs/roadmap/changelog now live inteta-pi/infra. I did not open a cross-repo changelog entry there since this session's scope iswordpress-plugin/only; flagging here so the manager can log it inteta-pi/infra/docs/changelog.mdif that's still the convention post-split.Heads-up: concurrent edits in this worktree
While working,
teta-pi.phpandincludes/class-tetapi-plugin.phpwere modified on disk by another process/session (droppedload_plugin_textdomain, bumpedTested up to, fixed stale "TetaPi GmbH" author) and landed in commit03b173con this same branch before I pushed. Those are not my changes — I left them as committed by that other session and only added my own commit on top. Worth confirming with whoever owns that CI-fix work that this branch is still what they expect.Test plan
php -lclean on all touched files (CI: Plugin Check workflow runs this)🤖 Generated with Claude Code