Multiple PHP warnings and non-working drop-downs

ticgal / yagp

Yet Another GLPI Plugin

https://tic.gal/en/project/yagp-yet-another-glpi-plugin/

GNU Affero General Public License v3.0

2 stars 1 forks source link

Multiple PHP warnings and non-working drop-downs #37

Closed raregtp closed 9 months ago

raregtp commented 9 months ago

Using GLPI 10.0.10, and YAGP 2.2.0.

Getting this error flashing up on login and in various other screens:

In addition, I have discovered these three options will not let me set them to 'Yes'....but I believe this to be related to the above error:

Please let me know if you need any other information. Thanks!!

OscarBeiro commented 9 months ago

It looks like the issue is on the webresources plugin, which unfortunately I don't know. Not sure if we need to do something about it.

raregtp commented 9 months ago

So your saying the above warnings and the non-working drop-downs are due to the Webresources plugin? I did disable and uninstall that plugin but there is no change to the issue after doing so. Am I missing something?

OscarBeiro commented 9 months ago

Sorry, I think I've mixed up some different Issues. Could you please recreate it on a clean instance?

raregtp commented 9 months ago

Well......time-wise, I can't quickly test it on a clean instance. That said, I have another instance in a test environment that is still on GLPI 10.0.8, and the latest version of YAGP does seem to work ok there (the drop-downs, not sure on the PHP warnings as I don't always see those on our prod instance).

I'm going to upgrade the 10.0.8 instance to 10.0.10 and see if there is any difference. More to come.

raregtp commented 9 months ago

Ok....YAGP continued to work normally on the test system after upgrading to 10.0.10. Embarrassingly, after looking at the plugin settings on the prod system we hadn't yet configured anything to "yes".....so I uninstalled and reinstalled the plugin and all is well. Not sure what happened there but all is good...appreciate the dialog!

OscarBeiro commented 9 months ago

Good to know it is fixed :) Thanks for the swift feedback.