Description of problem: I'm using phpldapadmin, installed from mageia repository, on a mageia 8 the access fails with the following php errror [Tue Jun 08 10:28:28.178179 2021] [php:error] [pid 29100] [client 137.129.151.11:56910] PHP Fatal error: Uncaught Error: Call to undefined function get_magic_quotes_gpc() in /usr/share/phpldapadmin/lib/common.php:299\nStack trace:\n#0 /usr/share/phpldapadmin/htdocs/common.php(13): require_once()\n#1 /usr/share/phpldapadmin/htdocs/cmd.php(13): require_once('/usr/share/phpl...')\n#2 /usr/share/phpldapadmin/htdocs/index.php(153): include('/usr/share/phpl...')\n#3 {main}\n thrown in /usr/share/phpldapadmin/lib/common.php on line 299 the php doc says ( https://www.php.net/manual/en/function.get-magic-quotes-gpc.php) that the function has been DEPRECATED as of PHP 7.4.0, and REMOVED as of PHP 8.0.0 Version-Release number of selected component (if applicable): phpldapadmin-1.2.6.2-1 How reproducible: every time Steps to Reproduce: 1. urpmi phpldapadmin 2. open phpldapadmin url , should be http://localhost/phpldapadmin/ 3. look at /var/log/httpd/error_log file
Thank you for the report. Seeing we are at version 1.2.6.2, these sites: https://sourceforge.net/projects/phpldapadmin/ http://phpldapadmin.sourceforge.net/wiki/index.php/Release are terribly old, stopping at about 1.2.2. The URL in the RPM summary is ancient, and I think should now be: https://github.com/leenooks/phpLDAPadmin I could find nothing more recent ... until: https://github.com/leenooks/phpLDAPadmin/releases on 23 Sep 2020 1.2.6.2 As for PHP8, I found just this: https://github.com/leenooks/phpLDAPadmin/issues/133 "Not working with PHP 8.0 #133" says it all. Raised early in the year, nothing seems to be happening on it. Marking this Upstream. Marc did the commit for version 1.2.6.2, so think it best to assign this bug to you.
Status: NEW => UPSTREAMURL: (none) => https://github.com/leenooks/phpLDAPadmin/issues/133Assignee: bugsquad => mageia
@Lewis: thanks. I'm not sure how we will handle this with mageia. I can do some patching. But I don't think it is the idea of patching sources from an almost untouched project for years. Maybe there already exists some patches on forkes subprojects - one of the things of github I don't understand... I assume v2 which was announced 9 months ago will fix this - but I can't find, when this will be ready.
we already updated/moved to a newer version which should solve this
Resolution: (none) => OLDStatus: UPSTREAM => RESOLVED