LibreSign / LibreSign/libresign
When browser is in French language, requesting a code doesn't work.
@vitormattos is already working on this.
Since May 7, 2025.
- Dominant language
- PHP
- Stars
- 818
- Forks
- 146
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 326
Description
Describe the bug
When browser is in French language, requesting a code doesn't work.
I test it also with English, German and Italian, works well.
To Reproduce
Steps to reproduce the behaviour :
Requirements :
- First, request a signature with email address.
- Set your browser language in French
Step :
- I'm not an authenticated user
- Click on the button of the email received to sign a document
- Click on "Définissez votre signature."
- Draw signature
- Click on "Sauvegarder"
- Click on "Sauvegarder"
- Click on "Signer le document"
- Enter the email
- Click on "Demander un code".
The notification displayed is : "La requête de signature du fichier à été correctement soumise."
Which mean "The file signature request has been correctly submitted."
No code is received by email.
Expected behavior
The message of the notification should be "The code to sign file was successfully requested." in french "Le code pour signer le fichier a été demandé avec succès."
Environment information (please complete the following information):
- OS: Client: Linux ; Server: Podman containers Nexcloud AIO
- Browser : Tested with Firefox and Ungoogled-chromium both in French language
- LibreSign Version 10.7.2
- Nextcloud Server Version 30.0.8
- Logs :
Request with English language
Request :
curl 'https://--removed--.org/ocs/v2.php/apps/libresign/api/v1/sign/uuid/0ea4af05-efda-4555-8783/code' \
-H 'accept: application/json, text/plain, */*' \
-H 'accept-language: en-US,en;q=0.9,fr-FR;q=0.8,fr;q=0.7,en-GB;q=0.6' \
-H 'content-type: application/json' \
-b '__Host-nc_sameSiteCookielax=true; __Host-nc_sameSiteCookiestrict=true; oc_sessionPassphrase=--removed--; ocufnhdp8gk8=--removed--' \
-H 'dnt: 1' \
-H 'origin: https://--removed--.org' \
-H 'priority: u=1, i' \
-H 'requesttoken: --revoved--' \
-H 'sec-ch-ua: "Chromium";v="135", "Not-A.Brand";v="8"' \
-H 'sec-ch-ua-mobile: ?0' \
-H 'sec-ch-ua-platform: "Linux"' \
-H 'sec-fetch-dest: empty' \
-H 'sec-fetch-mode: cors' \
-H 'sec-fetch-site: same-origin' \
-H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36' \
-H 'x-requested-with: XMLHttpRequest, XMLHttpRequest' \
--data-raw '{"identify":"--removed--","identifyMethod":"email","signMethod":"emailToken"}'
Response :
{"ocs":{"meta":{"status":"ok","statuscode":200,"message":"OK"},"data":{"message":"The code to sign file was successfully requested."}}}
Request with French language
Request :
curl 'https://--removed--.org/ocs/v2.php/apps/libresign/api/v1/sign/uuid/0ea4af05-efda-4555-8783-7ec0d0f3e266/code' \
-H 'accept: application/json, text/plain, */*' \
-H 'accept-language: fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7,en-GB;q=0.6' \
-H 'content-type: application/json' \
-b '__Host-nc_sameSiteCookielax=true; __Host-nc_sameSiteCookiestrict=true; oc_sessionPassphrase=--removed--; ocufnhdp8gk8=--removed--' \
-H 'dnt: 1' \
-H 'origin: https://--removed--.org' \
-H 'priority: u=1, i' \
-H 'requesttoken: --removed--' \
-H 'sec-ch-ua: "Chromium";v="135", "Not-A.Brand";v="8"' \
-H 'sec-ch-ua-mobile: ?0' \
-H 'sec-ch-ua-platform: "Linux"' \
-H 'sec-fetch-dest: empty' \
-H 'sec-fetch-mode: cors' \
-H 'sec-fetch-site: same-origin' \
-H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36' \
-H 'x-requested-with: XMLHttpRequest, XMLHttpRequest' \
--data-raw '{"identify":"--removed--","identifyMethod":"email","signMethod":"emailToken"}'
Response :
{"ocs":{"meta":{"status":"ok","statuscode":200,"message":"OK"},"data":{"message":"La requ\u00eate de signature du fichier \u00e0 \u00e9t\u00e9 correctement soumise."}}}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.