WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#25417 closed defect (bug) (fixed)

Stopping HTML in comments Codex section

Reported by: henrywright Owned by:
Milestone: WordPress.org Priority: normal
Severity: trivial Version:
Component: WordPress.org site Keywords:
Focuses: Cc:
PR Number:

Description

http://codex.wordpress.org/Answers-Configuration#Stopping_HTML_in_Comments

This Codex section is telling users to modify the kses.php core file. Perhaps this should be updated to reflect best practice?

Please feel free to let me know if this is the wrong place to report such stuff.

Change History (6)

#1 @SergeyBiryukov
6 years ago

  • Component changed from General to WordPress.org site
  • Keywords needs-codex added
  • Milestone changed from Awaiting Review to WordPress.org

#2 @DrewAPicture
6 years ago

  • Component changed from WordPress.org site to General
  • Keywords needs-codex removed
  • Milestone changed from WordPress.org to 3.7
  • Resolution set to fixed
  • Status changed from new to closed

I've removed the offending section.

@henrywright: For future reference, remember that the Codex is a wiki. Anyone with a WordPress.org username can edit any page in the Codex, including yourself :)

#3 follow-up: @SergeyBiryukov
6 years ago

  • Component changed from General to WordPress.org site
  • Milestone changed from 3.7 to WordPress.org

#4 in reply to: ↑ 3 ; follow-up: @DrewAPicture
6 years ago

Replying to SergeyBiryukov:
Setting the milestone to WordPress.org implies that it's the responsibility of the meta team to make changes to the Codex. It's an issue for the docs team, though it doesn't apply to Inline Docs or the Help/About components.

#5 @henrywright
6 years ago

@DrewAPicture thanks for letting me know :)

#6 in reply to: ↑ 4 @SergeyBiryukov
6 years ago

Replying to DrewAPicture:

Setting the milestone to WordPress.org implies that it's the responsibility of the meta team to make changes to the Codex.

I think it just indicates that the ticket requires changes on WordPress.org rather than in core. As you pointed out, anyone can make the changes.

We used to assign Codex edits to the WordPress.org component and milestone in the past, I was just following the existing pattern.

Last edited 6 years ago by SergeyBiryukov (previous) (diff)
Note: See TracTickets for help on using tickets.