docs: Add PHP Error Tracking installation page#16197
Merged
Conversation
Contributor
|
Hey ! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.
|
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 0 errors, 23 warnings, 0 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 3:15 | warning | Use 'PHP' instead of 'php'. | Vale.Terms |
| 152:53 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 154:59 | warning | 'Throwable' is a possible misspelling. | PostHogBase.Spelling |
contents/docs/libraries/php/index.mdx — 0 errors, 20 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 6:18 | warning | Use 'GitHub' instead of 'github'. | Vale.Terms |
| 6:37 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 6:45 | warning | Use 'PHP' instead of 'php'. | Vale.Terms |
| 86:4 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'Feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 86:4 | warning | 'Feature flags' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 106:8 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 106:51 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 106:124 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 116:28 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 116:54 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 120:122 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 120:130 | warning | Use 'PHP' instead of 'php'. | Vale.Terms |
| 146:4 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'Error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 146:4 | warning | 'Error tracking' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 148:73 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 166:115 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 192:110 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 194:276 | warning | Use 'PHP' instead of 'php'. | Vale.Terms |
| 195:78 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 196:87 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
b129778 to
9c03f90
Compare
9c03f90 to
f0ffc6b
Compare
cat-ph
approved these changes
Apr 7, 2026
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
Adds PHP to the Error Tracking installation documentation.
Changes
contents/docs/error-tracking/installation/php.mdxwith step-by-step installation instructionssrc/navs/index.jsDetails
This PR adds error tracking documentation for the PHP SDK, following the feature introduced in PostHog/posthog-php#109.
Key points covered:
PostHog::captureException()The page follows the same pattern as the Go and Elixir installation pages (inline steps using the
<Steps>component) since PHP uses manual exception capture rather than automatic capture.Since the installation platforms grid uses
usePlatformListto dynamically generate from MDX files withplatformLogofrontmatter, PHP will automatically appear in the installation grid at/docs/error-tracking/installation.This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.
Note: Since I cannot access the posthog-php repository directly to verify exact API signatures, please review the
captureException()method signature to ensure it matches the actual implementation.