dolibarr-bugtrack
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dolibarr-bugtrack] [Bug #938] Number invoice lost in stock movements


From: Doliforge
Subject: [Dolibarr-bugtrack] [Bug #938] Number invoice lost in stock movements
Date: Tue, 06 Aug 2013 10:30:48 +0200

Doliforge
Is this email not displaying correctly?
update email preferences.

Number invoice lost in stock movements

Latest modifications

2013-08-06 10:30 (Europe/Paris)
Changes:
  • Status: 
OpenClosed

Answer now

Snapshot

 Details
Submitted on:  2013-06-12 12:14 Last Modified On:  2013-08-06 10:28
Submitted by:  Arnaud Lemonnier (sunchyny) 
Summary:  Number invoice lost in stock movements
Description:  When a chinese user validate a invoice, the invoice number are lost!
In Products -> Stock -> Movements, you can see
发票%s的验证 -> Facture %s validé (%s ; invoice number)

With a french user -> no problem
With a english user -> no problem

Dolibarr 3.2.3 -> same problem
Dolibarr 3.3.2 -> same problem

Forum francophone:
http://www.dolibarr.fr/forum/527-bugs-sur-la-version-stable-courante/41416-liste-mouvements-de-stock-pb-utilisateur-chinois
Step to reproduce bug:  When a chinese user
Create a facture
Validate it
Go to Products -> Stock -> Movements
Version:  3.3.1 Category:  Module: Customer Invoices
Severity:  5 - Major OS Type/Version:  WIN XP Pro 2002 sp2
PHP version:  PHP/5.3.0 Database type and version:  MySQL5.0.45-community-nt
 Status
Status:  Closed Assigned to:  None
Resolution:  Fixed 

Comments

Laurent Destailleur 2013-08-06 10:28
The bug should be fixed into last stable version.
You can download last stable version onto
http://www.dolibarr.org/downloads/
HENRY Florian 2013-06-19 14:33
Solution trouvée !

Les caractères "%" dans le fichier langue zn_CN ne sont pas les mêmes que dans le fichier langue Fr (code ASCII différent)

==> Il faut donc tous les modifier

Merci de clôturer l'anomalie dans Doliforge (N° 938)
Arnaud Lemonnier 2013-06-15 18:04
This bug record has been closed because it was waiting for more
information or answers from submitter for a too long time.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]