Repository navigation
fix: point the docs links to the current Hyve docs pages with UTMs - #306
Merged
Merged
Conversation
The "Docs" link (header bar and dashboard help card) and the Qdrant "Learn more" link used old HelpScout URLs (/article/2009-…, /article/2066-…). They redirect to the Hyve docs, but the redirect drops the query string, and the links had no UTM parameters anyway. Both now point at the current docs pages through tsdk_utmify(). Part of Codeinwp/docs-site#1596. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pirate-bot
requested changes
Nov 9, 2026
Contributor
There was a problem hiding this comment.
🟡 Changes requested
The dashboard docs links now open the current pages with UTMs, but the readme's ThemeIsle links still lack UTM parameters.
readme.txt:25—correctnessThe fix tags the two dashboard docs links, but the readme's ThemeIsle links still carry no UTM parameters.readme.txt:25links[Documentation](https://docs.themeisle.com/hyve/)without attribution. The Terms, Privacy, FTP and Security links atreadme.txt:144,readme.txt:178andreadme.txt:208are also untagged. Docs visits from the plugin listing and the plugin details screen therefore stay unattributed, which is the problem this PR fixes. Add UTM parameters to each of these links. Use the same scheme as the readme's Pro links, which already carryutm_source,utm_mediumandutm_campaign(for example onreadme.txt:25).
Validation details
- Files reviewed: 3/3 changed files.
- The Hyve admin page loaded as admin with HTTP 200 and no fatal error on PHP 8.3.36
cd /workspace/checks/R1 && curl -s -b jar.txt -c jar.txt -o dash.html -w '%{http_code}\n' 'http://localhost:8080/wp-admi…(run R7, exit 0). - The localized
hyvedata held the new URLs, for examplecd /workspace/checks/R1 && python3 - <<'EOF' import re,html s=open('dash.html').read() m=re.search(r'var hyve = (\{.*?\}…printedutm_source=wpadmin&utm_medium=dashboard&utm_campaign=documentation(run R9). Both values match the new test assertions. tsdk_utmify()comes from the Composer-loaded SDK before the data filter runs.
Untested areas
- The Playwright tests did not run at HEAD or at
pr-base. They neednpm ci, a built bundle andwp-env.
🤖 Automated review · run code-review-agent_6af1c92733e642.17089338.
🤖 Review agent — review posted ✅ on 2c05fc80 · changes requested · 1 finding · 10 min
Run code-review-agent_6af1c92733e642.17089338 · trail
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
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
The dashboard's two docs links use old HelpScout URLs on docs.themeisle.com. They still redirect to the Hyve docs, but the redirect drops the query string, and the links sent no UTM parameters anyway, so docs visits from the plugin aren't attributed in analytics. This is part of Codeinwp/docs-site#1596 (reviewing docs links in all products).
This PR (
inc/Main.php, thehyvescript data):/article/2009-hyve-documentationtsdk_utmify( 'https://docs.themeisle.com/hyve/hyve-documentation', 'documentation', 'dashboard' )/article/2066-integrate-hyve-with-qdranttsdk_utmify( 'https://docs.themeisle.com/hyve/integrate-hyve-with-qdrant', 'qdrant', 'settings' )The Docs link now opens
https://docs.themeisle.com/hyve/hyve-documentation?utm_source=wpadmin&utm_medium=dashboard&utm_campaign=documentation&utm_content=docshyvehyve-documentation.The record of current vs new parameters for every product is in the docs-links report: https://claude.ai/artifact/TFrbebxm6kHNpJfb7GfzR2
Testing
dashboard.spec.js(app shell test) checks the header's Docs href, andsettings.spec.js(Qdrant form test) checks the "Learn more about Qdrant" href. Both pass with the fix and fail on the old code (they receive the/article/…URLs). The full Dashboard and Settings specs pass (22 tests).composer lint(phpcs oninc/Main.php),composer phpstanand ESLint pass.🤖 Generated with Claude Code