Changes between Initial Version and Version 1 of Ticket #26673
- Timestamp:
- 12/18/2013 05:40:26 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #26673 – Description
initial v1 7 7 We use `wp_parse_args()` to parse an `$args` parameter against default known parameters for some functionality. bbPress's `bbp_parse_args()` function applies filters before and after the `array_merge()` which allows for just-in-time or brute-force filtering of parsed arguments. Each call to `bbp_parse_args()` includes a unique string so each call has unique filters applied to them. 8 8 9 This introduces invisible flexibility for each call to `wp_parse_args()` when a unique string is passed. If no string is passed, no filters are applied, meaning it's completely backwards compatible and allows for filters to be rolled in on a case by case basis later. 10 11 Patch incoming 9 The incoming patch introduces invisible flexibility for each call to `wp_parse_args()` when a unique string is passed. If no string is passed, no filters are applied, meaning it's completely backwards compatible and allows for filters to be rolled in on a case by case basis later.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)