I have created and using Magento translations. Translations are placed under app/locale/language_LANGUAGE.csv

After the installation I figured out that some parts of translations dont work. CSV is perfectly fine, I have translated ALL fields that I need, and I have double checked that.

For some fields I had to use inline translations so I searched phtml and php files and edited translations manually. Its a weird thing, because I now have ie some phtml files with 8 fields that are translated from CSV, and one field that is translated manually.

Had someone this problem before? Why does not some parts of translations work?


  • Have you tried to add the scope to your csv file? Like "Mage_Catalog::Special Price:","now:"
    – mnp
    Commented Apr 2, 2013 at 9:47
  • Yes, It doesnt work neither with that.. Commented Apr 2, 2013 at 10:57
  • Its pretty weird, I cannot find the reason. In example, I tried to translate the sentence "Coupon code is invalid" on the cart review page, and it just wont work.. Commented Apr 2, 2013 at 15:44

2 Answers 2


Magento have multiple translation scopes: Global, admin, theme & module. Depending on which block type (model) each template is defined by, the scope differs.

I'll would try adding your translation strings to your theme at: /app/design/frontend/yourpackage/yourtheme/locale/en_US/translate.csv

But it's better to know your scope, check which module/class $this is an instance of in each template, if it's not already defined in the template top comment block. Then you can add the translation strings to each modules own translation files or create them if they does not already exist.


In many cases "Special Price" is a magento attribute.

You can look it up in the magento admin catalog->attributes->manage attributes.

Look for special price, you can translate it there.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.