dolibarr-bugtrack
[Top][All Lists]
Advanced

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

[Dolibarr-bugtrack] [Bug #1578] Cannot create proposal by copy of anothe


From: Doliforge
Subject: [Dolibarr-bugtrack] [Bug #1578] Cannot create proposal by copy of another one
Date: Sun, 16 Nov 2014 16:42:48 +0100

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

Cannot create proposal by copy of another one

Latest modifications

2014-11-16 16:42 (Europe/Paris)
Bug can't be reproduced on last develop version or may be
obsolete because of changes, so we suppose it was silently fixed.
Because of this, we close the request.
Changes:
  • Status: 
OpenClosed
  • Assigned to: 
NoneLaurent Destailleur (eldy)
  • Resolution: 
NoneFixed

Answer now

Snapshot

 Details
Submitted by:  Francois Couque (fcouque) Submitted on:  2014-08-23 13:02
Last Modified On:  2014-08-23 13:02 
Summary:  Cannot create proposal by copy of another one
Description:  When creating the draft of a proposal by copy an old one, we get a fatal error message:
La référence utilisée pour la création existe déjà

I've "fixed" it quickly by moving the create fonction in the else part where it should probably be. Currently, in this workflow, there is a first $object->create_from($user); then $object->create($user);
The second one failed because the ref has been already created.
Step to reproduce bug:  1 Choose a customer
2 Go to proposal tab
3 Click create proposal button
4 Select "Créer proposition/devis par recopie d'un proposition existant" and an old proposal.
5 Click "create draft button"
Detected in version:  3.6.0 Category:  Module: Proposals
Severity:  5 - Major OS Type/Version:  Debian Linux 2.6.32
PHP version:  5.3.8 Database type and version:  Mysql 5.1.39
 Status
Status:  Closed Assigned to:  Laurent Destailleur (eldy)
Resolution:  Fixed 

Comments

Laurent Destailleur 2014-11-16 16:42
Bug can't be reproduced on last develop version or may be
obsolete because of changes, so we suppose it was silently fixed.
Because of this, we close the request.


reply via email to

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