WordPress.org

Make WordPress Core

Opened 18 months ago

Closed 18 months ago

Last modified 15 months ago

#46955 closed defect (bug) (fixed)

Order of WP_DEBUG and WP_MAX_MEMORY_LIMIT of site health info

Reported by: tmatsuur Owned by: SergeyBiryukov
Milestone: 5.2 Priority: normal
Severity: normal Version: 5.2
Component: Site Health Keywords: site-health
Focuses: administration Cc:

Description

This is a proposal for the order of WP_DEBUG and WP_MAX_MEMORY_LIMIT.

Currently, the site health info items are as follows.

WP_DEBUG: true
WP_MAX_MEMORY_LIMIT: 512M
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: true
SCRIPT_DEBUG: false

I think it is better to line up debugging related constants.

WP_MAX_MEMORY_LIMIT: 512M
WP_DEBUG: true
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: true
SCRIPT_DEBUG: false

Attachments (1)

46955.diff (894 bytes) - added by tmatsuur 18 months ago.

Download all attachments as: .zip

Change History (5)

@tmatsuur
18 months ago

#1 @SergeyBiryukov
18 months ago

  • Component changed from General to Administration
  • Focuses administration added
  • Keywords site-health added
  • Milestone changed from Awaiting Review to 5.2
  • Type changed from feature request to defect (bug)

#2 follow-up: @SergeyBiryukov
18 months ago

  • Owner set to SergeyBiryukov
  • Resolution set to fixed
  • Status changed from new to closed

In 45230:

Site Health: Group WP_DEBUG-related constants together.

Props tmatsuur.
Fixes #46955.

#3 in reply to: ↑ 2 @tmatsuur
18 months ago

Replying to SergeyBiryukov:

In 45230:

Site Health: Group WP_DEBUG-related constants together.

Props tmatsuur.
Fixes #46955.

Thank you @SergeyBiryukov .

#4 @spacedmonkey
15 months ago

  • Component changed from Administration to Site Health
Note: See TracTickets for help on using tickets.