You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When new order is created, it looks like OpenCart saves title strings for the following entities in DB for each order:
shipping method
payment method
product name
total modules
That means that if user ordered something while using language A, these strings are saved using this language. If user then switches to language B and goes to view Order Details, she will see strings from language A.
Is there a particular reason why OpenCart saves these strings? I can only think that so not to do few extra joins to get the proper values from relevant tables, but I don't think its worth it and it affects user experience negatively.
The text was updated successfully, but these errors were encountered:
andreihq
changed the title
Localisation in Order Information Page is broken (v 2.0.3.1)
Localisation in Order Information page is broken (v 2.0.3.1)
Oct 29, 2015
Further investigation showed that actually there is no way to get strings for payment, shipping and total modules without actually requesting the module or using them.
Payment Modules have only method getMethod()
Shipping Modules have only method getQuote()
Order Total Modules have only method getTotal()
I think these modules should have another method, like getInfo() that returns common information about the module, i.e. its title using current session language.
When new order is created, it looks like OpenCart saves title strings for the following entities in DB for each order:
That means that if user ordered something while using language A, these strings are saved using this language. If user then switches to language B and goes to view Order Details, she will see strings from language A.
Is there a particular reason why OpenCart saves these strings? I can only think that so not to do few extra joins to get the proper values from relevant tables, but I don't think its worth it and it affects user experience negatively.
The text was updated successfully, but these errors were encountered: