dolibarr-bugtrack
[Top][All Lists]
Advanced

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

[Dolibarr-bugtrack] [Bug #1216] new shipment and sgl syntax error, fk_el


From: Doliforge
Subject: [Dolibarr-bugtrack] [Bug #1216] new shipment and sgl syntax error, fk_element isn't string, integer or constant
Date: Mon, 20 Jan 2014 01:30:01 +0100

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

new shipment and sgl syntax error, fk_element isn't string, integer or constant

Latest modifications

2014-01-20 01:30 (Europe/Paris)
The bug has been corrected inside GIT sources
(http://www.github.com/Dolibarr/dolibarr).

So fix should be available with next stable release.
Changes:
  • Detected in version: 
3.4.13.4.2
  • Resolution: 
NoneFixed

Answer now

Snapshot

 Details
Submitted by:  Robert Krivic (robik) Submitted on:  2014-01-18 16:49
Last Modified On:  2014-01-18 16:49 
Summary:  new shipment and sgl syntax error, fk_element isn't string, integer or constant
Description:  trying to click new shipment in the shipment menu, my dolibarr broke, both test version, win stand alone and server side. I download version 3.4.2 for win and for web server.
Following SELECT a.id FROM llx_actioncomm as a WHERE a.entity = 1 AND a.fk_element = AND a.elementtype = 'shipping'; I think problem is a.fk_element = doesn' have any data, no string, no int or any const. In that case dolibarr broke. Because I am new at dolibarr, I think this is bug, why is fk_element without any data called.
Step to reproduce bug:  ver.3.4.2
click to new shipment in the menu shipment.
PS: I can create test user to see online dolibarr with this problem.
Detected in version:  3.4.2 Category:  Module: Shipments
Severity:  9 - Blocking - Critical OS Type/Version:  Linux
PHP version:  5.2.17 Database type and version:  MySQL 5.1.72-cll
 Status
Status:  Open Assigned to:  Laurent Destailleur (eldy)
Resolution:  Fixed 

Comments

Laurent Destailleur 2014-01-20 01:30
The bug has been corrected inside GIT sources
(http://www.github.com/Dolibarr/dolibarr).

So fix should be available with next stable release.


reply via email to

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