This category is for issues regarding specific apps, NOT general issues with YunoHost.
on
This form is written in English but feel free to write in French if you’re more comfortable!
on
What app is this about, and its version
PhpIpam, 1.19.008~ynh1
What YunoHost version are you running
12.1.41.2
What type of hardware are you using
Old laptop or computer
Describe your issue
Hello everyone ! So I just installed PhPIpam on my yunohost server and I got this weird bunch of warnings that appear directly on app screen and maks the app unusable, because a new line appears at each click anywhere on the app. The log shows this message : “Warning: Attempt to read property “log” on null in /var/www/phpipam/functions/classes/class.Log.php on line 74”. Can somebody explain what it means, why it shows on the web interface and most important : how to get rid of them ?
Bonjour tout le monde, je viens d’installer PHPIpam sur mon yunohost et à chaque fois que j’ouvre l’appli j’ai des logs qui apparaissent directement dans l’appli et la rendent inutilisable : “Warning: Attempt to read property “log” on null in /var/www/phpipam/functions/classes/class.Log.php on line 74” est-ce que quelqu’un aurait déjà vu ça, et saurait comment s’en débarrasser ?
Merci/Thanks
Share relevant logs or error messages
Warning: Attempt to read property “log” on null in /var/www/phpipam/functions/classes/class.Log.php on line 74
Hi @PdeJj
The ynh shipped version is quite outdated (v1.19 whereas the upstream latest release is 1.8.3). I updated the source and the php version.
I only can say it installs but the package may need some rework…
If you want to test the v1.8.3 :
Hello, thank you for taking time to answer me. I installed it with the command you gave me. Now the application just shows “invalid username or password”. So I ran the script to reset admin credentials, but it still shows the same message (cf screenshot)
Hi, just for the follow-up, the original issue reported here is covered by 31, and the version issue by 28.
Merging the fix branch could solve the two issues and update the app to the latest release (thus preventing security breaches), but I understand some work needs to be done regarding the DB upgrade ?
@SveDec
Well, I think upgrading from version 1.19.008 is impossible. IMO, it’s a non-working version (upstream released it in 2015… and it was installed with PHP 8.3 released 8 years later…).
If your version was up to date until the bot meltdown, (around v1.7 ?) I guess you can safely upgrade to 1.8.3. Let us know !