Skip to content

Commit 4d9a475

Browse files
Edits
1 parent 5a27ff5 commit 4d9a475

File tree

1 file changed

+8
-13
lines changed

1 file changed

+8
-13
lines changed

_posts/2016-07-29-version-0.24.0.md

Lines changed: 8 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -17,30 +17,25 @@ With this model, my focus is shifting towards designing a world-class experience
1717

1818
For organizational users, one last ask: if you care about the WP-CLI release cycle, please [let me know how often you think WP-CLI should be released](https://github.com/wp-cli/wp-cli/issues/3198).
1919

20-
Let's get on with the show. Use `wp cli update` to install v0.24.0, representing [NNN resolved issues and pull requests](https://github.com/wp-cli/wp-cli/issues?q=milestone%3A0.24.0+is%3Aclosed). Here's what's new.
20+
Let's get on with the show. Use `wp cli update` to install v0.24.0, representing [450 resolved issues and pull requests](https://github.com/wp-cli/wp-cli/issues?q=milestone%3A0.24.0+is%3Aclosed). Here's what's new.
2121

22-
### WP-CLI no longer uses a forked `wp-settings.php`
22+
### Forked `wp-settings.php` no more
2323

2424
Every application has a bootstrap file which loads all of the requisite utilities needed to serve a request. In WordPress, this is called `wp-settings.php`.
2525

2626
Since v0.8.0 [[#261](https://github.com/wp-cli/wp-cli/pull/261)], WP-CLI has used a forked version of the bootstrap file, called `wp-settings-cli.php`, to give us more control over the load process, and providing features like `--skip-plugins`. But, because WordPress can require new files from `wp-settings.php`, maintaining a forked version has the unfortunate side effect of WP-CLI [regularly breaking when a new version of WordPress is released](http://wp-cli.org/blog/versions-0.21.1-and-0.20.4.html).
2727

2828
Thanks to coordinated changes in the WordPress project, WP-CLI v0.24.0 returns to loading `wp-settings.php` for WordPress 4.6 and higher [[#2278](https://github.com/wp-cli/wp-cli/issues/2278)]. Doing so should make a given version of WP-CLI more future proof against new versions of WordPress.
2929

30-
### Increased documentation coverage
30+
### More documentation in more languages
3131

32+
Thanks to tireless efforts by a solid group of contributors, WP-CLI now has more documentation in more languages.
3233

33-
#### Improved examples for many commands.
34+
* Dozens of commands have improved examples for reference.
35+
* We have a new [CONTRIBUTING.md](https://github.com/wp-cli/wp-cli/blob/master/CONTRIBUTING.md), which also has a [page on the website](http://wp-cli.org/docs/contributing/).
36+
* Our new [README.md](https://github.com/wp-cli/wp-cli/blob/master/README.md) powers the [WP-CLI homepage](http://wp-cli.org/), and is available in [Japanese](http://wp-cli.org/ja/), [Français](http://wp-cli.org/fr/), [Português (Brasil)](http://wp-cli.org/br/), [Türkçe](http://wp-cli.org/tr/), [Deutsch](http://wp-cli.org/de/), [नेपाली](http://wp-cli.org/ne/), and [ελληνικά](http://wp-cli.org/gr/).
3437

35-
@tk
36-
37-
#### New README.md, homepage, and localization of homepage
38-
39-
@tk
40-
41-
#### New CONTRIBUTING.md
42-
43-
@tk
38+
Want to get involved with WP-CLI's documentation? Check out the [Github issues labeled "scope:documentation"](https://github.com/wp-cli/wp-cli/issues?q=is%3Aopen+sort%3Aupdated-desc+label%3Ascope%3Adocumentation).
4439

4540
### Aliases and SSH support
4641

0 commit comments

Comments
 (0)