Forum GLPI-Project

joseph.fischetti

Member

Registered: 2017-05-16

Posts: 4

Upgrade database to 9.1.3 from .84.5

We have an existing GLPI installation and I was tasked with updating to a new one.

I ran into 2 snags after importing/updating the database:
1)  Our "Staff" profile lost all permissions set for asset view/management.  The existing installation has "write" selected for every drop down, while the new installation had an empty table with nothing allowed.

2)  The associated elements table wasn't properly populated.  Ticket management had empty results under "Associated Elements" for every ticket.  The glpi_items_tickets table was empty.

My fix was to run the following SQL command, to pull the associated element out of each row in tickets, and insert it into the glpi_items_tickets table:

INSERT INTO glpi_items_tickets (itemtype, items_id, tickets_id)
SELECT itemtype, items_id, id as tickets_id
FROM glpi_tickets
WHERE NOT items_id=0;

yllen

GLPI-DEV

From: Sillery (51)

Registered: 2008-01-14

Posts: 15,278

Re: Upgrade database to 9.1.3 from .84.5

1/ in 0.85 the system of profile change but all old rights are transcribed.
    For Write right, read, create, update, delete, purge are defined.

2/ This table was created in 0.85.3 with items of glpi_tickets
   Have you still items_id and itemtype fields in glpi_tickets table?

---

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)

joseph.fischetti

Member

Registered: 2017-05-16

Posts: 4

Re: Upgrade database to 9.1.3 from .84.5

It seems that multiple profile types lost their permissions after the upgrade.  I specified "Staff" in my original post, but no other profile types have any permissions associated.

Every row in the tickets table still had the entries for associated elements.  The query that I ran from the original post took the values from the tickets rows and inserted them into the glpi_items_tickets table.