pluginsGLPI / escalade

GLPI Plugin escalade
http://www.teclib-edition.com
GNU General Public License v2.0
17 stars 30 forks source link

Groups do not appear in suggestions when creating a ticket #173

Closed Critxtth closed 6 months ago

Critxtth commented 6 months ago

Hi,

I am not sure if this is the same issue as this issue But it certainly look similar. I have recently updated GLPI from 10.0.10 to 10.0.12, and the escalade plugin to 2.9.3. Since this update, I encounter a bug : I can't assign new tickets to a group that I'm not a member of.

This is the expected behavior :

image

This is the behavior after update :

image

I haven't changed the config, it's always been the same but it doesn't work anymore after the update, even after trying the fix from this PR (which I thought was related, but maybe it is not) : https://github.com/pluginsGLPI/escalade/pull/172

Escalade config :

image

I will also add that I tried disabling all the other plugins and leave this one enabled only, and it doesn't change a thing.

Critxtth commented 6 months ago

FYI I tried fix #174 , and now I can't assign the ticket to anyone anymore because it's stuck in loading :

image

stonebuzz commented 6 months ago

can you check glpi log ?

Critxtth commented 6 months ago

can you check glpi log ?

I have set 2 log files in the apache web server, the CustomLog combined gives me this log when I click on the "assign to" drop down :

image

Are you looking for something else ?

Observer and Creator field work fine by the way.

stonebuzz commented 6 months ago

Hi @Critxtth

can you test this PR -> https://github.com/pluginsGLPI/escalade/pull/176

Best regards

Critxtth commented 6 months ago

Hi @stonebuzz thanks for your reply.

It doesn't seem to be working, now it does load the users but still not the groups.

Maybe I am not proceeding the right way, so I'll tell you what I do and you let me know if I do something wrong.

So I go check the PR you mentionned (#176) , and there I take the link to the files you changed, and proceed this way :

cd /var/www/html/glpi/plugins/escalade
mv setup.php setup.php.bkp
wget https://github.com/pluginsGLPI/escalade/blob/fbc2819cf35844420fbf8c6d6374ebe7f78ea02b/setup.php
chown apache.apache setup.php
chmod g+w setup.php
cd inc/
mv group_group.class.php group_group.class.php.bkp
wget https://github.com/pluginsGLPI/escalade/blob/fbc2819cf35844420fbf8c6d6374ebe7f78ea02b/inc/group_group.class.php
chown apache.apache group_group.class.php
chmod g+w group_group.class.php

Is that correct or am I missing something ?

Thanks in advance

stonebuzz commented 6 months ago

Hi @Critxtth

we prefer to use patches (to make sure we apply all the changes without forgetting any)

Can you deliver version 2.9.3 (without any changes to the code)

Then, jJust apply this -> https://patch-diff.githubusercontent.com/raw/pluginsGLPI/escalade/pull/176.diff

With

cd /var/www/html/glpi/marketplace/escalade/
patch -p1 < path_to_file.patch

Finally, logging out of GLPI, clearing the cache with the following command

cd /var/www/html/glpi/
php bin/console cache:clear

and then logging in again, and retry

Critxtth commented 6 months ago

Hi @Critxtth

we prefer to use patches (to make sure we apply all the changes without forgetting any)

Can you deliver version 2.9.3 (without any changes to the code)

Then, jJust apply this -> https://patch-diff.githubusercontent.com/raw/pluginsGLPI/escalade/pull/176.diff

With

cd /var/www/html/glpi/marketplace/escalade/
patch -p1 < path_to_file.patch

Finally, logging out of GLPI, clearing the cache with the following command

cd /var/www/html/glpi/
php bin/console cache:clear

and then logging in again, and retry

Hi @stonebuzz ,

Following your procedure, it seems like it's working now 👍 Thank you for your time !