Prestashop: An answer to your message no. ct%thread_id is available (thread ID tcVZCv6tKE7zVG)

Created on 20 Aug 2019  路  4Comments  路  Source: PrestaShop/PrestaShop

Describe the bug
Weird email reply subejct

To Reproduce
Steps to reproduce the behavior:

  1. use contact form on shop
  2. reply to it via prestashop "Customer Service"
  3. receive weird email subject

I dont know if this is a bug or my error as first timer on prestashop.
So if i use contact form and send message to site and i reply to it via "Customer Service" from presta shop interface i get this error (?). email subject looks like this: "An answer to your message no. ct%thread_id is available (thread ID tcVZCv6tKE7zVG)"

1.7.5.2 1.7.6.0 Bug Customer service Email Fixed Minor

Most helpful comment

Dear @arouiadib, I've looked a bit into en-US files and the mistake is on the translation part, not the source string. I've just corrected it on the Crowdin translation project here, it should be effective in a couple of days. ;-)

All 4 comments

Hi @ArtiomkaPL,

Thanks for your report.
I manage to reproduce the issue with PS1.7.6.0 & PS1.7.5.2.
image
I鈥檒l add this to the debug roadmap so that it鈥檚 fixed. If you have already fixed it on your end or if you think you can do it, please do send us a pull request!
Thanks!

On Crowdin, I have this string, available for all catalogs (from 1.7.2 to 1.7.6):

Capture d鈥檈虂cran 2019-08-21 a虁 14 15 18

Here, it seems that the variables are not properly displayed... @jolelievre, any idea? If it is a bug, let's add it to the debug roadmap, thanks @khouloudbelguith. :-)

The default translation string is missing a % at the end of the variable. I can see it from International / Translation / Emails translations/ Subject in 1.7.5.0

It is (probably) coming from the translation file app/Resources/translations/en-US/EmailsSubject.en-US.xlf. But how can I edit this file? I don't find it in the repository.

Edit:
Both en-Us and en-GB xlf files have this mistake. But where are they in Github? I just find the 'default' in app/Resources/translations. Any help?

Dear @arouiadib, I've looked a bit into en-US files and the mistake is on the translation part, not the source string. I've just corrected it on the Crowdin translation project here, it should be effective in a couple of days. ;-)

Was this page helpful?
0 / 5 - 0 ratings