Updated: Comment 0

Problem/Motivation

This 403/404 page should better describe that the message is actually the page on which the access denied/not found happened.

Proposed resolution

Remaining tasks

User interface changes

API changes

CommentFileSizeAuthor
#6 D8-Rename_watchdog_table_header_text-2105431.patch5.04 KBSagar Ramgade
#3 D8-Rename_watchdog_table_header_text-2105431.patch716 bytesSagar Ramgade
#1 D8-Rename_watchdog_table_header_text-2105431.patch674 bytesSagar Ramgade
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Sagar Ramgade’s picture

Sagar Ramgade CreditAttribution: Sagar Ramgade commented
Title: Rename the table headers on on thewatchdog 403/404 controllers » Rename the table headers on the watchdog 403/404 controllers
Issue summary: View changes
Status: Active » Needs review
FileSize
D8-Rename_watchdog_table_header_text-2105431.patch674 bytes

Hi,

Does it makes more sense to rename it to "URL", Attached patch does that.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented

This is also used for 'search', so maybe we should check whether we show 403/404 results.

dblog.search:
  path: '/admin/reports/search'
  defaults:
    _controller: '\Drupal\dblog\Controller\DbLogController::topLogMessages'
    _title: 'Top search phrases'
    type: 'search'
  requirements:
    _module_dependencies: 'search'
    _permission: 'access site reports'
Sagar Ramgade’s picture

Sagar Ramgade CreditAttribution: Sagar Ramgade commented
FileSize
D8-Rename_watchdog_table_header_text-2105431.patch716 bytes

I didn't notice that, Here is the updated patch.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Status: Needs review » Reviewed & tested by the community

Cool

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
CreditAttribution: alexpott commented
Status: Reviewed & tested by the community » Needs review

Shouldn't we do this in a more elegant and extensible way? For example add:

DbLogController::topLogMessagesUrl($type) {
  return $this->topLogMessages($type, $this->t('URL'));
}
DbLogController::topLogMessagesSearch($type) {
  return $this->topLogMessages($type, $this->t('Search'));
}

And change DbLogController::topLogMessages to accept and row title?

Sagar Ramgade’s picture

Sagar Ramgade CreditAttribution: Sagar Ramgade commented
FileSize
D8-Rename_watchdog_table_header_text-2105431.patch5.04 KB

Hi Alex,

Here's the patch as per your suggestion.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dagmar’s picture

dagmar
Primary language Spanish
Location Argentina
CreditAttribution: dagmar as a volunteer and at Globant commented
Component: watchdog.module » dblog.module

Moved to dblog.module for future triage.

dagmar’s picture

dagmar
Primary language Spanish
Location Argentina
CreditAttribution: dagmar as a volunteer and at Globant commented
Status: Needs review » Needs work 
  1. +++ b/core/modules/dblog/src/Controller/DbLogController.php
@@ -133,20 +133,24 @@ public function overview() {
+        'class' => array(RESPONSIVE_PRIORITY_LOW)

    This needs to be updated to array [] syntax. 

  2. +++ b/core/modules/dblog/src/Controller/DbLogController.php
@@ -233,7 +237,9 @@ public function overview() {
+    if ($dblog = $this->database->query('SELECT w.*, u.name, u.uid FROM {watchdog} w INNER JOIN {users_field_data} u ON w.uid = u.uid WHERE w.wid = :id AND u.default_langcode = 1', array(':id' => $event_id))

    This change should not be part of this patch. 

  3. +++ b/core/modules/dblog/src/Controller/DbLogController.php
@@ -366,13 +400,16 @@ public function formatMessage($row) {
+  public function topLogMessages($type, $title) {

    This is breaking Backward Compatibility. You could use the info returned by topLogMessages() and change the header there.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.