People of WordPress: Ugyen Dorji

You’ve probably heard that WordPress is open source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories.

Meet Ugyen Dorji from Bhutan

Ugyen lives in Bhutan, a landlocked country situated between two giant neighbors, India to the south and China to the north. He works for ServMask Inc and is responsible for the Quality Assurance process for All-in-One WP Migration plugin.

He believes in the Buddhist teaching that “the most valuable service is one rendered to our fellow humans,” and his contributions demonstrates this through his WordPress translation work and multi-lingual support projects for WordPress.

Bhutanese contributors to the Dzongkha locale on WordPress Translation Day

How Ugyen started his career with WordPress

Back in 2016, Ugyen was looking for a new job after his former cloud company ran into financial difficulties.

During one interview he was asked many questions about WordPress and, although he had a basic understanding of WordPress, he struggled to give detailed answers. After that interview he resolved to develop his skills and learn as much about WordPress as he could. 

A few months passed and he received a call from ServMask Inc, who had developed a plugin called All-in-One WP Migration. They offered him a position, fulfilling his wish to work with WordPress full-time. And because of that, Ugyen is now an active contributor to the WordPress community.

WordCamp Bangkok 2018

WordCamp Bangkok 2018 was a turning point event for Ugyen. WordCamps are a great opportunity to meet WordPress community members you don’t otherwise get to know, and he was able to attend his first WordCamp through the sponsorship of his company.

The first day of WordCamp Bangkok was a Contributor Day, where people volunteer to work together to contribute to the development of WordPress. Ugyen joined the Community team to have conversations with WordPress users from all over the world. He was able to share his ideas for supporting new speakers, events and organizers to help build the WordPress community in places where it is not yet booming.

During the main day of the event, Ugyen managed a photo booth for speakers, organizers, and attendees to capture their memories of WordCamp. He also got to take some time out to attend several presentations during the conference. What particularly stuck in Ugyen’s mind was learning that having a website content plan has been shown to lead to 100% growth in business development.

Co-Organizing Thimphu‘s WordPress Meetup

After attending WordCamp Bangkok 2018 as well as a local Meetup event, Ugyen decided to introduce WordPress to his home country and cities. 

As one of the WordPress Translation Day organizers, he realized that his local language, Dzongkha, was not as fully translated as other languages in the WordPress Core Translation. That is when Ugyen knew that he wanted to help build his local community. He organized Thimphu’s first WordPress Meetup to coincide with WordPress Translation Day 4, and it was a huge success!

Like all WordPress Meetups, the Thimpu WordPress Meetup is an easygoing, volunteer-organized, non-profit meetup which covers everything related to WordPress. But it also keeps in mind the Bhutanese Gross National Happiness four pillars by aiming to preserve and promote their unique culture and national language. 

Big dreams get accomplished one step at a time

Ugyen has taken an active role in preserving his national language by encouraging his community to use WordPress, including Dzongkha bloggers, online Dzongkha news outlets, and government websites.

And while Ugyen has only been actively involved in the community for a short period, he has contributed much to the WordPress community, including:

  • becoming a Translation Contributor for WordPress Core Translation for Dzongkha;
  • participating in the Global WordPress Translation Day 4 Livestream and organizing team;
  • inviting WordPress Meetup Thimphu members and WordPress experts from other countries to join the local Slack instance;
  • encouraging ServMask Inc. to become an event sponsor;
  • providing the Dzongkha Development Commission the opportunity to involve their language experts.

When it comes to WordPress, Ugyen particularly focuses on encouraging local and international language WordPress bloggers; helping startups succeed with WordPress; and sharing what he has learned from WordPress with his Bhutanese WordPress community.

As a contributor, Ugyen hopes to accomplish even more for the Bhutan and Asian WordPress Communities. His dreams for his local community are big, including teaching more people about open source, hosting a local WordCamp, and helping to organize WordCamp Asia in 2020 — all while raising awareness of his community.


This post is based on an article originally published on HeroPress.com, a community initiative created by Topher DeRosia. HeroPress highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.

Meet more WordPress community members over at HeroPress.com!

Source

WordPress 5.2 “Jaco”

Keeping Sites Safer

Version 5.2 of WordPress, named “Jaco” in honor of renowned and revolutionary jazz bassist Jaco Pastorius, is available for download or update in your WordPress dashboard. New features in this update make it easier than ever to fix your site if something goes wrong.

There are even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.


Site Health Check

Building on the Site Health features introduced in 5.1, this release adds two new pages to help debug common configuration issues. It also adds space where developers can include debugging information for site maintainers.

PHP Error Protection

This administrator-focused update will let you safely fix or manage fatal errors without requiring developer time. It features better handling of the so-called “white screen of death,” and a way to enter recovery mode,  which pauses error-causing plugins or themes.


Improvements for Everyone

Accessibility Updates

A number of changes work together to improve contextual awareness and keyboard navigation flow for those using screen readers and other assistive technologies.

New Dashboard Icons

Thirteen new icons including Instagram, a suite of icons for BuddyPress, and rotated Earth icons for global inclusion. Find them in the Dashboard and have some fun!

Plugin Compatibility Checks

WordPress will now automatically determine if your site’s version of PHP is compatible with installed plugins. If the plugin requires a higher version of PHP than your site currently uses, WordPress will not allow you to activate it, preventing potential compatibility errors.


Developer Happiness

PHP Version Bump

The minimum supported PHP version is now 5.6.20. As of WordPress 5.2*, themes and plugins can safely take advantage of namespaces, anonymous functions, and more!

Privacy Updates

A new theme page template, a conditional function, and two CSS classes make designing and customizing the Privacy Policy page easier.

New Body Hook

5.2 introduces a wp_body_open hook, which lets themes support injecting code right at the beginning of the <body> element.

Building JavaScript

With the addition of webpack and Babel configurations in the wordpress/scripts package, developers won’t have to worry about setting up complex build tools to write modern JavaScript.

*If you are running an old version of PHP (less than 5.6.20), update your PHP before installing 5.2.


The Squad

This release was led by Matt Mullenweg, Josepha Haden Chomphosy, and Gary Pendergast. They were graciously supported by 327 generous volunteer contributors. Load a Jaco Pastorius playlist on your favorite music service and check out some of their profiles:

aandrewdixon, Aaron D. Campbell, Aaron Jorbin, Adam Silverstein, Adam Soucie, Adil Öztaşer, Ajit Bohra, Alain Schlesser, aldavigdis, Alex Denning, Alex Kirk, Alex Mills, Alex Shiels, Alexis, Alexis Lloyd, allancole, Allen Snook, André, Andrés, andraganescu, Andrea Fercia, Andrea Middleton, Andrei Lupu, Andrew Duthie, Andrew Nacin, Andrew Ozz, Andrey “Rarst” Savchenko, Andy Fragen, Andy Meerwaldt, Aniket Patel, Anton Timmermans, Anton Vanyukov, Antonio Villegas, antonypuckey, Aristeides Stathopoulos, Aslam Shekh, axaak, Bego Mario Garde, Ben Dunkle, Ben Ritner – Kadence Themes, Benjamin Intal, Bill Erickson, Birgir Erlendsson, Bodo (Hugo) Barwich, bonger, Boone Gorges, Bradley Taylor, Brandon Kraft, Brent Swisher, bulletdigital, Burhan Nasir, Cathi Bosco, Chetan Prajapati, Chiara Magnani, Chouby, Chris Van Patten, D.S. Webster, Damon Cook, Daniel Bachhuber, Daniel James, Daniel Llewellyn, Daniel Richards, Daniele Scasciafratte, Darren Ethier (nerrad), Dave Whitley, DaveFX, davetgreen, David Binovec, David Binovec, David Herrera, David Roddick, David Smith, davidb, Davide ‘Folletto’ Casali, dekervit, Denis de Bernardy, Dennis Snell, Derek Herman, Derrick Hammer, designsimply, Dhanukanuwan, Dharmesh Patel, Diane, diegoreymendez, Dilip Bheda, Dima, Dion Hulse, Dixita Dusara, Dmitry Mayorov, Dominik Schilling, Drew Jaynes, dsifford, Ella van Durpe, etoledom, fabiankaegy, Faisal Alvi, Farhad Sakhaei, Felix Arntz, Franklin Tse, Fuegas, Garrett Hyder, Gary Jones, Gennady Kovshenin, Grzegorz (Greg) Ziółkowski, Guido Scialfa, GutenDev ✍㊙, Hannah Malcolm, Hardik Amipara, Hardik Thakkar, Hendrik Luehrsen, Henry, Henry Wright, Hoover, Ian Belanger, Ian Dunn, ice9js, Igor Zinovyev, imath, Ixium, J.D. Grimes, jakeparis, James, janak Kaneriya, Jarred Kennedy, Javier Villanueva, Jay Upadhyay, Jaydip Rami, Jayman Pandya, jdeeburke, Jean-Baptiste Audras, Jeff Paul, Jeffrey de Wit, Jenny, Jeremy Felt, Jeremy Green, Jeremy Herve, jitendrabanjara1991, JJJ, Joe Dolson, Joe McGill, Joen Asmussen, Johan Falk, Johanna de Vos, John Blackbourn, Jonathan Desrosiers, Jonathandejong, Jonny Harris, jonnybojangles, Joost de Valk, jordesign, Jorge Bernal, Jorge Costa, Jory Hogeveen, Jose Castaneda, josephwa, Josh Feck, JoshuaWold, Joy, jplo, JR Tashjian, jrf, Juhi Patel, juliarrr, K. Adam White, KamataRyo, Karine Do, Katyatina, Kelin Chauhan, Kelly Dwan, Khokan Sardar, killua99, Kite, Kjell Reigstad, Knut Sparhell, Koji Kuno, Konstantin Obenland, Konstantinos Xenos, Kʜᴀɴ (ಠ_ಠ), laurelfulford, lkraav, Luke Carbis, Luke Gedeon, Luke Pettway, Maedah Batool, Maja Benke, Malae, Manzoor Wani, Marcin, Marcin Pietrzak, Marco Peralta, marcofernandes, Marcus Kazmierczak, marekhrabe, Marius Jensen, Mariyan Belchev, Mark Uraine, markcallen, Markus Echterhoff, Marty Helmick, marybaum, mattnyeus, mdwolinski, Meet Makadia, Mel Choyce, mheikkila, Micah Wood, michelleweber, Miguel Fonseca, Miguel Torres, Mikael Korpela, Mike Auteri, Mike Schinkel [WPLib Box project lead], Mike Schroder, Mike Selander, MikeNGarrett, Milan Dinić, mirka, Mobin Ghasempoor, Mohadese Ghasemi, Mohammed Saimon, Morten Rand-Hendriksen, Morteza Geransayeh, Muhammad Muhsin, Mukesh Panchal, Mustafa Uysal, mzorz, Nahid F. Mohit, Naoki Ohashi, Nate Allen, Ned Zimmerman, Neokazis Charalampos, Nick Cernis, Nick Diego, Nick Halsey, Nidhi Jain, Niels Lange, nielsdeblaauw, Nikolay Nikolov, Nilambar Sharma, ninio, notnownikki, pandelisz, paragoninitiativeenterprises, Pascal Birchler, Paul Bearne, Paul Biron, Pedro Mendonça, Peter Booker, Peter Wilson, pfiled, pilou69, Pranali Patel, Pratik K. Yadav, Presskopp, psealock, Rachel Cherry, Rahmon, Ramanan, Rami Yushuvaev, Ramiz Manked, ramonopoly, Riad Benguella, Rinat Khaziev, Robert Anderson, Rudy Susanto, Ryan Boren, Ryan Welcher, Saeed Fard, Sal Ferrarello, Samaneh Mirrajabi, Sami Keijonen, Samuel Elh, Santiago Garza, Sara Cope, saracup, sarah semark, Sebastian Pisula, Sekineh Ebrahimzadeh, Sergey Biryukov, SergioEstevao, sgastard, sharifkiberu, shazdeh, Shital Marakana, sky_76, Soren Wrede, Stephen Edgar, Steven Word, Subrata Sarkar, Sudar Muthu, Sudhir Yadav, szepe.viktor, Takayuki Miyauchi, Tammie Lister, Themonic, thomstark, Thorsten Frommen, Thrijith Thankachan, Tim Hedgefield, Tim Wright, Timothy Jacobs, timph, tmatsuur, tmdesigned, tmdesigned, Tobias Zimpel, TomHarrigan, Tor-Bjorn Fjellner, Toro_Unit (Hiroshi Urabe), torres126, Torsten Landsiedel, Towhidul Islam, Tracy Levesque, Umang Bhanvadia, Vaishali Panchal, WebFactory, Weston Ruter, William ‘Bahia’ Bay, William Earnhardt, williampatton, Willscrlt, Wolly aka Paolo Valenti, wrwrwr0, Yoav Farhi, Yui, and zebulan.

Also, many thanks to all of the community volunteers who contribute in the support forums. They answer questions from people across the world, whether they are using WordPress for the first time or since the first release. These releases are more successful for their efforts!

If you want learn more about volunteering with WordPress, check out Make WordPress or the core development blog.

Thanks for choosing WordPress!

Source

WordPress 5.2 Beta 3

WordPress 5.2 Beta 3

WordPress 5.2 Beta 3 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

There are two ways to test the latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 2, nearly 40 tickets have been closed since then. Here are the major changes and bug fixes:

  • The new Site Health feature has continued to be refined.
  • Plugins no longer update if a site is running an unsupported version of PHP (see #46613).
  • It’s now more apparent when a site is running in Recovery Mode (see #46608).
  • The distraction free button no longer breaks keyboard navigation in the Classic Editor (see #46640).
  • Assistive technologies do a better job of announcing admin bar sub menus (see #37513).
  • Subject lines in WordPress emails are now more consistent (see #37940).
  • Personal data exports now only show as completed when a user downloads their data (see #44644).
  • Plus more improvements to accessibility (see #35497 and #42853).

Minimum PHP Version Update

Important reminder: as of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.

Developer Notes

WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 3 release also marks the soft string freeze point of the 5.2 release schedule.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.


Would you look at that
each day brings release closer
test to be ready
.

WordPress

via News – – WordPress.org

April 12, 2019 at 02:42PM

WordPress 5.2 Beta 2

WordPress 5.2 Beta 2 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

There are two ways to test the WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 1, nearly 100 tickets have been closed since then. Here are the major changes and bug fixes:

  • We’ve added support for Emoji 12! 🪂
  • A brand-new wp_body_open() template tag (and corresponding wp_body_open action) will let themes (and plugins!) add content right after the <body> is opened (#12563).
  • Superfluous paragraph tags will no longer incorrectly appear in dynamic block content (#45495).
  • The Site Health screens have received several bug fixes, tweaks, and performance improvements.
  • Crash Protection no longer interrupts plugin editing (#46045).
  • Custom error handlers now load correctly (#46069).

Minimum PHP Version Update

As of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.

Developer Notes

WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.


The wonderful thing
about betas, is betas
are wonderful things.
🐯

Source

Minimum PHP Version update

WordPress 5.2 is targeted for release at the end of this month, and with it comes an update to the minimum required version of PHP. WordPress will now require a minimum of PHP 5.6.20.

Beginning in WordPress 5.1, users running PHP versions below 5.6 have had a notification in their dashboard that includes information to help them update PHP. Since then, the WordPress stats have shown an increase in users on more recent versions of PHP.


Screenshot of the "PHP Update Required" widget from the WordPress dashboard. Contains information about detecting an insecure version of PHP, how it affects your site, and a link for information on upgrading.
The dashboard widget users see if running an outdated version of PHP

Why You Should Update PHP

If your site is running on an unsupported version of PHP, the WordPress updater will not offer WordPress 5.2 to your site. If you attempt to update WordPress manually, that update will fail. To continue using the latest features of WordPress you must update to a newer version of PHP.

When updating to a new version of PHP, WordPress encourages updating to its recommended version, PHP 7.3. The PHP internals team has done a great job making its most recent version the fastest version of PHP yet. This means that updating will improve the speed of your site, both for you and your visitors.

This performance increase also means fewer servers are needed to host websites. Updating PHP isn’t just good for your site, it also means less energy is needed for the 1-in-3 sites that use WordPress, so it’s good for the planet.

How to Update PHP

If you need help updating to a new version of PHP, detailed documentation is available. This includes sample communication to send to your host for them to assist you. Many hosting companies have published information on how to update PHP that is specific for them.

5.6 now, but soon 7+

This is the first increase in PHP required version for WordPress since 2010, but may not be the only increase in 2019. The WordPress core team will monitor the adoption of the most recent versions of PHP with an eye towards making PHP 7+ the minimum version towards the end of the year.

Update PHP today, so you can update WordPress tomorrow!

Source

What’s Coming in WordPress 5.2 (Features and Screenshots)

What’s Coming in WordPress 5.2 (Features and Screenshots)

WordPress 5.2 is expected to be released by the end of April 2019. We have been following the development and tested the first beta to try out new features that are on the way.

This release will bring improvements to the block editor, site health check, several bug fixes and minor enhancements.

In this article, we will show you what’s coming in WordPress 5.2 with features and screenshots.

What is coming in WordPress 5.2

Note: You can try out the beta version on your computer or on a staging environment by using the WordPress Beta Tester plugin.

WordPress 5.2 is still under development, which means some features may not make it to the final release.

That being said, let’s take a look at some of the upcoming features in WordPress 5.2.

Improved Fatal Error Protection in WordPress

The most common WordPress errors are usually fatal errors that stop users from accessing the admin dashboard.

Users are then required to undo changes using an FTP client or ask their hosting company for support.

WordPress 5.2 introduces a new recovery mode for site administrators. In case of a fatal error, you will see a message that ‘This site is experiencing technical difficulties’.

Technical difficulties error in WordPress 5.2

WordPress will then send an email to the admin email address with a special login link.

Using that link, you will be able to login to the WordPress admin area. After that, you can undo any changes that may have triggered the fatal error.

This feature will be a blessing for many beginners who find it quite difficult to fix such errors.

Block Editor Updates in WordPress 5.2

The WordPress block editor (Gutenberg) was introduced in WordPress 5.0. Since then there has been continuous development on the block editor to further improve it.

WordPress 5.2 will continue that with some new features and enhancements to the block editor.

Performance Improvements

The new WordPress block editor is much faster than the older classic editor. However, it could get slower when editing lengthier blog posts with tons of blocks.

WordPress 5.2 addressed that with significant performance improvements.

It will now shave 35% off the load time for massive posts. WordPress 5.2 will also cut the keypress time in half, which would make it feel way more responsive when you are typing.

Accessibility Improvements

The goal of WordPress is to democratize publishing and making the software accessible for all users. WordPress 5.2 will bring several accessibility improvements to the block editor.

  • The block editor will now support reduced motion settings in user’s browser.
  • The post URL slug will have better labeling and help text, which will make it easier to locate.
  • Block editor will have a clearer and consistent focus styling for keyboard navigating through landmarks.
  • WordPress 5.2 will also bring improved screen-reader experience with new speak messages. Existing speak messages are also improved to be clearer.

Introduction of New Blocks

WordPress 5.2 will also introduce the following new blocks in the default editor. Some of them were already available as Widgets, but now you can use them in posts and pages as well.

  • RSS block – It will allow you to easily fetch and display any RSS feed in your WordPress posts and pages.
  • Amazon Kindle embed block – Allows you to embed content from Amazon Kindle
  • Search block – Add the default WordPress search feature in your content.
  • Calendar block – Displays a calendar of your blog posts allowing users to click on a date to view posts published on that day.
  • Tag Cloud block – Displays the tag cloud in your content.

A New Block Manager Tool

By default, the block editor comes with several default blocks. You also have plugins and themes adding their own blocks as well.

However, the reality is that you’ll probably never use all those blocks. Most users usually stick to a handful of blocks for writing all their content.

WordPress 5.2 will introduce a new block management tool, which will allow you to hide blocks that you don’t want to use.

Launching the new block manager in WordPress 5.2

The block manager will list all the blocks that you have available on your site. You can simply uncheck the blocks that you don’t want to use.

The new block manager in WordPress

The Minimum PHP Version Requirement

WordPress is used by millions of people from all over the world, using different hosting companies, and hosting environments.

This is why WordPress still supports some older PHP versions, which is a bit problematic. Users may not even realize that they can improve the performance of their website by using a newer PHP version.

WordPress 5.2 will set the current minimum required PHP version to 5.6, which is still old (current stable PHP version is 7.3.2). The goal is to gradually increase the minimum required PHP version with future releases.

Users on the older versions of PHP will see a notification, that they are using an older PHP version and need to update it.

PHP version notice in WordPress 5.2 beta

Under The Hood Improvements in WordPress 5.2

These are the changes in WordPress 5.2 which will mostly affect developers.

Users will be able to provide a log file path when adding WP_DEBUG_LOG in wp-config.php file. #18391.

Plugins will be able to specify the minimum required PHP version. #40934

Dashicons, the default icon font used for the WordPress admin area will have 25 new icons to use. #41074

We hope this article gave you a glimpse of what’s coming in WordPress 5.2. Let us know which features you find interesting and what new features you would like to see in the future.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post What’s Coming in WordPress 5.2 (Features and Screenshots) appeared first on WPBeginner.

WordPress

via WPBeginner

April 1, 2019 at 05:11AM

WordPress 5.2 Beta 1

WordPress 5.2 Beta 1 is now available!

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

You can test the WordPress 5.2 Beta two ways:

WordPress 5.2 is slated for release on April 30, and we need your help to get there. Here are some of the big items to test so we can find as many bugs as possible in the coming weeks.

Block Editor

The block editor has received significant performance improvements since WordPress 5.1, shaving 35% off the load time for massive posts, and cutting the keypress time (how responsive it feels when you’re typing) in half!

Accessibility continues to improve, too. The block editor now supports your browser’s reduced motion settings. The post URL slug has better labelling and help text. The focus styling for keyboard navigating through landmarks is clearer and more consistent. There are a variety of new speak messages, and existing messages have been tweaked for more useful screen-reader behaviour.

We’ve added several new blocks:

  • An RSS block
  • An Amazon Kindle embed block
  • A Search block
  • A Calendar block
  • A Tag Cloud block

To help you keep track of these blocks, and only show the ones you need, there’s a new block management tool to switch blocks on and off.

Block Management Modal

We’re constantly working on existing blocks, too. There are hundreds of bug fixes and improvements in the block editor, you can read more about them in the Gutenberg plugin releases: 4.9, 5.0, 5.1, 5.2, and 5.3.

The WordPress Mobile Apps

The block editor isn’t just for websites, either. The WordPress mobile apps now include an experimental version of a built-in block editor. This is still under development, but you can try it out now!

Site Health Check

Site Health Check is an ongoing project aimed at improving the stability and performance of the entire WordPress ecosystem.

The first phase of this project (originally scoped for WordPress 5.1) is now included in WordPress 5.2. For the first time, WordPress will catch and pause the problem code, so you can log in to your Dashboard and see what the problem is (#44458). Before, you’d have to FTP in to your files or get in touch with your host.

In addition, we’re adding a new Health Check tool to your Dashboard. Visit the Tools menu and click on Health Check to get information that can help improve the speed and security of your site.

PHP Version Bump

With this release, WordPress will increase its minimum supported PHP version to 5.6. To help you check if you’re prepared for this change, WordPress 5.2 will show you a warning and help you upgrade your version of PHP, if necessary.

For Developers

  • Plugins can now specify the minimum version of PHP that they support, so you can safely modernise your development practices without risking breaking your users’ sites. (#40934)
  • We’ve added the sodium_compat library, which provides backwards compatibility for the Sodium-based cryptography library added in PHP 7.2. (#45806)
  • There’s a new release of Dashicons, the WordPress Dashboard icon font. There are 25 new icons for you to use! (#41074)
  • You can now pass a label to get_search_form(), improving accessibility. (#42057)

There have been 130 tickets closed in WordPress 5.2 so far, with numerous small bug fixes and improvements to help smooth your WordPress experience.

Keep your eyes on the Make WordPress Core blog for developer notes (which are assigned the dev-notes tag) in the coming weeks detailing other changes in 5.2 that you should be aware of.

How to Help

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.


With each new release,
bearing multiple betas;
We fix, then we fly.

Source

Python Insider: Python 3.8.0a3 is now available for testing

Python Insider: Python 3.8.0a3 is now available for testing

Go get it here:
https://www.python.org/downloads/release/python-380a3/

The most visible change so far is probably the implementation of PEP 572: Assignment Expressions.  For a detailed list of changes, see:
https://docs.python.org/3.8/whatsnew/changelog.html

Python 3.8.0a3 is the third of four planned alpha releases of Python 3.8, the next feature release of Python.  During the alpha phase, Python 3.8
remains under heavy development: additional features will be added and existing features may be modified or deleted.  Please keep in mind that this is a preview release and its use is not recommended for production environments.  The last alpha release, Python 3.8.0a4, is planned for 2019-04-29.

Thanks
to all of the many volunteers who help make Python development and these releases possible!  Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.

Python

via Planet Python

March 26, 2019 at 03:48AM

The Month in WordPress: February 2019

A new version of WordPress, significant security enhancements, important discussions, and much more – read on to find out what has been going on in the WordPress community for the month of February. Release of WordPress 5.1 Near the end of the month, WordPress 5.1 was released , featuring significant stability and performance enhancements as well as the first of the Site Health mechanisms that are in active development.

Source: The Month in WordPress: February 2019