Implementing a Psr-3 Logger upper \jLog::log #5866
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdouchin
approved these changes
Jul 1, 2025
Require psr/log:2.* because psr/log 3.* is in conflict with symfony/console v5.4.47
```
Your requirements could not be resolved to an installable set of packages.
Problem 1
- symfony/console v5.4.47 conflicts with psr/log 3.0.2.
- symfony/console v5.4.47 conflicts with psr/log 3.0.1.
- symfony/console v5.4.47 conflicts with psr/log 3.0.0.
- jelix/jelix dev-jelix-1.8.x requires symfony/console ^5.4.26 -> satisfiable by symfony/console[v5.4.47].
- jelix/jelix is locked to version dev-jelix-1.8.x and an update of this package was not requested.
- Root composer.json requires psr/log ^3.0 -> satisfiable by psr/log[3.0.0, 3.0.1, 3.0.2].
```
symfony/console could not be updated to version v7 because jelix-1.8.x requires symfony/console ^5.4.26
nworr
reviewed
Jul 15, 2025
| \lizmap::getLogger()->log($cat, $message); | ||
| } else { | ||
| \jLog::log($message, $cat); | ||
| } |
There was a problem hiding this comment.
In a long term, maybe this function should launch a deprecated error ?
We may add a CustomLogger acting as PSR-3 logger but for the lizadmin file ?
// \lizmap::getAppContext()->logMessage($errormsg, 'lizmapadmin');
lizmap::getCustomLoger()->debug($errormsg);
There was a problem hiding this comment.
You're rights @nworr but do we still need a lizmap-admin log ?
There was a problem hiding this comment.
I think so , the aim of "lizmap-admin" is to display on admin backend some events (and keep more sensitive events to the errors.log, unreadable for non "sysadmin" users ) .
| } | ||
| } else { | ||
| \jLog::logEx($exception, $cat); | ||
| } |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Psr-3 Logger has seven log levels :
The log levels could be defined in the LizmapConfig.ini.php file or with setLogLevel of the Logger.
A main logger is available through the lizmap singleton :
lizmap::getLogger()or can be instantiated with it's own levelnew Lizmap\Logger\Logger('info').