Hey there

Alright I made a grave mistake the other day and enabled the entity translation for Commerce order. Upon doing this I found two bugs...

* Commerce order total no longer works
* Could not revert the commerce order total translation (b/c it's always set to locked)

I ended up having to hack entity translation to get it to force the form to disable translation and I was back to happy land.

Just thought I would report this for people to know about and also if they run into the problem themselves.

Comments

rszrama’s picture

Category: bug » support
Status: Active » Postponed (maintainer needs more info)

How did you even enable Entity Translation for Commerce Orders? The entity info doesn't define any translation information like it does for Commerce Products.

shaneonabike’s picture

Well if you enable entity translation and field translation it allows individuals to translate fields (for labels and stuff like that). So when I looked at that field I was able to enable the actual translation for it (which was a bad idea in reflection)

Any way after that all hell broke loose. I think it partly has to due with the fact that commerce locks the field b/c you can't reverse the operation (unless you hack the entity module like I did).

rszrama’s picture

Curious - do you think we need a feature request in the translation module to prevent translation of locked fields or something?

shaneonabike’s picture

I would imagine b/c it actually exposes a whole that is super hard to get out of!

aschiwi’s picture

We have the same problem, just discovered it on an almost 2 year old multilingual commerce project. I'm pretty sure it wasn't like this in the beginning but "all of a sudden" we notice the totals block is only visible when logged in as user 1. We are still trying to hunt down what causes it but in the database it started to not save the total from a certain order id.

aschiwi’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Just had the time to re-read this thread. Comment #2 said "Well if you enable entity translation and field translation it allows individuals to translate fields (for labels and stuff like that). So when I looked at that field I was able to enable the actual translation for it (which was a bad idea in reflection)" - so it's clear to just disable translation for that field at admin/commerce/config/order/fields/commerce_order_total. You can still do this later, at least there haven't been any problems for us so far.

I will change the status of this ticket to won't fix and hope that leaving my solution here is enough.

bagqueen’s picture

Hi, I did the same thing and tried to translate the order total field. Not a good idea I soon discovered. Now I've just started using Drupal and Drupal Commerce so I don't really know how I would go about to try to hack entity translation to get back to normal. Any suggestions would be appreciated!