Many might choose multiple words as theme name, and they may not be sure where they should use a space, a hyphen or an underscore to separate words when doing the initial replacements. The example provided in the README file should cover that scenario.
* Include skip-link-focus-fix.js in the js hint/lint tests & fix up the file.
* Pull in .jshintrc from WP SVN.
* Add PHPCompatibility Sniffs.
* Sync the ignore statements to always exclude .min.js files.
* Slim down the tested against PHP versions even more.
Helps avoid Travis CI errors for wrongly formatted comments. Most of
these end of function comments (if not all) are useless anyway.
Props @WPAddiction for reporting.
Fixes#891.
What it will now do:
- Lint the php files against relevant PHP versions.
- Lint the js files once - the result won't change across PHP versions.
- Check against WPCS once - the result won't change across PHP versions.
What I have changed:
- Added linting against PHP 7 and HHVM, with HHVM being allowed to fail.
- Added js linting and style check per example from Twenty Sixteen.
- Moved to the faster container based environment for running travis.
- Script will no longer pull in PHPCS, WPCS and the JS linters in every build. Now they will only be pulled in when needed.
- Limited the clone depth for quicker cloning of external repositories.
- Removed the pulling in of WP and running builds against different WP versions as this wasn't used at all in the actual test scripts.
Rationale:
1. The principle of pingbacks is based on articles. Pingbacks are a special kind of comments and the article being 'pinged-back' has to be identifiable (which they're not on archive pages and the like).
2. WP only registers a ping if it can identify the article which is supposed to have been 'pung'. See: https://developer.wordpress.org/reference/classes/wp_xmlrpc_server/pingback_ping/
3. Pingbacks, like comments, can be disabled on a per article basis.
Therefore, having the pingback url auto-discovery header in place, only makes sense on singular pages where pings are open.
It appears that the entire sidebar should be one large aside instead of
making each widget it's own aside. At least that's how I understand it
when reading w3. It would make sense to make each widget it's own aside
if not all of the widgets were asides, but otherwise the entire sidebar
should be considered one aside.
Plus I think this would make more sense for accessibility and with the
widgets titles being h2 because if the entire sidebar had a title that
would be the h1.
https://www.w3.org/wiki/HTML/Elements/aside
This fixes the header text color link (blogname) to also update the same way as the blogdescription
Fix for open issue #768 (Site title color in the Customizer)
Fixed the missing Blog title text when "Display Header Text "option in the Customizer is toggled on/off
Updated the code to adjust the css color of .site-title a
Fix for the header color issue #816
Prayag Verma
Chris Schmieder
Ardalan Naghshineh
David A. Kennedy
Takashi Irie
Greg Rickaby
jrfnl
Caroline Moore
Konstantin Obenland
mrwweb
Konstantin Obenland
byjml
sarah ✈ semark
Ulrich Pogson
alaczek
patryk
Emil Uzelac
Mark Batchelder
Serge Noskov
carl alberto
Tammie Lister
Dmitry Mayorov