![]() ![]() Hari ini saya kembali mengupgrade Wordpress ke versi 2.7 untuk blog ini. Kesan pertama, keren habis. Menu pada dashboard diletak disebelah kiri, semakin interaktif. Mark Jaquith has just announced that WordPress 2.7 is. WordPress 2.7 using WP automatic upgrade plugin. Quick Divi Theme Tutorial. Ill show you how to update the your current version of the divi theme on wordpress to divi 3.0. The first thing you need to do is get the elegant themes updater plugin. You can get it here at this page You can purchase the divi through my and get 20% off the regular price. Its a limited time. I have no idea when the elegant theme sale ends but i would purchase asap! Get 20% OFF Divi Theme Limited Time!: Try the new visual page builder for FREE: For more tutorials like this or to learn how to create your own wordpress website, feel free to visit my website. What do you see when you go to Tools -> Upgrade? If there the only suggested version is a local one you will be able to hide it. Some more clarifications follow. There are two ways to localize WordPress: • Drop some translation files. ![]() ![]() • Install localized package. Whenever possible we try to enforce the 2nd way. So, here is how the whole thing works: • Both the current locale and the current localized package, installed, are sent to the API. • If a localized package for the user's locale is available and the user doesn't have the localized package, the user is prompted to upgrade or to hide updgrade. I would be happy if somebody proposes a better way to communicate this behaviour interface-wise. Denis, let's take the following case: you have a Wordpress 2.7.1 with a German MO file. Then the German local package is released. What should we do? • Don't show a upgrade notice at all. This way the user may be running a old MO file and may not know how to get the new translaiton. In this case we won't confuse the user. I don't think that's the acceptable solution. We should encourage users to upgrade to local versions. • Show the upgrade notice. Either if we show the Hide button or we don't, we confuse the user. I preferred the former, because it's not so hard to let the user make an informed decision about hiding the local upgrade. Quite honestly, I'd be curious to know how long it takes for the mo file to get updated. For what it's worth, here's what I do with my customers: I disable WP update notifications entirely. Only when a new version of Semiologic Pro is around (usually a week or two later), do they receive a notification. That way, they're not confused into upgrading WP when the latter can potentially break the plugins that they use. Once I make sure everything works fine do they see a nag in their admin area. And Tools / Upgrade will conveniently let them upgrade WP, and my themes, and my plugins, all in one go. Now, I arguably don't maintain mo files, but it seems to me that localized versions of WP should behave more or less the same, at least until a reasonably long amount of time has elapsed. As long as their install can potentially 'break' (in the sense that it won't show captions in their preferred language), they should not see the nag. When Tools / Upgrade will give the correct mo file alongside WP, they should get the nag. Arguably, some mo files might be dropped at some point from lack of support by translation teams. For this reason, we could consider that a week or two after the initial WP update is a long enough delay. If the mo isn't done by then, we could consider that nobody is maintaining the mo file. Along the same lines, it might make sense to only enforce the above-mentioned behavior for major updates (e.g. 2.6 to 2.7), and not for minor ones (2.6 to 2.6.1). After all, minor updates are frequently security related, and it's better to have wrong caption or two than a hopelessly hacked site. Replying to: Quite honestly, I'd be curious to know how long it takes for the mo file to get updated. It depends entirely on each locale's team. Some team try to make sure the locale version is available in the hours following the release of WP, while other teams catch up in the following weeks, even months sometimes. For this reason, we could consider that a week or two after the initial WP update is a long enough delay. If the mo isn't done by then, we could consider that nobody is maintaining the mo file. We can't work that way. A team should not be dropped just because they are slower than others. I'd rather have a team working at their pace on a translation, than no team at all. To each his own.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
July 2018
Categories |