Forum GLPI-Project

bruhelp

Member

Registered: 2015-08-10

Posts: 4

[GLPI 0.85.4] Problems searching for users

Hello,

We have recently updated from version 0.85.4  Since that update the system seems to require quite some time to find the specific user in the database.

On my one search for the issue i found out that when i turn on the debug mode i recieve a php error.
This one concerning the search class. the error beeing :

PHP Notice: Undefined offset: 2 in C:\inetpub\wwwroot\inc\search.class.php at line 3814
PHP Notice: Undefined offset: 2 in C:\inetpub\wwwroot\inc\search.class.php at line 3814

this would be found in this piece of code underneath:
if (isset($data[$num][$k]['name'])
                           && ($data[$num][$k]['name'] > 0)
                              || ($data[$num][$k][2] != '')) {
                        if ($count_display) {
                           $out .= self::LBBR;
                        }            }

Is there a solution to this?

Last edited by bruhelp (2015-09-03 14:44:23)

yllen

GLPI-DEV

From: Sillery (51)

Registered: 2008-01-14

Posts: 15,278

Re: [GLPI 0.85.4] Problems searching for users

What is your version of GLPI? 85.4 as in the title of your post? or 0.84 as in the body of your post?

---

CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6  - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)

bruhelp

Member

Registered: 2015-08-10

Posts: 4

Re: [GLPI 0.85.4] Problems searching for users

It is he 85.4 I made a typo I changed it in the first post.

yllen

GLPI-DEV

From: Sillery (51)

Registered: 2008-01-14

Posts: 15,278

Re: [GLPI 0.85.4] Problems searching for users

This issue was solved in 0.85.5 svn

---

CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6  - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)

bruhelp

Member

Registered: 2015-08-10

Posts: 4

Re: [GLPI 0.85.4] Problems searching for users

Wil it solve the search speed of a user aswel? Or is that due to an other error?