Skip to content

feat: clarify that permission settings apply across all locales#5486

Open
lupafubeep wants to merge 1 commit into
apostrophecms:mainfrom
lupafubeep:fix/permissions-locale-clarification
Open

feat: clarify that permission settings apply across all locales#5486
lupafubeep wants to merge 1 commit into
apostrophecms:mainfrom
lupafubeep:fix/permissions-locale-clarification

Conversation

@lupafubeep

Copy link
Copy Markdown

Please indicate which branch this PR should merge into:

Check one

  • main
  • latest
  • stable
  • Check if this PR will be resubmitted against another branch

Summary

Closes #3452

Added a notice banner in the AposPermissionGrid component to clearly inform users that permission settings apply across all locales and cannot be set independently per locale. Also added the corresponding i18n translation key permissionsApplyToAllLocales to the English translation file.

What are the specific steps to test this change?

  1. Run the website and log in as an admin
  2. Go to any page settings
  3. Click on the Permissions tab
  4. A notice banner will appear at the top informing the user that permission settings apply across all locales

What kind of change does this PR introduce?

  • Bug fix
  • New feature
  • Refactor
  • Documentation
  • Build-related changes
  • Other

Make sure the PR fulfills these requirements:

  • It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
  • The changelog is updated
  • Related documentation has been updated
  • Related tests have been updated

Other information:
This change improves UX by making it clear to users that page permission settings are global across all locales, addressing the confusion reported in issue #3452.

@boutell boutell left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are changes in this PR that don't seem relevant to the intended change.

Are you working on an ApostropheCMS project where this created user confusion?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants