Issue with EventLogger and loading config from the container about ldaprecord-lumen HOT 5 CLOSED

Hi @AlastairDewar,

I've just released LdapRecord-Lumen v2.0 that should resolve your issues that you're experiencing. 🎉

Can you give it a shot and let me know your results?

from ldaprecord-lumen.

Thanks @stevebauman.

It looks like it's still occurring, but now in newer ./src/Events/Logger.php.

./vendor/directorytree/ldaprecord/src/Events/Logger.php:74
./vendor/directorytree/ldaprecord/src/Events/Logger.php:42
./vendor/directorytree/ldaprecord/src/Container.php:235
./vendor/directorytree/ldaprecord/src/Events/Dispatcher.php:266
./vendor/directorytree/ldaprecord/src/Events/Dispatcher.php:112
./vendor/directorytree/ldaprecord/src/Events/Dispatcher.php:93
./vendor/directorytree/ldaprecord/src/Auth/Guard.php:216
./vendor/directorytree/ldaprecord/src/Auth/Guard.php:101
./vendor/directorytree/ldaprecord/src/Auth/Guard.php:134

I've managed to get around the issue just now by setting the env variable LDAP_LOGGING to false.

This is not an issue for me, as the logging is not something I require and was using just for debugging.

Thanks for your help,
Ally

from ldaprecord-lumen.

Happy to help @AlastairDewar!

That's strange that you're still encountering it though. Would you mind letting me know your Lumen version so I can try and debug this?

It looks like your Lumen application doesn't have the config singleton registered in its container. I'm not sure if that's something that was added in a later version of Lumen or not.

from ldaprecord-lumen.

I've tested this again via the following:

1. Created a completely fresh Lumen 8.0 instance
2. Followed the documentation guide step-by-step
3. Enabled LDAP logging
4. Attempted querying an LDAP directory

Everything is working fine -- no errors or exceptions. All operations are also being successfully sent to the log file.

Let me know your version and I can help you debug this 😄

from ldaprecord-lumen.

Closing due to inactivity.

from ldaprecord-lumen.