After upgrading to VM 2.0.22b custom fields language overrides not working

Started by sokostas, August 30, 2013, 12:34:57 PM

Previous topic - Next topic

sokostas

Hello,

After upgrading to VM 2.0.22b custom fields language overrides not working. The language override ini files are correct on their place and the custom fields names relations are correct. I have attached you 2 screenshots before and after upgrade


Joomla 2.5.14
php 5.3.27
vm 2.0.22b

Thanks for your support,
Kostas

[attachment cleanup by admin]

balai

Hi Kostas

Go to your VM config and check the default language of your VM shop.
Then check the language for which the overrides has been done.

Maybe the default vm lang is changed and is not corresponding to the language for your which your overrides has been done

sokostas

Thanks for your reply balai,

The settings are as you say. I attached the files. I really can't find where the problem is.



[attachment cleanup by admin]

Maxim Pishnyak

You can support Community by voting for Project on the JED
https://extensions.joomla.org/extension/virtuemart/#reviews
Join us at
https://twitter.com/virtuemart

sokostas

I am working on a test enviroment. So i have attached you 2 files for language debugging mode, before and after upgrade. No parsing errors and no untranslated strings.

Thanks,
Kostas

[attachment cleanup by admin]

balai

Could you please set the English lang first and then the Greek in the vm config?

sokostas

I 've changed the language ordering several times with no result. By the way the ordering is always greek first. I think  is a matter of appearance.

Milbo

Your first two screenshots show the product in different language, therefore it is not really useable. Do you have set greece as the default joomla language?
Should I fix your bug, please support the VirtueMart project and become a member
______________________________________
Extensions approved by the core team: http://extensions.virtuemart.net/

sokostas

Greek is my default language in joomla settings as it was before the vm upgrade. Screenshot are just indicative. I have attached you a new one, in Greek, before upgrade.

[attachment cleanup by admin]

sokostas

Hello,

After upgrading vm to 2.0.24 problem is solved.

Regards,
Kostas