Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
admin_toolbar
Manage
Activity
Members
Labels
Plan
Wiki
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
project
admin_toolbar
Commits
b655dbac
Commit
b655dbac
authored
8 months ago
by
Jakob P
Browse files
Options
Downloads
Patches
Plain Diff
Issue
#3446836
: Incorrect logger name in admin_toolbar_links_access_filter module.
parent
d969da4e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Pipeline
#242083
passed with warnings
8 months ago
Stage: build
Stage: validate
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
admin_toolbar_links_access_filter/admin_toolbar_links_access_filter.module
+1
-1
1 addition, 1 deletion
...ks_access_filter/admin_toolbar_links_access_filter.module
with
1 addition
and
1 deletion
admin_toolbar_links_access_filter/admin_toolbar_links_access_filter.module
+
1
−
1
View file @
b655dbac
...
...
@@ -123,7 +123,7 @@ function admin_toolbar_links_access_filter_filter_non_accessible_links(array &$i
}
catch
(
\UnexpectedValueException
$e
)
{
// Skip on errors like "base:block has no corresponding route":
\Drupal
::
logger
(
'
my_module
'
)
->
error
(
$e
->
getMessage
());
\Drupal
::
logger
(
'
admin_toolbar
'
)
->
error
(
$e
->
getMessage
());
continue
;
}
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment