WordPress 3.6 yayınlanalı sadece iki ay oldu ve WordPress 3.7 neredeyse hazır durumda. Bu sürümün 14 Ekim 2013 tarihinde yayınlanması planlanıyor. Size doğru gelen bazı önemli değişiklikler var. WordPress 3.7 temel olarak WordPress çekirdeğinin güvenliği ve kararlılığına odaklanacak. WordPress 3.7’de hangi yeni özelliklerin geleceğine bir göz atalım.
Otomatik Güncellemeler
WordPress 3.7’nin en çok beklenen özelliklerinden biri de otomatik güncellemeler. Yönetilen WordPress barındırma sağlayıcıları, yeni bir güncelleme mevcut olduğunda kullanıcıları için otomatik WordPress güncellemeleri yapıyor.
Artık WordPress bunu kendi başına yapabilecek. Tipik bir WordPress kurulumu, herhangi bir kullanıcı girişi olmaksızın minör/güvenlik sürümlerini otomatik olarak güncelleyebilecektir. Bu, bir kullanıcının WordPress’i 3.7’den 3.7.1’e güncellemesine gerek olmadığı anlamına gelir. Ancak, otomatik güncellemeler varsayılan olarak büyük sürümler için yapılmayacaktır, örneğin 3.7.1’den 3.8’e.
Twitter ve Facebook sayfalarımızı kullanarak izleyicilerin bu konudaki görüşlerini sorduğumuzda, kullanıcılardan karışık bir yanıt aldık. Bazıları gerçekten beğendi, bazıları ise kesinlikle nefret etti. Bu nedenle wp-config.php dosyasından otomatik güncellemeleri kapatma seçeneği olacak. Ayrıca wp-config.php dosyasına bir tanımlama parametresi ekleyerek süreci tamamen otomatikleştirme ve hatta WordPress’i ana sürümlere otomatik olarak güncelleme seçeneği de olacak.
Dil Paketleri
WordPress 3.7 ayrıca dil paketleri için daha iyi bir destekle birlikte gelecek. WordPress 3.7 için belirlenen mevcut hedef, varsayılan temalar, ithalatçı eklentileri ve WordPress çekirdeği için dil dosyalarını ayrı ayrı korumaktır. Kullanıcılar için bu, WordPress’i kendi dilinizde kullanıyorsanız, her güncellemede WordPress’in varsayılan temalar, ithalatçı eklentileri ve çekirdek için dil dosyalarını otomatik olarak getireceği anlamına gelir.
Şu anda kullanıcıların çeviriye hazır bir WordPress teması bulmaları ve dil dosyalarını yüklemeleri gerekiyor. Umarız bu özellik diğer tema ve eklentileri de kapsayacak şekilde genişletilir ve böylece kullanıcılar kullandıkları her eklenti için çeviri dosyalarını indirme ve yükleme konusunda endişelenmek zorunda kalmazlar.
Yeni Şifre Ölçer
Güçlü parola WordPress güvenliği için önemlidir. Bu nedenle WordPress bir parola gücü ölçer ile birlikte gelir, ancak bu çok zayıftır. Bu nedenle WordPress 3.7’de çekirdek ekip, kullanıcıları daha güçlü parolalar seçmeye teşvik edecek yeni bir parola ölçer eklemeye karar verdi.
Bu, yöneticilerin kullanıcıları güçlü parolalar kullanmaya zorlamak için kullanabilecekleri güçlü parolaları zorla eklentisi ile harika bir ek olacaktır.
Geliştirilmiş WordPress Arama
Kabul edelim, varsayılan WordPress araması en iyisi değil. Bu nedenle birçok kullanıcı siteleri için SearchWP veya hatta Google özel arama gibi diğer çözümlere güveniyor.
Neyse ki WordPress 3.7 ile varsayılan arama biraz daha iyi hale gelecek. WordPress artık arama sonuçlarını ters kronolojik sıralama yerine alaka düzeyine göre gösterecek. Anahtar kelime hem başlıkta hem de içerikte eşleşiyorsa, bir sonucu daha alakalı olarak değerlendirecektir.
Kancalar için Satır İçi Dokümantasyon
Açık kaynaklı bir yazılım olarak WordPress ücretsizdir ve kaynak kodu herkesin kullanması, değiştirmesi, incelemesi ve üzerine inşa etmesi için mevcuttur. Tüm WordPress kodu zaten belgelenmiştir, ancak birçok yeni kanca mevcuttur.
Çekirdek ekip, çekirdekteki tüm kancalar için satır içi dokümantasyonu düzenlemeye karar verdi. Bu, yeni geliştiricilerin kodu incelemesini, öğrenmesini ve pratik yapmasını kolaylaştıracaktır. Ayrıca deneyimli geliştiricilerin kendi WordPress uygulamaları için daha iyi kod yazmalarına yardımcı olacaktır.
WordPress 3.7 şu anda Beta sürümünde ve yeni özelliklerin eklenmesi ihtimali çok düşük. Ancak yine de nihai sürümün farklı olması mümkündür. Beta sürümünü denemek istiyorsanız, WordPress’i yerel sunucu ortamına kurarak ve beta tester eklentisini çalıştırarak bunu yapabilirsiniz.
En çok hangi özelliği dört gözle bekliyorsunuz? WordPress 3.7 hakkında beğendiğiniz veya beğenmediğiniz şeyleri aşağıya yorum bırakarak bize bildirin.
Syed Balkhi
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
Change your picture “new password meter” arrow directions. WordPress 3.7 should be very weak, not WP 3.6.
WPBeginner Support
@Kris Thank you for pointing this out. We have updated the screenshot.
Yönetici
Hunky
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
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
I think the minor auto update is a fantastic feature. I’m looking forward to all these features actually. Great news, thanks!
olly connelly
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
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.
Yönetici
olly connelly
(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
“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
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
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.
Yönetici
Kennth Guinto
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
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
Happy to hear about this!
Jason Skinner
They will probably give you the ability to bypass auto updates.
Bjarni Wark
Anything that improves the default search, good to see this is getting some attention, good work allround.
Grant
Do you know the date of the release yet?
WPBeginner Support
Last we heard it was 14 October.
Yönetici
Alan Hughes
Having a secure website won’t matter when an auto update crashes it.
Omega
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
Wordpress 3.7 should have a inbuilt backup and restore functionality atleast. Automatic updates is good to keep the wordpress safe.
Sergiu Poenaru
Yup, that would be useful.
Mike
I vote for the backup feature too. It is unthinkable not to have a full blown backup feature built in.
Greg
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
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.