Skip to content

Fix for record-comments CMA client targeting primary env instead of current.#140

Merged
marcelofinamorvieira merged 1 commit intomasterfrom
fix/environments
Apr 14, 2026
Merged

Fix for record-comments CMA client targeting primary env instead of current.#140
marcelofinamorvieira merged 1 commit intomasterfrom
fix/environments

Conversation

@roger-datocms
Copy link
Copy Markdown
Contributor

Fixes #139

Fix for record-comments CMA client targeting primary env instead of current.

buildClient() without an environment parameter defaults to the primary
environment. When the primary env is write-protected, plugin installation
in secondary environments fails because model creation targets the
locked primary. Pass ctx.environment to all buildClient call sites.

Also fix onBoot error notification using ctx.notice instead of ctx.alert.

…current environment

  buildClient() without an environment parameter defaults to the primary
  environment. When the primary env is write-protected, plugin installation
  in secondary environments fails because model creation targets the
  locked primary. Pass ctx.environment to all buildClient call sites.

  Also fix onBoot error notification using ctx.notice instead of ctx.alert.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Record Comments plugin has permissions issues

2 participants