Hi,
I found this bug, and it is very easy to reproduce:
1 - Install NOP 1.8 in a new database (I do the installation from vstudio development server, not an IIS virtual directory)
2 - Download Spanish language extension (https://www.nopcommerce.com/p/158/spanish-language-pack.aspx)
3 - Uncompress the file, we got an XML
4 - Login in NOP as administrator, go to Configuration -> Location -> Languages
5 - Click "Add new"
6 - Fill the form with this data:
Name: Espanol
Culture: es-ES (international)
Flag image file: es.png
Published: checked
Display order: 2
7 - Click "save"
8 - Import XML appears, choose the spanish xml file and click "Import"
9 - Import takes some time, but there are not visible errors or exceptions
10 - Click save. If you do so... I think it behaves like no XML file was imported (you see resource keys in labels, instead of its values)
I've discovered (after some reinstallations), that if I do not click at the "save" button it works...
1.8 - Install spanish language
MVP
Socio de Solución de Plata
- 5236
- 49495
- 4/10/2010
- Mexico
jboschSZD wrote:
We already installed it. The problem is that the XML file of the Spanish language extension has many errors.
Hi,
I found this bug, and it is very easy to reproduce:
1 - Install NOP 1.8 in a new database (I do the installation from vstudio development server, not an IIS virtual directory)
2 - Download Spanish language extension (https://www.nopcommerce.com/p/158/spanish-language-pack.aspx)
3 - Uncompress the file, we got an XML
4 - Login in NOP as administrator, go to Configuration -> Location -> Languages
5 - Click "Add new"
6 - Fill the form with this data:
Name: Espanol
Culture: es-ES (international)
Flag image file: es.png
Published: checked
Display order: 2
7 - Click "save"
8 - Import XML appears, choose the spanish xml file and click "Import"
9 - Import takes some time, but there are not visible errors or exceptions
10 - Click save. If you do so... I think it behaves like no XML file was imported (you see resource keys in labels, instead of its values)
I've discovered (after some reinstallations), that if I do not click at the "save" button it works...
I found this bug, and it is very easy to reproduce:
1 - Install NOP 1.8 in a new database (I do the installation from vstudio development server, not an IIS virtual directory)
2 - Download Spanish language extension (https://www.nopcommerce.com/p/158/spanish-language-pack.aspx)
3 - Uncompress the file, we got an XML
4 - Login in NOP as administrator, go to Configuration -> Location -> Languages
5 - Click "Add new"
6 - Fill the form with this data:
Name: Espanol
Culture: es-ES (international)
Flag image file: es.png
Published: checked
Display order: 2
7 - Click "save"
8 - Import XML appears, choose the spanish xml file and click "Import"
9 - Import takes some time, but there are not visible errors or exceptions
10 - Click save. If you do so... I think it behaves like no XML file was imported (you see resource keys in labels, instead of its values)
I've discovered (after some reinstallations), that if I do not click at the "save" button it works...
We already installed it. The problem is that the XML file of the Spanish language extension has many errors.
- 12
- 60
- 24/11/2010
- Spain
eadameg wrote:
If we know the problem exists, don't we could look for a solution? It is expensive or something?
Hi,
I found this bug, and it is very easy to reproduce:
1 - Install NOP 1.8 in a new database (I do the installation from vstudio development server, not an IIS virtual directory)
2 - Download Spanish language extension (https://www.nopcommerce.com/p/158/spanish-language-pack.aspx)
3 - Uncompress the file, we got an XML
4 - Login in NOP as administrator, go to Configuration -> Location -> Languages
5 - Click "Add new"
6 - Fill the form with this data:
Name: Espanol
Culture: es-ES (international)
Flag image file: es.png
Published: checked
Display order: 2
7 - Click "save"
8 - Import XML appears, choose the spanish xml file and click "Import"
9 - Import takes some time, but there are not visible errors or exceptions
10 - Click save. If you do so... I think it behaves like no XML file was imported (you see resource keys in labels, instead of its values)
I've discovered (after some reinstallations), that if I do not click at the "save" button it works...
We already installed it. The problem is that the XML file of the Spanish language extension has many errors.
I found this bug, and it is very easy to reproduce:
1 - Install NOP 1.8 in a new database (I do the installation from vstudio development server, not an IIS virtual directory)
2 - Download Spanish language extension (https://www.nopcommerce.com/p/158/spanish-language-pack.aspx)
3 - Uncompress the file, we got an XML
4 - Login in NOP as administrator, go to Configuration -> Location -> Languages
5 - Click "Add new"
6 - Fill the form with this data:
Name: Espanol
Culture: es-ES (international)
Flag image file: es.png
Published: checked
Display order: 2
7 - Click "save"
8 - Import XML appears, choose the spanish xml file and click "Import"
9 - Import takes some time, but there are not visible errors or exceptions
10 - Click save. If you do so... I think it behaves like no XML file was imported (you see resource keys in labels, instead of its values)
I've discovered (after some reinstallations), that if I do not click at the "save" button it works...
We already installed it. The problem is that the XML file of the Spanish language extension has many errors.
If we know the problem exists, don't we could look for a solution? It is expensive or something?
MVP
Socio de Solución de Plata
- 5236
- 49495
- 4/10/2010
- Mexico
jboschSZD wrote:
Hola:
Lo que te decía es que encontramos que el archivo XML extensión de la versión del Español para la version 1.80 viene con errores (esta corrompido). Eliminando a mano los errores se pudo cargar pero todavía tiene errores en algunos campos y en la traducción (parece que la hicieron con un traductor automático). Cuando lo tengamos corregidotratare enviartelo
Hi,
We already installed it. The problem is that the XML file of the Spanish language extension has many errors.
If we know the problem exists, don't we could look for a solution? It is expensive or something?
We already installed it. The problem is that the XML file of the Spanish language extension has many errors.
If we know the problem exists, don't we could look for a solution? It is expensive or something?
Hola:
Lo que te decía es que encontramos que el archivo XML extensión de la versión del Español para la version 1.80 viene con errores (esta corrompido). Eliminando a mano los errores se pudo cargar pero todavía tiene errores en algunos campos y en la traducción (parece que la hicieron con un traductor automático). Cuando lo tengamos corregidotratare enviartelo