Forum GLPI-Project

Mr.Sfigatto

Member

Registered: 2014-02-04

Posts: 102

Tab historical // Security die. trying to load an forbidden class name

Hi,
For some ticket the tab historical returns with this error:

Security die. trying to load an forbidden class name

What could cause the issue?

I'm on glpi 0.85.2 (and .4 in dev environment)

Thanks

yllen

GLPI-DEV

From: Sillery (51)

Registered: 2008-01-14

Posts: 15,278

Re: Tab historical // Security die. trying to load an forbidden class name

Do you use plugins?

---

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)

Mr.Sfigatto

Member

Registered: 2014-02-04

Posts: 102

Re: Tab historical // Security die. trying to load an forbidden class name

Course yes..
Anyway I saw (and I strongly hope..) that it is strictly related to old tickets. I didn't still noticed about the same issue on tickets opened after the go live of  0.85.

Thanks

Last edited by Mr.Sfigatto (2015-05-18 15:46:00)

yllen

GLPI-DEV

From: Sillery (51)

Registered: 2008-01-14

Posts: 15,278

Re: Tab historical // Security die. trying to load an forbidden class name

Have you try to deactivate your plugin to see is the problem persists?

---

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)

Mr.Sfigatto

Member

Registered: 2014-02-04

Posts: 102

Re: Tab historical // Security die. trying to load an forbidden class name

Yes, unfortunately the issue persist..

Consider that this issue is affecting even the mailreceiver when glpi try to load new email sent by user in reply to followups. This happens only if the ticket itself has the issue.

To unlock the receiver it is required to move the email from inbox to another folder so that the receiver can go ahed.

blerohellec

Member

From: Paris

Registered: 2015-04-08

Posts: 84

Re: Tab historical // Security die. trying to load an forbidden class name

Hello,

I got this error caused by plugin CustomFields, in its version for 0.85.
Once customfields have been added to an objet (eg a ticket), the error occurs.
Even when the plugin is desactivated, the error persists because the lines originating the error remain in the historical.

This error has been reported to the plugin's developpers.

Regards

---

Benoit Le Rohellec
blerohellec@tlsconsulting.eu
www.tlsconsulting.eu