[wp-trac] [WordPress Trac] #29577: Twenty Thirteen: Use proper way to get customizer settings values
WordPress Trac
noreply at wordpress.org
Thu Nov 20 13:13:50 UTC 2014
#29577: Twenty Thirteen: Use proper way to get customizer settings values
---------------------------------------------+-------------------------
Reporter: obenland | Owner: kdoran
Type: defect (bug) | Status: assigned
Priority: normal | Milestone: 4.1
Component: Bundled Theme | Version: 3.5
Severity: normal | Resolution:
Keywords: good-first-bug has-patch commit | Focuses: javascript
---------------------------------------------+-------------------------
Changes (by obenland):
* keywords: good-first-bug has-patch needs-testing => good-first-bug has-
patch commit
* focuses: => javascript
* version: 3.6 => 3.5
Comment:
From Slack:
> @obenland: When you have time could you review #29577 please? Need to
know if Twenty Twelve also needs a similar patch. And if it's urgent for
4.1 and next theme releases in directory.
[attachment:29577.4.diff] covers Twenty Twelve as well. Just tested it
successfully with 3.5.
I'm not sure we really need a separate ticket for Twenty Twelve, we could
as well update the description of this ticket to make it broader, if that
is the reason.
It's not necessarily urgent, but it's a reasonably small change that has
been soaking for all of 4.1, so I don't see a reason to wait either.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/29577#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list