Skip to content

Fixed #179 MU plugin path incorrect - #182

Merged
danielmorell merged 2 commits into
masterfrom
fixed/issue-179-must-use-plugin-path-incorrect
Sep 15, 2026
Merged

danielmorell merged 2 commits into
masterfrom
fixed/issue-179-must-use-plugin-path-incorrect

Conversation

@danielmorell

Copy link
Copy Markdown
Collaborator

Description of the change

This PR fixes #179 by correcting the path the Rollbar plugin. It also addresses a couple minor improvements for the MU plugin.

  • Added MU plugin ABSPATH security check.
  • Reduced verbose name.
  • Fixed WP env using project directory name for plugin name.

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • Maintenance

Related issues

Checklists

Development

  • Lint rules pass locally
  • The code changed/added as part of this pull request has been covered with tests
  • All tests related to the changed code pass in development

Code review

  • This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
  • "Ready for review" label attached to the PR and reviewers assigned
  • Issue from task tracker has a link to this pull request
  • Changes have been reviewed by at least one other engineer

- Added MU plugin ABSPATH security check
- Reduced verbose name
- Fixed WP env using project directory name for plugin name
@danielmorell danielmorell added this to the 3.2.1 milestone Sep 12, 2026
@danielmorell
danielmorell requested a review from brianr September 12, 2026 14:43
Comment thread mu-plugin/rollbar-mu-plugin.php
@danielmorell
danielmorell merged commit dc7a06c into master Sep 15, 2026
40 checks passed
@danielmorell
danielmorell deleted the fixed/issue-179-must-use-plugin-path-incorrect branch September 15, 2026 00:52
@danielmorell danielmorell modified the milestones: 3.2.1, 3.3.0 Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enable as a Must-Use plugin setting is no longer rendered in 3.2.0

3 participants