Restore confirmation modal texts are hardcoded, not customizable

[Krzyzu84]

Describe the Bug

In the restore confirmation modal shown when restoring a version, the title, message, and button texts are hardcoded inside PayloadCMS and cannot be customized or localized through Payload Config or translation files.
This results in awkward or unclear messages for end users, especially in non-English locales.

Link to the code that reproduces this issue

This happens inside PayloadCMS core and we cannot provide a public reproduction repository as our project is private. However, the issue can be reproduced using the default admin with Polish (pl) i18n enabled.

Reproduction Steps

1. Log in as an admin.
2. Go to a page with at least two versions.
3. Open the versions list.
4. Select any version.
5. Click “Restore this version”.
6. Observe the confirmation modal.

Expected behavior:

• Title of the modal: “Confirm change”
• Message: “Restore page version from [date]” (with 24h format)
• Confirm button: “Change”
• These should be customizable via translation keys or config.

Actual behavior:

• Title: “Confirm restoring version”
• Message: “You are about to restore the global record [label] to the state it was in on May 26 2025, 4:14 PM.”
• Confirm button: “Confirm”
• These strings are not accessible for translation or override.

Which area(s) are affected? (Select all that apply)

Not sure

Environment Info

PayloadCMS version: v3.28.0

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload