WordPress 3.6がリリースされたのはつい2ヶ月前のことだが、すでにWordPress 3.7の準備はほぼ整っている。2013年10月14日にリリースされる予定です。重要な変更がいくつか予定されています。WordPress 3.7は、主にWordPressコアのセキュリティと安定性に重点を置いています。WordPress 3.7ではどのような新機能が追加されるのか見てみましょう。
自動更新
WordPress 3.7で最も期待されている機能のひとつが自動更新です。マネージドWordPressホスティングサービスプロバイダーは、すでに新しい更新が利用可能になると、ユーザーのためにWordPressの自動更新を行っています。
しかし、WordPressはこれを独自に行うことができるようになります。一般的なWordPressインストールでは、マイナーリリースやセキュリティリリースの更新をユーザー入力なしで自動的に行うことができるようになります。これは、ユーザーがWordPressを3.7から3.7.1に更新する必要がないことを意味します。しかし、初期設定ではメジャーリリース、例えば3.7.1から3.8への自動更新は行われません。
ツイッターやフェイスブックのページでユーザーの意見を聞いたところ、さまざまな反応がありました。とても気に入った人もいれば、絶対に嫌だという人もいた。このため、wp-config.phpファイルから自動更新をオフにするオプションを設定する予定です。また、wp-config.phpにdefineパラメータを追加することで、プロセスを完全に自動化し、WordPressをメジャーリリースに自動更新するオプションも用意する予定です。
言語パック
WordPress 3.7では、言語パックのサポートも強化されます。WordPress 3.7の現在の目標は、デフォルトテーマ、インポータープラグイン、WordPressコアの言語ファイルを区切りで管理することです。ユーザーにとっては、WordPressを自分の言語で使用している場合、更新のたびにWordPressがデフォルトテーマ、インポータープラグイン、コアの言語ファイルを自動的に取得することを意味します。
現在のところ、ユーザーは翻訳対応のWordPressテーマを探し、言語ファイルをインストールする必要があります。願わくば、この機能が他のテーマやプラグインにも拡張され、ユーザーが使用する各プラグインの翻訳ファイルのダウンロードやアップロードを心配する必要がなくなることを願っています。
新規パスワードメーター
強力なパスワードはWordPressのセキュリティにとって重要である。そのため、WordPressにはパスワード強度メーターが付属していますが、これは非常に弱いものです。そのため、WordPress 3.7では、コアチームは、ユーザーがより強力なパスワードを選択することを奨励する新しいパスワードメーターを追加することを決定しました。
これは、管理者がユーザーに強力なパスワードの使用を強制するために使用できる強制強力パスワードプラグインと一緒に素晴らしい追加となります。
WordPress検索の改善
WordPressの初期設定の検索はベストとは言えない。そのため、多くのユーザーはSearchWPや Googleカスタム検索などの他のソリューションに頼っている。
ありがたいことに、WordPress 3.7では初期設定が少し改善されます。WordPressは検索結果を時系列順ではなく、関連性で表示するようになった。キーワードがコンテンツだけでなくタイトルでも一致する場合、より関連性の高い検索結果とみなされる。
フックのドキュメンテーション
オープンソースソフトウェアであるWordPressはフリーであり、ソースコードは誰でも利用、修正、研究、構築することができます。WordPressのコードはすべてすでにドキュメンテーションされていますが、新しいフックもたくさんあります。
コアチームは、コアのすべてのフックのインラインドキュメンテーションを合理化することを決定しました。これにより、新規開発者がコードを学び、学習し、練習することが容易になります。また、経験豊富な開発者が自分の WordPress アプリケーションのためによりよいコードを書くのにも役立つでしょう。
WordPress 3.7は現在ベータ版であり、新機能が追加される可能性はほとんどありません。しかし、最終リリースが異なるものになる可能性はあります。ベータ版を試したい場合は、ローカルサーバー環境にWordPressをインストールし、ベータテスタープラグインを実行することで可能です。
どの機能が一番楽しみですか？WordPress 3.7の好きなところ、嫌いなところを以下にコメントしてください。
Syed Balkhi says
Hey WPBeginner readers,
Did you know you can win exciting prizes by commenting on WPBeginner?
Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
You can get more details about the contest from here.
Start sharing your thoughts below to stand a chance to win!
Kris says
Change your picture “new password meter” arrow directions. WordPress 3.7 should be very weak, not WP 3.6.
WPBeginner Support says
@Kris Thank you for pointing this out. We have updated the screenshot.
管理者
Hunky says
I have been updating it with one click, most plug-ins and themes never needed any attention for update so i dont think its a bad feature.
I welcome it,
better would have been an API which should have allowed the plug-ins and themes too receive auto update from their new releases.
One thing would have been appreciated and that is a feature like Windows system restore or Apple time machine where a restore point should be created and saved for user to revert back the changes with single click, if things are broken by chance.
Imad Daou says
I believe we need a sandbox for plugins before activation. It would be great if I can test the plugin before I activate it, especially if this plugin would conflict with other plugin or code.
Performance meter to monitor every code or plugin you add, that would be great to measure the impact on performance after installing specific plugin and how can this be related to server performance as well.
Maybe because I’m new to wordpress, but I found it very hard to find the right theme. I recommend a wizard like method, ask the user few question about their website needs and popups the most related themes for the requirements.
Finally, a setup wizard once you install wordpress would be lovely to new users once they login for the first time, especially if starts with tutorials to educate users about security and to pick the most proper settings. I think we need something similar to what Servers usually have: Roles! is a perfect word for that. WordPress can do a lot of things, it would be great to setup wordpress based on Roles, Roles might have suggestion for specific themes and plugins!
I’m so happy with WordPress and especially WPbeginner site , I wish you Happy Eid and very Blessed Future.
All my Best,
Imad Daou
Pace says
I think the minor auto update is a fantastic feature. I’m looking forward to all these features actually. Great news, thanks!
olly connelly says
WordPress bloggers, with good intention, tend to tell us to always update, “asap dammit!”, upon a core update being available. That can be bad advice leading to broken sites, as we casually hack ourselves, effectively, due to incompatibilities from unkempt plugins, old themes and the like.
This auto-updates thing will be terrific for casual bloggers with very few plugins and a basic theme …
… but beware, everyone else, of the potential for a broken site when opting for this feature.
I wrote something or other about this update business, BTW, and why ** it is not best advice to tell people to update the WordPress core, verbatim, ** without explaining the possible pitfalls and proper procedure. Please excuse the plug but I hope that’s handy …
“Updating WordPress: Think First, Here’s Why”: http://wpcop.com/updates
For auto-updates, in addition to this welcome new function, what would be really cool would be:-
– an option of a middle approach, too, allowing us to set how long after a core update to wait before updating. That would allow potentially incompatible plugins to be updated (hopefully!) so that the core update then goes without a hitch
– a further option, whereby the admin can choose auto-updates to be committed (again however long after the update becomes available) ONLY depending on the kind of update it is
Regarding that latter point, for example, if WordPress has a snazzy new feature update, we could opt not to auto-update as those updates tend to be most likely to break a site. But if the update is security-related then, hey, maybe we’d want that to auto-update although, again, perhaps with a delay option.
You could take this update option feature even further, because as we know some security updates are critical (as was 3.6.1, confronting XSS vulnerabilities, for one thing) while most are relatively minor. (This is not to say they should not be addressed as a priority. Hardly.)
This all brings me back to one of my pet hopes: that Automattic separates out security fixes from any other updates, again to reduce (greatly) the number of post-updated, broken sites.
Verdict: if in doubt, be old-fashioned, don’t use this (nonetheless important) feature. Instead always explore each and every WordPress update and, ideally, test it on your cloned development site before deploying it on your production site.
WPBeginner Support says
We disagree with the argument as the main point of the argument is that people hack into their core files and an update could result into broken sites.
First of all users should never hack into the core WordPress files, or core files of any plugins. If they are making changes to a plugin they should rename that plugin so that updates don’t affect it. Same goes for themes, you should always use a child theme to make changes or rename the theme so that it does not get updates for the original theme. As for WordPress core files, there is no reason to hack into them. If you want to make changes into core files you can try to submit them as patches, report bugs, or try to implement your changes in a plugin without touching the core files.
On the other hand auto-updates can be disabled and users can choose to manually update their WordPress sites. This way they can have the time to get their changes saved as a back up and safely update to a new version.
管理者
olly connelly says
(Sorry for delay, just saw this, I daresay an even more important topic for many now … who have broken their sites!)
“the main point of the argument is that people hack into their core files”
Well, that sure wasn’t my argument
Never said a word about it. Irrelevant. **Never edit core files!**
Auto updates add the potential to break sites. Period.
(The stats so far would be interesting.)
olly connelly says
“On the other hand auto-updates can be disabled and users can choose to manually update their WordPress sites”
Yes. Good idea. For sites that matter … way to go!
Daniel Dogeanu says
Ugh… No! What are they thinking?!?! Auto-updates turned on by default? I struggle not to brake the site on every update and they’re implementing it automatically? Come on… If all plugins would keep updating at the right time, it would be ok, but sadly we don’t live in a perfect world. This feature will ruin a lot of sites. And I mean A LOT of sites…
WPBeginner Support says
In 3.7 auto updates will only be open for minor releases. There is no default auto update option for themes and plugins. We think its quite safe and the core team seems to be quite confident about it.
管理者
Kennth Guinto says
I think the auto update feature is geared towards security and minor releases. there is no need to worry much about breaking your site. do also take note that WP 3.7 and WP 3.8 are being developed simultaneously so if all plans go by schedule WP 3.7 would be one shortest stable release that WordPress had in terms of duration. people can read more about it at the core discussion page at wordpress (dot) org
Thomas Varghese says
The new features are good and waiting to see the new changes but i too think there should be some facility provided by wordpress for backup and restore without making any use of plugin for this process. Also automatic updates are fine until it doesn’t mess up the theme on the live site.
Gene says
Happy to hear about this!
Jason Skinner says
They will probably give you the ability to bypass auto updates.
Bjarni Wark says
Anything that improves the default search, good to see this is getting some attention, good work allround.
Grant says
Do you know the date of the release yet?
WPBeginner Support says
Last we heard it was 14 October.
管理者
Alan Hughes says
Having a secure website won’t matter when an auto update crashes it.
Omega says
I wished for this feature exist some time ago… now i’m glad to know that I can focus on other task instead of go and update all the sites when there are new releases.
( Nice post btw )
Sai Varun KN says
WordPress 3.7 should have a inbuilt backup and restore functionality atleast. Automatic updates is good to keep the wordpress safe.
Sergiu Poenaru says
Yup, that would be useful.
Mike says
I vote for the backup feature too. It is unthinkable not to have a full blown backup feature built in.
Greg says
New security is good. But if I have less control over my site (auto updates), that sometimes makes me feel less secure for my site. Security is about consciousness and control (what goes in and out).
Other than that, it sounds good. I like the idea of giving more input on hooks. Hooks are what make WordPress great customizable.
Dave Navarro says
I really wish they’d fix the AUDIO support from 3.6. The Audio Player lacks the ability to include title/track information and control of the size. It doesn’t play nice with images and floating DIVs.