I'm editing this report to include a few dfferent issues:
- After the order is completed by the customer, the thank you message displays the "!site" token instead of its replacement:
"Thank you for shopping at !site. While logged in, you may continue shopping or click here to view your current order status and order history."
Also, the URL under "click here" points to /user/1/orders (the admin's order list, which obviously is inaccessible by other users).
- I realize that the string doesn't get translated, despite being present as a translation (which I guess means it used to get translated in the past).
- I also found out that a number of other strings in the transaction process don't get translated either. Any t() missing?
I'm using the latest Bazaar version.
Thanks,
Tony
[Super-edit:]
OK, I realize that a few strings are customizable by the admin, including the one I mentioned above. This causes a problem in a multilingual site, unless the admin is given the ability to specify each string in each of the enabled languages.
As it is, the string configuration page for Ãœbercart gives me (by default) strings in English, even when Italian is the language. If I leave them in English, they show up in English everywhere; if I change them to Italian, they will show up in Italian everywhere.
Providing textareas for every single language would make a huge mess, so why not wrap these strings in t()?
Or am I just missing something?
