dolibarr-bugtrack
[Top][All Lists]
Advanced

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

[Dolibarr-bugtrack] [Bug #1471] Several PHP warnings when intercepting U


From: Doliforge
Subject: [Dolibarr-bugtrack] [Bug #1471] Several PHP warnings when intercepting USER_CREATE trigger
Date: Tue, 01 Jul 2014 12:41:31 +0200

Doliforge
Ce message ne s'affiche pas correctement?
mettez à jour vos préférences utilisateur.

Several PHP warnings when intercepting USER_CREATE trigger

Dernières modifications

01/07/2014 12:41 (Europe/Paris)
Like Laurent, I don't reach to reproduce that on 3.5.4
What is piece of code used for trigger failure ?
Changements :
  • Status: 
OpenNeed more info

Répondre

État

 Détails
Submitted by:  Marcos García (marcosgdf) Submitted on:  12/06/2014 07:12
Last Modified On:  01/07/2014 12:35 
Summary:  Several PHP warnings when intercepting USER_CREATE trigger
Description:  ( ! ) Warning: Illegal offset type in isset or empty in /var/www/htdocs/core/class/translate.class.php on line 393
Call Stack
# Time Memory Function Location
1 0.0021 257008 {main}( ) ../fiche.php:0
2 0.0923 1690872 Translate->trans( ) ../fiche.php:241

( ! ) Warning: preg_match() expects parameter 2 to be string, array given in /var/www/htdocs/core/class/translate.class.php on line 350
Call Stack
# Time Memory Function Location
1 0.0021 257008 {main}( ) ../fiche.php:0
2 0.0923 1690872 Translate->trans( ) ../fiche.php:241
3 0.0924 1691112 Translate->getTradFromKey( ) ../translate.class.php:427
4 0.0925 1691304 preg_match ( ) ../translate.class.php:350

( ! ) Warning: preg_match() expects parameter 2 to be string, array given in /var/www/htdocs/core/class/translate.class.php on line 354
Call Stack
# Time Memory Function Location
1 0.0021 257008 {main}( ) ../fiche.php:0
2 0.0923 1690872 Translate->trans( ) ../fiche.php:241
3 0.0924 1691112 Translate->getTradFromKey( ) ../translate.class.php:427
4 0.0925 1691304 preg_match ( ) ../translate.class.php:354

( ! ) Warning: preg_match() expects parameter 2 to be string, array given in /var/www/htdocs/core/class/translate.class.php on line 358
Call Stack
# Time Memory Function Location
1 0.0021 257008 {main}( ) ../fiche.php:0
2 0.0923 1690872 Translate->trans( ) ../fiche.php:241
3 0.0924 1691112 Translate->getTradFromKey( ) ../translate.class.php:427
4 0.0926 1691432 preg_match ( ) ../translate.class.php:358

( ! ) Warning: preg_match() expects parameter 2 to be string, array given in /var/www/htdocs/core/class/translate.class.php on line 362
Call Stack
# Time Memory Function Location
1 0.0021 257008 {main}( ) ../fiche.php:0
2 0.0923 1690872 Translate->trans( ) ../fiche.php:241
3 0.0924 1691112 Translate->getTradFromKey( ) ../translate.class.php:427
4 0.0927 1691432 preg_match ( ) ../translate.class.php:362

( ! ) Warning: preg_match() expects parameter 2 to be string, array given in /var/www/htdocs/core/class/translate.class.php on line 366
Call Stack
# Time Memory Function Location
1 0.0021 257008 {main}( ) ../fiche.php:0
2 0.0923 1690872 Translate->trans( ) ../fiche.php:241
3 0.0924 1691112 Translate->getTradFromKey( ) ../translate.class.php:427
4 0.0927 1691432 preg_match ( ) ../translate.class.php:366

( ! ) Warning: Cannot modify header information - headers already sent by (output started at /var/www/htdocs/core/class/translate.class.php:354) in /var/www/htdocs/main.inc.php on line 917
Call Stack
# Time Memory Function Location
1 0.0021 257008 {main}( ) ../fiche.php:0
2 0.0930 1691576 llxHeader( ) ../fiche.php:577
3 0.0930 1694408 top_htmlhead( ) ../main.inc.php:889
4 0.0930 1694584 top_httphead( ) ../main.inc.php:941
5 0.0930 1694736 header ( ) ../main.inc.php:917
Step to reproduce bug:  
Detected in version:  3.5.3 Category:  Module: Users
Severity:  5 - Major OS Type/Version:  
PHP version:   Database type and version:  
 Etat
Status:  Need more info Assigned to:  Cedric GROSS (kreizit)
Resolution:  Aucun 

Commentaires

Cedric GROSS 01/07/2014 12:41
Like Laurent, I don't reach to reproduce that on 3.5.4
What is piece of code used for trigger failure ?
Marcos García 26/06/2014 21:17
Still happening with latest 3.5 branch code
Laurent Destailleur 20/06/2014 16:20
Can't find a way to reproduce. So i introduced a check into 3.6 version to avoid this.


reply via email to

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