WordPress.org

Make WordPress Core

Opened 3 months ago

Last modified 3 months ago

#54390 new enhancement

Privacy Policy should be generated on the site language (locale) and not on users language

Reported by: oglekler Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Privacy Keywords: has-privacy-review 2nd-opinion
Focuses: administration Cc:

Description

If the user chose another language for admin and generated the Privacy Policy page, it was created in its chosen language and not in the site's language (locale).

Example: While managing site with German language and English language as personal preference, I've got English Privacy Policy page and not Datenschutzerklärung as I've exected.

It can be even better to give a user option to change the default (site's language) to another available one as an added feature.

Change History (4)

#1 @SergeyBiryukov
3 months ago

  • Component changed from General to Privacy
  • Focuses administration added

#2 @paapst
3 months ago

  • Keywords has-privacy-review 2nd-opinion added
  • Type changed from defect (bug) to enhancement

The privacy statement is usually being generated by someone who should at least understand the legal text and the consequences of that text. So if the language of preference is English, presumably because the admin understands that language best, the Privacy Statement is also being generated in that language. That is intended behaviour. Of course, you can always temporarily change the language of your profile to the locale in which you want to generate the Privacy Statement.

This ticket was mentioned in Slack in #core-privacy by paapst. View the logs.


3 months ago

#4 @oglekler
3 months ago

@paapst This is inconvenient behaviour. For example, I am managing the site for someone else and the client definitely needs the Privacy Policy on the site's language. Btw, my native language is Russian, but I am not using it in the admin preferring all interfaces in English for consistency (and because of the Block Editor which is not searching in English when used in another language), so, this logic you are referring to is not working.

Note: See TracTickets for help on using tickets.