Created attachment 1850874 [details] 1st patch Created attachment 1850874 [details] 1st patch Description of problem: phpldapadmin does not work at all with PHP >= 8 Version-Release number of selected component (if applicable): 1.2.6.2-3 How reproducible: Always Steps to Reproduce: 1. Install 2. Configure 3. Try to run from a browser. Actual results: Variouss warnings and error messages. Expected results: Working Additional info: The Fedora 35 version 1.2.6.2-3 fails because PHP version is >= 8. I made it work and posted a PR upstream but as they are not very reactive, I leave these 4 patches here in hope you will apply them quicker. Thanks.
Created attachment 1850875 [details] 2nd patch
Created attachment 1850876 [details] 3rd patch
Maybe give upstream a bit more time (at least a week, as per Fedora policies :) )? Anyway, Would you like to co-maintain?
> Maybe give upstream a bit more time (at least a week, as per Fedora policies :) )? Sure! I just wanted to pull your attention on it: this is not the first time I submit patches to this project and I know they have a very high "latency", if some. > Anyway, Would you like to co-maintain? No thanks! I'm already quite busy on some other projects and patched this because I need it. Sorry!
Created attachment 1850947 [details] 4th patch
Link to upstream PR: https://github.com/leenooks/phpLDAPadmin/pull/149
FEDORA-2022-ec7eb3a63a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec7eb3a63a
FEDORA-2022-ec7eb3a63a has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-ec7eb3a63a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec7eb3a63a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-ec7eb3a63a has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.