Voting starts in March for the Drupal Association Board election.
The submitted string contains disallowed HTML: Torna alla home page.
This is due to the token "[site:url]". The following translation works, for instance:
This string has been translated on the translation server, though: http://localize.drupal.org/translate/languages/de/translate?sid=435083
What else can we do here? We can't translate the string alone, what if you want to return to somewhere other than the front page?
Maybe this is something to bring up with core, since the [variable:name] syntax is so common for tokens. Perhaps this could be allowed to pass the filter test.
Thanks for the heads up about the string already being translated. This will probably work for me, but some people may want to have a different translation of the same text, and won't be able to easily do the translation.
Already noted against core, Drupal Commerce suffers from the same problem, with no solution yet
#1292140: Can't translate completion message due to tokens in t() string.#1196488: Allow checkout completion message to be translated
Marked #1734690: Can't translate "<a href="[uc_order:url]">view your current order status</a>" as duplicate, although that's a slightly different string - we should deal with all strings containing tokens here.
Fixed the typo in the title.
Wow since april 2012! Nice that at least the typo in the title was corrected.
@ñull: What's your point? We don't need your snide remarks. If you don't have anything to contribute please refrain from posting.
If you'd actually taken the time to read the above thread, you'd know this is a CORE DRUPAL issue - t() can't translate strings with tokens. @longwave gave the link to the core issue in #3, which I'll repeat here: #1292140: Can't translate completion message due to tokens in t() string.. If you want to see this fixed, contribute to that issue in the core Drupal issue queue. Try out the patch, give your feedback, maybe even work on the code yourself, etc.
This issue is left "postponed" here in the Ubercart issue queue solely as a tracking issue so that people can find the core issue and help out in the core issue queue - there is nothing that is going to be changed in Ubercart to correct the core problem.
If you want a work around, just enter a completion message that doesn't include a token - no one is making you use the default continue shopping message. That was made configurable for a reason ...
@ñull: What's your point? We don't need your snide remarks.
I understand your frustration with my remarks. The point is that I hit against this issue already for years, without having too much to time to dig deeper. The other point is that nobody is perfect and in the end I apparently reached that point that the "snide remark" just came out.
I took your advice, tested the last patch.
Drupal is a registered trademark of Dries Buytaert.