Wordpress News

WPTavern: WPWeekly Episode 352 – Capital P Dangit and My Future Plans

Wordpress Planet - Tue, 05/14/2019 - 21:47

*Update* The previous mp3 attached to this post inadvertently ended around the 31 minute mark. I’ve reuploaded the episode and corrected the problem. The full episode is attached below.

In this episode, John James Jacoby and I share what’s new in WordPress 5.2, discuss why not capitalizing one letter can make or break someone in the WordPress community, and what’s new in Jetpack 7.3. We also highlight the highly anticipated release of Advanced Custom Fields 5.8.0.

Near the end of the show, I describe what I’ve been going through the last few months and what you can expect from me going forward. In short, a variety of audio content.

Stories Discussed:

WordPress 5.2 “Jaco” Released, Includes Fatal PHP Error Protection and A Recovery Mode

Registration for WordSesh 6 Is Now Open

New Membership Block Coming to Jetpack, Site Health and Debug Info Added to Version 7.3

Advanced Custom Fields 5.8.0 Introduces ACF Blocks: A PHP Framework for Creating Gutenberg Blocks

WPTracSearch: An Elasticsearch-Powered Search Interface for WordPress Trac Tickets

Transcript:

Transcript of EPISODE 352 – WordPress Weekly

WPWeekly Meta:

Next Episode: Wednesday, May 22nd 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #352:

WPTavern: Bear App Adds WordPress Publishing Integration for iOS

Wordpress Planet - Tue, 05/14/2019 - 20:20

For several years, Bear App users have eagerly requested the ability to publish their notes to WordPress. Bear features a zen writing experience blended seamlessly with note-taking capabilities, a combination that landed the app an Apple Design Award in 2017.

People use Bear for everything from taking notes to writing chapters for books. Many users also rely on the app for writing drafts for blogs they plan to publish on other platforms. This often requires multiple steps for copying and pasting content, especially when there is media or HTML included in the content.

Two years ago, the app’s creators had WordPress publishing on their to-do list but it wasn’t yet a priority. They were reluctant to implement their own publishing tool with the WordPress APIs and preferred a solution that would rely on external apps.

Things have changed in the past couple of years, as writing apps have more pressure to provide a frictionless connection to publishing capabilities in order to remain competitive. WordPress’ market share has grown to be an estimated 33% of the the top 10 million websites. In fact, Bear recently moved its blog off of Medium and over to WordPress in February 2019.

This week WordPress.com, maintainers of the open source WordPress mobile apps, and Bear announced that they have collaborated on a solution that allows users to publish notes to WordPress blogs on iOS. Recent updates to both Bear and WordPress apps enable users to click the share icon on a note and see WordPress pop up as an option. The content is shared with all of its formatting, headings, lists, links, and media in tact.

The developers at Shiny Frog, makers of the Bear app, explained the solution they landed on for the WordPress integration:

We built an open source library for processing TextBundle files. TextBundle is an open standard for sharing plain text files that include attachments like photos. WordPress then worked to add TextBundle support to its iOS app. Bear hands your note off to WordPress as a TextBundle file, and WordPress converts it into a blog post.

Using an open standard like this allows other other developers to build on top of it to create their own integrations for other platforms. It also keeps the Bear app team from having to stay up to date with all the changes to APIs of multiple platforms.

The new WordPress publishing integration works with any site you have in the WordPress mobile app for iOS, including both self-hosted and WordPress.com sites. Notes must begin with an H1 tag in order to have the blog post title automatically populated. Bear App users can start publishing to WordPress immediately after updating both apps to the latest versions released this week.

Akismet: Version 4.1.2 of the Akismet WordPress Plugin is Now Available

Wordpress Planet - Tue, 05/14/2019 - 15:06

Version 4.1.2 of the Akismet plugin for WordPress is now available. It contains the following changes:

  • We’ve reduced the number of API requests made by the plugin when attempting to verify the API key.
  • We’re now including additional data in the pingback pre-check API request to help make stats more accurate.
  • We fixed a bug that was enabling the “Check for Spam” button when no comments were eligible to be checked.
  • We’ve improved Akismet’s AMP compatibility.

To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins directory.

WPTavern: The Most Common WordPress Theme Development Mistakes (and How to Fix Them)

Wordpress Planet - Tue, 05/14/2019 - 14:56

Submitting a theme to the WordPress.org theme directory is a great way to share your work and contribute to the WordPress community. Currently, there are over 7000 themes in the directory, the most popular of which exceeds 300,000 active installations. (Not including Twenty____ Themes which are packaged with WordPress and have install counts in the millions.)

Before submitting your theme to the directory, it’s important to understand the review process first because if your theme doesn’t meet those requirements it can be rejected on the spot.

Themes that have 3 or more distinct issues may be closed as not-approved. However, theme authors may resubmit the theme once they’ve corrected the issues.

https://make.wordpress.org/themes/handbook/review/required/

Reviewers are on your side and want to see your theme go live, once it meets the standards required. If your theme has only minor issues preventing it being included in the directory, your reviewer will work with you to fix those.

Unfortunately, if your theme has too many issues it will be closed as not-approved. If you decide to fix the issues you can upload the theme again – but it will join the back of the queue.

From my experience reviewing over 100 themes I’ve been able to identify the most common issues that prevent themes being approved. By sharing these with you in this article I’m hoping I can help you avoid getting stuck in the queue or rejected.

Uploading Your Theme

When you upload a theme, it joins the queue to be reviewed. On average it will take two months for your theme to reach the front of the queue and receive its first review. All reviewers are volunteers with limited time available to complete reviews. A variety of factors can affect the wait time. When more people volunteer to review themes, the queue moves quickly. Conversely, when themes with a lot of issues are submitted it slows down the queue.

By submitting a theme that meets all the requirements it makes the review process a lot smoother and ultimately your theme will be live sooner. In this guide, we are going to explore the most common issues that will keep your theme held up in the queue and prevent it from being approved.

Note: Theme authors that have a track record of submitting issue-free themes can apply to become ‘Trusted Authors‘.

Naming Issues

When you upload a theme, the first check that is performed is to see if the name is already taken. Frequently you will be told the name you’ve chosen is already taken, even if you can’t see a theme with that name in the directory.

How could that be? The reason is that the test isn’t checking against just the directory, it’s checking against the entire WordPress ecosystem. If a theme has been released anywhere (Github, ThemeForest, etc.) and has over 50 active installations, that name will be unavailable to use.

Note: if you’ve released your theme elsewhere and accumulated 50+ installations, you can still use that name in the directory.

Unescaped Output

Theme reviewers take security very seriously, there’s even a dedicated resource. An entire article could be written on writing secure themes, but in this section we are going to explore one aspect: escaping output.

Unescaped output places users of your theme at risk. Here’s an example of an unescaped value ($title):

$title = get_option( 'my_custom_title' ); echo '<h2>' . $title . '</h2>';

The problem with the above is that while we know what type of value $title should be, a string, we have not checked if that is the case.

If a hacker has managed to change the value of ‘my_custom_title’ in the database, your theme will output that value. This presents a huge risk as they could replace the intended output with inline Javascript:

alert('This is dangerous');

The solution is to escape all output to ensure it only includes the type of data we are expecting.

Our example could be fixed like this:

$title = get_option( 'my_custom_title' ); echo '<h2>' . esc_html( $title ) . '</h2>';

The downside to using esc_html is that it strips all HTML tags. If $title included bold or italics, for example:

$title = 'This article is <strong>very</strong> useful'; echo esc_html( $title );

The word ‘very’ would not be bold on the frontend; instead it would output the code <strong>very</strong>.

This illustrates why it’s important to use the correct escaping functions for the context. If we were expecting some HTML in the output, we’d be better using wp_kses_post() or wp_kses() and setting the $allowed_html parameter.

Functions that output also need to be escaped:

<a href="<?php echo esc_url( get_permalink() ); ?>">

The exception is WordPress core functions that include ‘the_’ in their name, these are usually escaped already.

function the_permalink( $post = 0 ) { /** * Filters the display of the permalink for the current post. * * @since 1.5.0 * @since 4.4.0 Added the `$post` parameter. * * @param string $permalink The permalink for the current post. * @param int|WP_Post $post Post ID, WP_Post object, or 0. Default 0. */ echo esc_url( apply_filters( 'the_permalink', get_permalink( $post ), $post ) ); } Untranslatable Text

To be accepted into the directory all themes must be 100% ‘translation-ready’. That means each text string your theme outputs must be translatable.

WordPress already has the systems and functionality to handle the translation process, you just need to make sure your strings use the correct functions.

While simple to implement, this is often overlooked as it goes against the flow of how people write HTML.

Normally, you might do something like this:

<h1>404 - Not Found</h1>

To make it translatable, you need to add in some PHP:

// __ functions are the basis of localization. <h1><?php echo __( '404', 'text-domain' ); ?> // _e functions echo the value. <h1><?php _e( '404', 'text-domain' ); ?> // Escape and echo the string. <h1><?php esc_html_e( '404', 'text-domain' ); ?> // localization and variables. <h1><?php _n( 'One post', '%s posts', $count, 'text-domain' ); ?>

Strings output by functions must also be translation ready:

// not translation-ready :-( <?php next_posts_link( 'Older Entries' ); ?> // translation-ready :-) <?php next_posts_link( esc_html__( 'Older Entries', ‘text-domain’ ) ); ?>

Tip: A lot of code examples in codex.wordpress.org don’t use the translation functions, so be careful when copy and pasting those.

Incorrectly Enqueuing Resources

The .css and .js files your theme uses must be enqueued using the correct functions: wp_enqueue_style() for CSS and wp_enqueue_script() for Javascript.

A common error is to hardcode scripts and styles directly into the <head> or before </body>. There are two problems to this approach:

1. Impossible to remove

If a plugin needs to remove a resource you have loaded, it’s not possible. If you had used the proper enqueue functions it could be done like so:

/** * Dequeue the theme javascript. * * Hooked to the wp_enqueue_scripts action, with a late priority (100), * so that it is after the script was enqueued. */ function wptavern_dequeue_script() { wp_dequeue_script( 'theme-scripts' ); } add_action( 'wp_enqueue_scripts', 'wptavern_dequeue_script', 100 );

2. Duplicate Loading

If you enqueue a resource, jQuery for example, and a plugin also enqueues it, WordPress is smart enough to only load it once.

/** * Enqueue jQuery * * jQuery will only be loaded once, despite the two enqueues. * jQuery is packaged with WordPress so we don't need to specify a src. */ function wptavern_enqueue_script() { wp_enqueue_script( 'jquery' ); wp_enqueue_script( 'jquery' ); } add_action( 'wp_enqueue_scripts', 'wptavern_enqueue_script' );

If instead you had hardcoded jQuery into your <head> then there would be no way for WordPress to know, and it would be loaded twice.

Plugin-Territory Functionality

The scope of a theme should only handle the design and aesthetic of a website, all other functionality should be handled by WordPress itself or plugins.

In an attempt to add more value to their themes, theme authors often try to incorporate extra functionality, for example, SEO controls or custom post types.

The problem with bundling functionality into a theme is that the data is not portable. Take SEO controls as an example, if the user changes the theme, they lose all the work they did to optimize their pages. In contrast by using an SEO plugin, the data and functionality is independent of the theme and will be retained when changing the theme.

Some examples of plugin-territory functionality:

  • Analytics/Tracking
  • SEO controls
  • Contact Forms
  • Shortcodes
  • Gutenberg Blocks

Tip: If your code writes to the database, it is highly likely to be plugin territory. The exception would be design-related settings (sidebar position, colors, etc.).

Not Prefixing

Prefixing is a way of ensuring that your code doesn’t clash with code from plugins. Namespacing in PHP is a better way to achieve the same effect. However, some users are still using old versions of PHP (5.2) which don’t support that feature.

Justin Tadlock shared a list of common things that should be prefixed:

  • PHP function names.
  • PHP class names.
  • PHP global variables.
  • Action/Filter hooks.
  • Script handles.
  • Style handles.
  • Image size names.

Source: https://themereview.co/prefix-all-the-things/

// function example. my_prefix_example(); // class example. class My_Prefix_Example { … } // action and filter example. do_action( 'my_prefix_action' ); apply_filters( 'my_prefix_filter', $values ); // enqueue examples. wp_enqueue_script( 'my_prefix_script', get_template_directory_uri() . '/js/custom-script.js' ); wp_enqueue_style( 'my_prefix_style', get_template_directory_uri() . '/css/styles.css' ); // image size example. add_image_size( 'my_prefix_image_size', 220, 180 ); // 220 pixels wide by 180 pixels tall.

Exception: When enqueuing third-party resources, don’t add a prefix:

// enqueuing a third-party script (chosen.js). wp_enqueue_script( 'chosen', get_template_directory_uri() . '/js/chosen.js' ); Licensing Issues

Your theme and all of its files must be 100% GPL-compatible. This includes images, libraries, scripts, and fonts.

All third-party resources must list their source and license information.

This requirement can be particularly tricky as not all licenses are GPL-friendly. The Unsplash license only has one restriction:

“This license does not include the right to compile photos from Unsplash to replicate a similar or competing service.”

That one restriction, however, is enough to make it non-GPL-compatible, and as such, you won’t see Unsplash images included in wordpress.org themes.

A list of GPL-compatible licenses is available here – https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses

Recently, stocksnap.io has been the most common source of images in the directory as all the images they list are licensed as CC0 (GPL-compatible).

Screenshot Mistakes

The requirements state that your screenshot should be an unedited representation of your theme that doesn’t look like an advertisement. That means no photoshop work, overlays, borders or fancy effects.

Images must also follow the same licensing requirements we explored above.

theme pictured: Blocksy Bonus: Use a Coding Standard

Code that seems easy to read and understand for you, can be the complete opposite for a reviewer who only has 10-15 minutes to check your code.

While there is no requirement on coding standards, following one does make your code easier to read, understand and maintain. I personally use and recommend the ‘WordPress Coding Standards‘, though there are others.

Using PHP_CodeSniffer and the WordPress ruleset in your code editor can make adhering to a standard a lot easier – https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards

Conclusion

The Theme Requirements are created with the end user in mind. Avoid making the common mistakes I’ve listed above and your theme will be approved in no time. If you would like to experience the review process from the other side, you can even become a reviewer.

WPTavern: Pressing Topics – Episode 1

Wordpress Planet - Tue, 05/14/2019 - 08:24

Pressing Topics is a daily podcast hosted by Malcolm Peralty and myself. We discuss the news that’s making headlines in the WordPress ecosystem as well as related topics that catch our eyes. Generally speaking, if you listen to this show on a daily basis, you should have a good idea on what’s going on in the WordPress community.

Pressing Topics is different from WordPress Weekly as we’ll rarely interview guests, go in-depth on specific subjects, and the show’s length is greatly reduced. Today’s episode is 26 minutes long and most episodes will be shorter than that.

In our first episode, we discuss the balancing act of user self sufficiency, a new empowerwoment project at Yoast, why countdown timers on event sites are impractical, and WPMU Dev ending development for more than 90% of their plugins.

We also talk about the success of WordPress Translation day 4, and inform listeners of multiple security vulnerabilities discovered in the WordPress Ultimate Member plugin.

I’ll submit the podcast to iTunes in the next few days to provide more convenient options of subscribing. Please listen to episode one and let us know what you think.

Stories Discussed:

User Self Sufficiency

Empowerwoment project at Yoast

Conference Websites – Please don’t use countdown timers

WPMUDEV Shutting Down Development on Many Plugins

WPMU Pro Sites Plugin Migration Option with WP Ultimo

WordPress Translation Day 4 Successfully Hosts 77 Local Events in 35 Countries, Recruits 183 New Translators

Multiple Vulnerabilities in the WordPress Ultimate Member Plugin

The transcript is in Rich-Text format. You can download the show or listen to it via the embedded audio player below.

EPISODE 1 – Pressing Topics TranscriptDownload Pressing Topics Episode 1Download Listen to Pressing Topics Episode 1

Property Zymphonies Theme

Drupal Themes - Sat, 05/11/2019 - 17:05

Property Zymphonies Theme is the powerful theme to make creating real estates websites with Drupal 8 easier. It has few of the key components which requires for real estates websites. It is mobile-first responsive Bootstrap theme which has all Drupal default components as well.

Live Demo Advanced Themes

Features
  • Drupal 8 core
  • Bootstrap v4
  • Mobile-first theme
  • Top bar information
    • Quick message
    • Email
    • Social media links
  • Types of property
    • Individual
    • Villas
    • Flat
  • Price table
  • Included Sass & Compass source file
  • Well organised Sass code
  • Custom slider - unlimited image upload
  • Home page layouts
    • 4 column top layout
    • 4 column middle layout
    • 4 column bottom layout
    • 4 column footer layout

WPTavern: WPTracSearch: An Elasticsearch-Powered Search Interface for WordPress Trac Tickets

Wordpress Planet - Fri, 05/10/2019 - 21:42

WordPress Trac is one of the more utilitarian and uninspiring interfaces that many contributors have to contend with in the process of giving back to the project. After growing tired of Trac’s mediocre search functionality, William Earnhardt set out to improve it with a new project called WPTracSearch that gave him an opportunity to play around with Elasticsearch and React.

WPTracSearch provides an alternative Elasticsearch-powered interface for searching WordPress Trac tickets. It performs a full text search of all of the fields, delivering more accurate results, even for basic queries, thanks to Elasticsearch’s relevance ranking. The results can be easily filtered based on milestone, component, focuses, usernames, and more criteria, making it easier to find specific tickets.

The search interface also supports fuzzy matching, adding to its ability to deliver more relevant results. Even if a term is misspelled (either in the search or the ticket) it will still yield results, as in the example below:

Earnhardt is a WordPress core contributor and a developer at Bluehost. His core team has the discretion to work on whatever they want for WordPress core and the community.

“This fit in nicely with that, but was also just something fun to tinker with,” he said. “It started as a fun experiment with Elasticsearch last fall. I built an index on my local machine and played around with it but got busy with other stuff pre-5.0 push and it sort of fell by the wayside.

“Then early this year I had a few times come up where it would have been helpful, so I threw together an interface for it and got it online.”

If you want to use WPTracSearch but are not sure how current the ticket index is, Earnhardt said it’s nearly constantly in sync:

There is a PHP script that parses all the information about a ticket in Trac using the XMLRPC api and puts it into an Elasticsearch index. There is a bash script that runs on a cron every minute to find any tickets updated since the last run and then uses the PHP script to reindex them. So it stays pretty constantly in sync.

The project uses a React interface that relies on the Reactivesearch library to query the Elasticsearch index. Earnhardt also borrowed some code from Ryan McCue’s Not Trac to help with some of the UI that deals with parsing TracLinks and code blocks.

WPTracSearch is an evolving project and Earnhardt has lots of plans for improving it. The two highest priority items on his roadmap are indexing meta Trac and making a search UI for it. He also wants to make the individual tickets have navigable URLs instead of being modal pop up windows when you click on the summary in the search results.

“I do it that way because it’s a lot faster to stay in this interface than jumping back and forth to core.trac.wordpress.org when browsing tickets, but you can’t link directly to a ticket and forward/back doesn’t work,” Earnhardt said.

“You can also query the Elasticsearch index directly without using the React interface if you know Elasticsearch Query DSL. This allows pretty complex queries to be built. I’ve thought about creating some charts using that. It could help with the core triage team effort to better understand churn and progress toward bringing that open ticket count down. There are a lot of cool possibilities.”

WPTracSearch is available on GitHub if anyone wants to contribute ideas or code to improve it.

WPTavern: Tips for Replying to A Call for Papers or A Call for Speakers

Wordpress Planet - Fri, 05/10/2019 - 18:32

The following is a guest post written by Jennifer Bourn. With 21 years experience as a graphic designer, 15 years experience as a web designer, 14 years as a creative agency owner, and 11 years as a blogger, Jennifer Bourn has worked with hundreds of service-based businesses to build brands and establish profitable online platforms. She also co-organizes the Sacramento WordPress Meetup and WordCamp Sacramento.

After being the lead organizer for WordCamp Sacramento for two years, speaker wrangler for two years, managing the program for a year, and speaking at several WordCamps and non-WordPress related conferences myself, I have seen a lot of amazing and a lot of awful speaker submissions. Some speaker submissions have been from people I know personally — people I want to choose and say yes to — but ultimately couldn’t because their submission was subpar.

It’s incredibly tough to both apply to speak and select speakers from applications.

With that in mind, I shared a Twitter thread yesterday with tips for replying to a Call for Papers or a Call for Speakers that will help you get your next talk submission accepted and it is summarized for your convenience below:

If your title is confusing, weird, unclear, too cutesy, or it feels like you put no effort into it, that will work against you. Organizers want talks attendees will be interested in and excited for. It must be easy to understand what the talk is about based on the title alone.

If your talk description is all about you, is only one sentence long, is sarcastic/unprofessional, isn’t aligned with the event focus/theme, or it’s totally self-serving, you should rethink things. Your talk isn’t about you, it’s about helping attendees expand their knowledge and move the needle and helping organizers host a successful event.

It is never ever a good idea to disparage or put down a person, job, tool, piece of software, or anyone/anything to make your point or make your topic interesting. If the only way you can communicate your point is through negativity, reconsider the topic. Being controversial may have been a draw in years past, but now it’s a risk most organizers aren’t willing to take.

Consider that someone else (or several people) may submit a talk on the exact same subject. Your title and description need to convince organizers why your submission should be picked over the other person’s submission.

Consider that if you submit multiple talks, none of them may be selected if your titles aren’t interesting and your descriptions are not descriptive. It must be clear what the talk is about and what the takeaways are, and how this talk will benefit the attendees.

Always think about how you can make the organizers’ or event planners’ jobs easier and follow instructions. For example, if they ask for bios in third-person, provide your bio in third-person. If they ask for full name, provide your full name.

Spell the name of the conference, software, industry, etc. correctly in your speaker application. Want to speak at a WordPress event? Double check that you’ve capitalized the P and proofread your submission.

Look at the topics requested by the event organizers. Submit talks on those topics and your chances of being selected will be higher because they are telling you what they want. Lists of preferred topics are usually included because that is what their local community has specifically requested.

Don’t submit the same talk you’ve submitted 10 times to other events. Put in some effort. Look at the event theme and submit something that relates to it or customize the talk title/description to include the theme.

Look at the past event schedules, agenda, or programs. Look at the types of talks they accept. For example, if a WordCamp has only had 2-3 business related talks in the past four years, it might be a sign they aren’t looking for business talks and want talks focused more on using WordPress.

Look at the topics the event has already covered in previous years. Then find the gap and find something they haven’t already heard or done.

Steer clear of the marketing hype. Avoid topics related to killing it, hustling, crushing, and dominating. Don’t refer to yourself as a guru or a thought leader (that’s only cool when other people say it about you). Avoid negativity, sarcasm, and assumptions about the audience.

If organizers ask how or why you’re qualified to talk on the topic being submitted:

  • It’s okay to be new/just learning — fresh voices are awesome.
  • Don’t just copy and paste your bio into the field. They already have your bio and that’s not what they meant or what they want.

Never assume the people reviewing your application are experts on your talk topic or have the same technical background you do.

Avoid submitting a talk that is all about one piece of software — i.e. one plugin — especially if the software is premium and requires an investment. An entire session dedicated to a paid plugin 1) excludes those who have not purchased it or cannot purchase it and 2) will apply to few attendees. Instead, consider a compare/contrast presentation that covers both free and paid options or a talk that introduces attendees to multiple options.

It’s okay to submit opinion pieces as talks, but be careful to NOT position your opinion or approach as the only one or the right one, when there are other options. Often there isn’t one right way (unless it’s technical and there is one right way).

If the submission form asks what skill level audience your talk is the best fit — Beginner, Intermediate, or Advanced — don’t pick them all. That isn’t helpful. The same is true if they ask who your talk is aimed at — designers, developers, or users, etc.

Organizers for events like WordCamps need to satisfy a diverse audience. The attendee makeup often ranges from those who make a living with WordPress all the way to newbies who just learned what WordPress is a few days ago, so talks at and for every skill level are needed and valued. Don’t skip applying because you think your talk isn’t advanced enough.

If there is a ‘notes to the organizer’ field in the talk submission form, communicate that you’re open to suggestions or making tweaks to the talk focus to ensure it’s a great fit for their audience. Often a talk being reviewed is close to what they want, but it needs a small tweak to be selected.

If something funky happened when you hit submit, don’t be afraid to submit your talk again. Organizers would rather have duplicate submissions than miss your submission. Also, it’s okay to reach out to confirm your submission was received.

Don’t skip applying to speak because you don’t think you know enough yet or don’t have enough experience yet. Everyone has value to contribute and fresh perspectives are always appreciated. Plus, there are people who just discovered or figured out the thing you want to talk about exists — I guarantee you can help them.

Behind the scenes organizers work hard to create a diverse lineup of speakers that provides representation for everyone in the community. Organizers can ask, beg, plead, and do loads of outreach, but ultimately, they are limited by who is willing to apply and/or who is willing to accept an invite to speak. So please say yes and apply.

When organizers make the offer to help you brainstorm talk ideas, craft a talk title/description, and even create your slide deck or watch your practice, say yes. Take them up on the offer. Asking for help doesn’t make you any less awesome. There are a lot of people who are incredibly talented and smart with great value to share but find it difficult to put what they know into a talk format. If that’s you, you’re not alone and there are people who want to help.

Interested in trying your hand at speaking for the first time?

Every event has limited space. When securing rooms for multi-track events and planning the schedule, organizers need to be able to split attendees across the different rooms/tracks. This means they need competing talks in each track that will be a draw and attract attendees. No one wants one full room and one empty room. No one.

If you don’t get selected, don’t get down on yourself. Often the selection choice has nothing to do with you and is simply a matter of many submissions on the same topic(s), needing to balance topics across disciplines to serve the range of attendees or skill sets, and looking for more diverse representation in the speaker lineup.

If the event is local to you, always apply. Many times event/conference organizers want to fill the speaking spots (or at least half of them) with local people from their community or region and you’ll have a leg up on the out-of-towners. Similarly, if there is a meetup group in the area tied to the event/conference, go to the meetup and get to know the organizers and other attendees.

New to a subject/topic? Just learning it? No problem! Consider submitting a talk reviewing your experience as a new user. Share surprises and obstacles encountered, lessons learned, and suggestions for improvement. This can be hugely valuable for advanced users who tend to what new users deal with and it can provide a different perspective and voice.

Want to learn a topic better? There’s no better way than to teach others about it. Submit the talk, do the work to learn it, and teach everything you’ve learned so far. For example, if you want to build a membership site, submit a talk on how to choose a membership plugin, document your research in finding the right plugin, and share what plugins you reviewed, what criteria you used for evaluation, what you discovered (pros/cons), and which you ended up choosing.

Never underestimate the power of awareness. Consider pitching a talk that presents options to expand attendees awareness of what is available or possible and gives them a starting place to research things on their own.

WPTavern: Storefront 2.5.0 Introduces a Custom, Block-Based Homepage

Wordpress Planet - Fri, 05/10/2019 - 15:59

Storefront, WooCommerce’s free flagship theme, has just released version 2.5.0 with updates that make it easier to setup and customize the homepage.

In 2017, WooCommerce 2.2 introduced starter content to help users set up the homepage template, menus, widgets, and add some demo products. This content has been updated to incorporate the WooCommerce blocks that were rolled into the plugin’s 3.6 release. It also adds support for the new cover block, which enables users to place headings, paragraphs, and buttons inside the block.

These changes essentially create a custom, editable homepage with all the flexibility of blocks, giving users more control than the previous custom homepage template approach. The old homepage (template-homepage.php) has now been retired.

Storefront is active on more than 200,000 stores. Many of these sites already have their homepages set, but the new block-based homepage makes it easier to set up a new store or make changes to existing homepage designs without having to use custom code or a plugin.

Version 2.5 is a minor release but still requires testing before updating, as some users have already reported a few discrepancies with how the “full width” template is displayed. Previewing the update in a staging environment will ensure there are no surprises on update.

Tomorrow is WordPress Translation Day 4

Wordpress News - Fri, 05/10/2019 - 09:17

The fourth edition of WordPress translation day is coming up on Saturday 11 May 2019: tomorrow! Get ready for a 24-hour, global marathon dedicated to localizing the WordPress platform and ecosystem. This event takes place both online and in physical locations across the world, so you can join no matter where you are!

The WordPress Polyglots Team has a mission to translate and make available the software’s features into as many languages as possible. As WordPress powers more than 33% of websites, people from across the world use it in their daily life. That means there is a lot that needs translating, and into many different languages.

On 11 May 2019, from 00:00 UTC until 23:59 UTC, WordPress Translation Day aims to celebrate the thousands of volunteers who contribute to translation and internalization. The event is also an opportunity for encouraging more people to get involved and help increase the availability of themes and plugins in different languages.

“At the time of the last event in 2017, WordPress was being translated into 178 languages, we have now reached the 200 mark!”

WPtranslationday.org What happens on WordPress Translation Day?

There are a number of local meetings all over the world, as well as online talks by people from the WordPress community. More than 700 people from around the world took part in past WordPress Translation Days, and everyone welcome to join in this time around!

Everyone is welcome to join the event to help translate and localize WordPress, no matter their level of experience. A lot is happening on the day, so join in and you will learn how to through online sessions!

What can you expect?
  • Live online training: Tutorials in different languages focused on translation and localization, or l10n, of WordPress. These are streamed in multiple languages
  • Localization sessions: General instruction and specifics for particular areas and languages. These sessions are streamed in multiple languages.
  • Internalization sessions: Tutorials about optimizing the code to ease localization processes, also called internationalization or i18n. These sessions are streamed in English.
  • Local events: Polyglot contributors will gather around the world for socializing, discussing, and translating together.
  • Remote events: Translation teams that cannot gather physically, will connect remotely. They will be available for training, mentoring, and supporting new contributors. They will also engage in “translating marathons”, in which existing teams translate as many strings as they can!

A number of experienced WordPress translators and internationalization experts are part of the line-up for the livestream, joined by some first time contributors.

Whether you have or haven’t contributed to the Polyglots before, you can join in for WordPress Translation Day. Learn more about both local and online events and stay updated through the website and social media.

WordPress.org blog: Tomorrow is WordPress Translation Day 4

Wordpress Planet - Fri, 05/10/2019 - 09:17

The fourth edition of WordPress translation day is coming up on Saturday 11 May 2019: tomorrow! Get ready for a 24-hour, global marathon dedicated to localizing the WordPress platform and ecosystem. This event takes place both online and in physical locations across the world, so you can join no matter where you are!

The WordPress Polyglots Team has a mission to translate and make available the software’s features into as many languages as possible. As WordPress powers more than 33% of websites, people from across the world use it in their daily life. That means there is a lot that needs translating, and into many different languages.

On 11 May 2019, from 00:00 UTC until 23:59 UTC, WordPress Translation Day aims to celebrate the thousands of volunteers who contribute to translation and internalization. The event is also an opportunity for encouraging more people to get involved and help increase the availability of themes and plugins in different languages.

“At the time of the last event in 2017, WordPress was being translated into 178 languages, we have now reached the 200 mark!”

WPtranslationday.org What happens on WordPress Translation Day?

There are a number of local meetings all over the world, as well as online talks by people from the WordPress community. More than 700 people from around the world took part in past WordPress Translation Days, and everyone welcome to join in this time around!

Everyone is welcome to join the event to help translate and localize WordPress, no matter their level of experience. A lot is happening on the day, so join in and you will learn how to through online sessions!

What can you expect?
  • Live online training: Tutorials in different languages focused on translation and localization, or l10n, of WordPress. These are streamed in multiple languages
  • Localization sessions: General instruction and specifics for particular areas and languages. These sessions are streamed in multiple languages.
  • Internalization sessions: Tutorials about optimizing the code to ease localization processes, also called internationalization or i18n. These sessions are streamed in English.
  • Local events: Polyglot contributors will gather around the world for socializing, discussing, and translating together.
  • Remote events: Translation teams that cannot gather physically, will connect remotely. They will be available for training, mentoring, and supporting new contributors. They will also engage in “translating marathons”, in which existing teams translate as many strings as they can!

A number of experienced WordPress translators and internationalization experts are part of the line-up for the livestream, joined by some first time contributors.

Whether you have or haven’t contributed to the Polyglots before, you can join in for WordPress Translation Day. Learn more about both local and online events and stay updated through the website and social media.

WPTavern: Advanced Custom Fields 5.8.0 Introduces ACF Blocks: A PHP Framework for Creating Gutenberg Blocks

Wordpress Planet - Thu, 05/09/2019 - 18:14

After six months in development, Advanced Custom Fields 5.8.0 was released yesterday with a new PHP-based framework for developing custom Gutenberg block types. ACF Blocks was announced in October 2018, to the great relief of many developers who didn’t know how they were going to keep pace with learning the JavaScript required to use WordPress’ Block API.

ACF’s creator, Elliot Condon, was one of the more vocal critics of Gutenberg leading up to its inclusion in WordPress 5.0. Developers were concerned about whether or not their custom metaboxes generated by ACF would still be compatible. The ACF team worked to ensure the plugin was integrated into the Gutenberg UI as much as possible and surprised users by announcing an acf_register_block() function that would allow developers to use PHP to create custom blocks.

The new ACF Blocks add-on is built on top of Advanced Custom Fields Pro and does not require any JavaScript knowledge. It integrates with custom fields so developers can create custom solutions. ACF blocks are rendered using a PHP template file or a callback function that allows full control of the output HTML and live previews while editing the blocks. They also maintain native compatibility with WordPress core, meaning that all Gutenberg features like “alignment” and “re-usable blocks” work as expected.

Early feedback indicates that ACF Blocks has made custom Gutenberg development more approachable for developers who are not as well-versed in React, significantly speeding up the creation of custom blocks.

ACF Pro 5.8 for #WordPress makes Gutenberg block development a breeze! Here's a staff block I made in less than 30 mins. @wp_acf #ACFBlocks #wordpressdeveloper #Gutenberg #reactjs #webdevelopment #webdeveloper pic.twitter.com/VqewoKkcSt

— Sam (@sam_kent_) May 9, 2019

This is one example of how the WordPress product ecosystem continues to evolve to support developers in the transition to a more JavaScript-powered WordPress.

ACF Blocks also launched with a suite of nine ready-to-use bocks available as a plugin from the new acfblocks.com website. These include commonly-requested functionality for client sites, such as testimonial, team, multi-button, star-rating, pricing list, and click-to-tweet, with more on the way.

WPTavern: WPWeekly Episode 351 – Results of the Gutenberg Accessibility Audit

Wordpress Planet - Thu, 05/09/2019 - 00:52

In this episode, John James Jacoby and I are joined by Rachel Cherry, Freelance software engineer, consultant, and director of WPCampus and Brian DeConinck, a front-end designer and developer with the OIT Design and Web Services team, part of the Office of Information Technology at NC State University.

We learn how Tenon was chosen as the vendor to perform the audit and what conditions needed to be met. We then dissected the results of the Gutenberg Accessibility Audit conducted by Tenon. We discuss the state of Gutenberg’s accessibility, recommendations for those in Higher Education environments, and where Gutenberg development might go from here.

Transcript:

WPWeeklyEpisode351Transcript

WPWeekly Meta:

Next Episode: Wednesday, May 15th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #351:

WPTavern: WordPress Professionals: Take the Future of WordPress Careers Survey

Wordpress Planet - Wed, 05/08/2019 - 23:24

Nevena Tomovic, a Business Developer at Human Made, is researching the most important skills for pursuing a career in WordPress. She is conducting a survey for professionals that is open to anyone working in a WordPress-related capacity, including writers, developers, marketers, UI & UX designers, illustrators, community drivers, evangelists, project managers, and creatives.

The survey takes less than five minutes to complete and the results will be shared at WordCamp Europe in Berlin and on nevena.blog. Tomovoic will be giving a presentation titled “Renaissance jobs in WordPress: Skills you need to survive the 21st-century career,” where she will elaborate on global trends related to the job landscape. She will also be speaking about how employers and managers can attract new talent through WordPress education.

In a recent post on her blog, Tomovic elaborated on the concept of “Renaissance jobs,” positions that use titles merging multiple skills into one role:

Renaissance jobs, also otherwise known as hybrid roles are a mishmash of more than one skill, a combination of expertise in more than one domain. You might have come across roles such as experience architect, user experience consultant, or even customer wrangler, all of these typically involve technical knowledge, excellent communication and management skills. All of these roles are a completely foreign concept for most of our parents. The 21st century has brought with it remote work, chief growth officers, and a globalized workforce among other things.

Tomovic’s survey data will identify what skills are most important in the WordPress job market right now. The survey does not collect any personal data and the raw data will be deleted after the results are published.

If you want to check out Tomovic’s talk in person, make sure to purchase a ticket to WordCamp Europe. The final batch of tickets has gone on sale and there are only 133 general admission tickets remaining.

WPTavern: New Membership Block Coming to Jetpack, Site Health and Debug Info Added to Version 7.3

Wordpress Planet - Wed, 05/08/2019 - 17:57

Jetpack 7.3 was released yesterday with changes that improve the “out of the box” experience. The plugin now enables fewer features on setup so users can have more control over what they activate on their sites.

The new version also integrates with WordPress 5.2’s new Site Health checks. It includes a status check and moves Jetpack’s legacy debug data to a section in the new “Site Health Info” tab. The initial status check isn’t very descriptive regarding critical errors, but these error messages can be improved in future iterations so users know how to get to a page with more information.

New Membership Block Now Available for Jetpack Beta Testers

Jetpack is getting ready to introduce a new Membership block that will essentially function like a recurring donation button using Stripe as the payment gateway.

Users will be able to set the currency, price, product name, and renewal interval directly within the block.

This release adds the new block behind the JETPACK_BETA_BLOCKS constant for users who are beta testing new blocks. Feedback from testers will be addressed in future pull requests. The PR merged into Jetpack 7.3 includes the following technical additions for the new Membership block:

  • Introduce endpoints that communicate with WP.COM
  • Whitelist certain options, CPTs and meta to store / sync data
  • Introduce Gutenberg block that uses these endpoints and provides UI to connect to Stripe, create and choose a product
  • Introduce a frontend of a block with the sole purpose of displaying a checkout window from WP.com in an iframe

In its current form, the use of the term “Membership” for the block might be a bit misleading for some users, depending on their expectations. Site owners usually expect more granular management of members, multiple membership tiers, customizable emails, various renewal options, content access, and more for managing memberships.

Unless Jetpack intends to make this the gateway to more robust membership capabilities, then “Recurring donation/payment button” might be a more accurate name for the block. However, it wouldn’t be surprising to see a more full-featured Membership module turn up as a SaaS product from WordPress.com, as opposed to everything getting packed into the plugin.

No release date has been announced for the membership block as it is still under active development and in the very early stages of beta testing.

Check out the full changelog to see all the enhancements and bug fixes in Jetpack 7.3.

WPTavern: WordPress 5.2 “Jaco” Released, Includes Fatal PHP Error Protection and A Recovery Mode

Wordpress Planet - Wed, 05/08/2019 - 17:16

WordPress 5.2 “Jaco” named after bassist Jaco Pastorius, is now available for download. Normally, I’d start listing new features but I’m going to do something a little different this time.

Let’s begin by recognizing the 327 people who contributed to this release with 109 of those being first time contributors. It was led by Matt Mullenweg, Josepha Haden Chomphosy, and Gary Pendergast. Included in the list is Alex (Viper007Bond) Mills who passed away from Leukemia earlier this year.

Screenshot taken by Brandon Kraft

Mills still has a few uncommitted patches in Trac so it’s possible he’ll end up on the list of contributors in future releases.

Minimum PHP Version Required to Run WordPress 5.2 Is Now 5.6.20

WordPress 5.2 bumps up the minimum PHP version required to 5.6.20. If you’re using an older version, you’ll need to update PHP before upgrading to WordPress 5.2. Updating PHP to version 7.3 or above is recommended.

Additional Improvements to Site Health Check

In WordPress 5.1, Site Health Check features were added to inform users of outdated PHP versions. WordPress 5.2 builds on this foundation by adding two new pages that help debug common configuration issues. Users can find the Site Health section in the WordPress backend by browsing to Tools > Site Health.

Site Health Check Test Results

Browsing to the Site Health page triggers a series of tests. When the tests are performed, errors and recommended improvements are displayed on the results page. There’s also a an Information tab that displays every detail about the configuration of your site.

Site Health Check Detailed Information

Theme and Plugin authors can add their own tests and modify or remove existing ones with filters.

Fatal Error Protection

Instead of seeing the dreaded “white screen of death,” WordPress 5.2 includes fatal PHP error protection. When a fatal error is detected, a user-facing error message is displayed and an email is sent to the administrator’s email address.

The email includes a link to a new feature called “recovery mode.” While in recovery mode, plugins and themes that are causing fatal errors are put into a paused state to ensure administrators can work around the errors and access the backend normally.

In addition to being informed about which themes or plugins are causing fatal errors, administrators have at least three options to fix the issue.

  • Administrators can deactivate the theme or plugin to maintain a working version of the site.
  • Administrators can fix the problem if they have the technical capabilities, and afterwards reactivate the theme or plugin.
  • Administrators can file a support request with the developer, pointing out the error.

Administrators can exit recovery mode by pressing a button in the admin bar. A few examples on how developers can utilize this feature can be found here.

WordPress 5.2 also includes accessibility improvements, thirteen new dashboard icons, plugin compatibility checks, and an variety of changes to the block editor. In addition, the Privacy Policy page includes four new helpers that make customizing and designing the page easier.

To learn more about the features in WordPress 5.2 and how to extend or work with them, check out the WordPress 5.2 Field Guide.

HeroPress: Broadening My Horizons Through WordPress

Wordpress Planet - Wed, 05/08/2019 - 12:00

I’ve been a web designer since 1996. In some ways, it’s hard for me to fathom. Those were the days of Netscape Navigator and table-based page layouts. I wrote every bit of HTML by hand on a seriously-underpowered computer and a tiny monitor. Definitely a far cry from where we are today.

I was completely self-taught and learned by doing. When I landed my first job as a full-time “webmaster” at my local newspaper, I didn’t even know what Photoshop was (I had been using Microsoft Paint for graphics – feel free to laugh).

Looking back, I know that I wasn’t a very good designer in those days – but that didn’t matter. I felt lucky to be on the ground floor of an industry that was poised to change the world.

An Early Start

As an 18-year-old, I was often the youngest person in the office. Sometimes, that led to not being taken seriously by those in charge. Still, I did have a few mentors at the paper who were more than generous with their friendship and advice. It was my first taste of the “real world” – a lesson I sorely needed.

At the same time, I realized that I wasn’t going to stay there forever. The pay wasn’t very good and the hours weren’t my cup of tea. Most of all, I just felt that I could do better. Just over a year in, I left.

From there, I spent the next couple of years in various corporate settings – none of which felt very fulfilling. My existence was very much that of a worker bee. Sure, this is what happens when you’re just starting out – but I was too dense to see it that way.

Again, I had a feeling that there was something else out there for me. But there didn’t seem to be a path to further my career, unless I took it upon myself to do so.

So, in 1999 I went all-in as a freelancer working from home. While I’ve gone through a few different places to call home in the years since, I’m still here – thanks in great part to WordPress.

But before I found both the software and community that would change my trajectory, I had to go through some ups and downs.

Hitting a Wall

Starting my own business at 21 was at once frightening and gratifying. I booked a few steady clients early on, and that provided a much-needed boost in confidence (and revenue). Yet there was also a tremendous amount of responsibility that I wasn’t prepared for. It was another real-world lesson and I had to mature in a hurry.

As for technology, I upgraded my computer, but not necessarily my approach. The first several years were still ruled by building static HTML sites. And as clients started asking for more complex features such as ecommerce, I realized something about myself: I was incredibly afraid of what I didn’t know.

This feeling would haunt me much more than I could have anticipated. It was like a massive weight on my shoulders. As long as work kept me in my comfort zone, I was fine. But anything outside of that brought out my anxiety.

Sure, I had achieved some level of success at a young age (with a hobby site even going viral). I had plenty of work, I even moved out of my parent’s house. But I also feared the unknown. I hadn’t been a very good student in high school and had zero confidence in my ability to learn something more advanced.

At the same time, that fear was joined by a great deal of frustration. I started struggling to build larger sites using those same tired methods. And maintaining them was even worse.

In all, I was stressed out and felt stuck in a dead end. The passion I once had for design and code had vanished. I was in desperate need of a new direction.

A Glimmer of Light

It’s amazing how, just when things feel their darkest, a little bit of light shows up and sparks something in you. For me, WordPress was like a tiny matchstick in a pitch-black cave.

Somewhere around 2005, I installed an early version of WordPress as a playful experiment. At the time, I saw other content management systems starting to pop up, but wasn’t really impressed. Frankly, the sites running them all looked the same.

But tearing apart a WordPress theme was different. I knew nothing about PHP, but found that the templates were pretty easy to follow. I liked that I could make design changes without too much trouble. Even if I broke something, I was (usually) able to bring things back to their previous state.

Still, I wasn’t ready or willing to abandon my old-school techniques for building sites just yet (I even jettisoned the CSS layouts from my theme and replaced them with tables). WordPress was something I used on the periphery. I created a few simple blogs for clients, but hadn’t really thought of using it for anything more.

In fact, it would be a few more years until I was finally ready to make a change.

A New Beginning

2010 was a banner year in my career. It was the year where I, inspired by my wife and newborn daughter, started to really confront my fears. I had grown completely tired of the way I had been doing things. This was the year I became convinced that WordPress was the game-changer I needed.

As the software matured, more developers started using it to run entire sites – not just traditional blogs. I was very much intrigued, even excited, about the possibility of what I could achieve in terms of both design and functionality.

So, I convinced one of my agency clients to let me try using WordPress on a project. Things went well enough that we decided to start using it more often. And, for me, it was like that little matchstick in the dark cave turned into a huge beacon.

The more I used WordPress, the more curious I became about what else it could do. I found myself not only being unafraid to learn, but actually motivated to do so.

By the next year, I had moved almost exclusively to WordPress. That led to another watershed moment: Attending my first WordCamp.

Discovering That I Wasn’t Alone

Visiting WordCamp Philadelphia 2011 was an eye-opening experience. This was not the buttoned-down, corporate atmosphere that brought me discomfort years earlier. Instead, I found a casual, welcoming vibe that made me feel like I belonged.

The crowd was diverse in just about every way imaginable. And I met people who were all over the map when it came to knowledge of WordPress. Some were complete newbies, others were experts. But regardless of their skill level or experience, they all gathered in the same place. It struck me that I was now a part of something unique.

This burgeoning community, coupled with great software, had all of the sudden put me on a path that I never imagined possible. It made me want to learn all that I could and be a part of something bigger than myself.

Before too long, I discovered a confidence I never felt before. I was not only building better websites than I ever had, I was also eager to be a part of the WordPress community. And, despite being a bit shy, I even spoke at WordCamp Baltimore in 2012.

I felt like anything was possible.

Opportunity Knocks

As my experience with both WordPress and its community has grown, it has opened up some amazing opportunities. For one, it gave me the courage to try and fulfill another lifelong dream: to become a writer.

I started off by submitting an article to Speckyboy Web Design Magazine, not really knowing what to expect. When it was published, I was incredibly excited. So, I kept on writing. And each time, site editor Paul Andrew kept on publishing my work.

Even more mind-boggling is that, eventually, this led to a regular role with the site. I’ve published hundreds of articles and have enjoyed every minute of it. And more writing gigs have followed. My topic of choice? WordPress, of course!

When it comes to my design business, I’m no longer afraid to push those boundaries. I’ve built and maintained hundreds of WordPress sites that run the gamut in terms of size and functionality. Yes, including the formerly fear-inducing ecommerce.

But I know that, without the confidence boost I received by working with WordPress, none of this would have been possible. I am beyond grateful, and so glad that I found it at a pivotal time in my life.

What I’ve Learned

So, what does this all mean? I’ve given it a lot of thought.

There are still days when I’m overwhelmed and stressed out. But even then, I tell myself how I lucky I am to do what I do each day. And somehow, I have maintained a passion for my work that I think is here to stay.

But the biggest lesson I’ve learned, and the thing I’d like to share with you, is to give yourself a chance to learn and grow. Sometimes, the unknown can be scary – I get it. I was so afraid of the fact that I wasn’t formally trained and that I didn’t have the knowledge I needed to go further. I was scared that if I failed to learn what I needed to know that I’d be left in the dust.

Yet, that’s the amazing thing about WordPress and web design in general. There are so many great resources out there you can learn from. And there is a community out there who is willing to help and share what they know.

Everything is right there in front of us. All it takes is a willingness to try.

The post Broadening My Horizons Through WordPress appeared first on HeroPress.

WordPress 5.2 “Jaco”

Wordpress News - Tue, 05/07/2019 - 21:03
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:

Aaron D. Campbell, Aaron Jorbin, Adam Silverstein, Adam Soucie, Adil Öztaşer, Ajit Bohra, Alain Schlesser, Alda Vigdís, Alex Denning, Alex Dimitrov, Alex Kirk, Alex Mills, Alex Shiels, Alexis, Alexis Lloyd, allancole, Allen Snook, Andr?, andraganescu, Andrea Fercia, Andrea Middleton, Andrei Lupu, Andrew Dixon, Andrew Duthie, Andrew Nacin, Andrew Ozz, Andrey "Rarst" Savchenko, Andrés Maneiro, Andy Fragen, Andy Meerwaldt, Aniket Patel, anischarolia, 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, 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, Dave Whitley, DaveFX, davetgreen, David Baumwald, David Binovec, David Binovec, David Herrera, David Roddick, David Smith, Davide 'Folletto' Casali, daxelrod, Debabrata Karfa, 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, EcoTechie, Eduardo Toledo, Ella Van Durpe, Emil Dotsev, fabiankaegy, Faisal Alvi, Farhad Sakhaei, Felix Arntz, Franklin Tse, Fuegas, Garrett Hyder, Gary Jones, Gennady Kovshenin, ghoul, Girish Panchal, Grzegorz Ziółkowski, Guido Scialfa, GutenDev , gwwar, 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, Janki Moradiya, Jarred Kennedy, Javier Villanueva, Jay Upadhyay, Jaydip Rami, Jaye Simons, Jayman Pandya, jdeeburke, Jean-Baptiste Audras, Jeff Paul, Jeffrey de Wit, Jenny Wong, Jeremy Felt, Jeremy Green, Jeremy Herve, jitendrabanjara1991, Joe Dolson, Joe McGill, Joen Asmussen, Johan Falk, Johanna de Vos, John Blackbourn, John James Jacoby, Jonathan Desrosiers, Jonathandejong, joneiseman, 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, Justin Ahinon, 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, lovingboth, Luke Carbis, Luke Gedeon, Luke Pettway, Maciej Palmowski, Maedah Batool, Maja Benke, Malae, Manzoor Wani, Marcin, Marcin Pietrzak, Marco Fernandes, Marco Peralta, 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, Niels de Blaauw, Nikolay Nikolov, Nilambar Sharma, ninio, notnownikki, Oliver Sadler, onlanka, pandelisz, Pascal Birchler, Paul Bearne, Paul Biron, Pedro Mendonça, Peter Booker, Peter Wilson, pfiled, pilou69, Pranali Patel, Pratik, Pratik K. Yadav, Presskopp, psealock, Punit Patel, Rachel Cherry, Rahmon, Ramanan, Rami Yushuvaev, Ramiz Manked, ramonopoly, Riad Benguella, Rinat Khaziev, Robert Anderson, Rudy Susanto, Ryan Boren, Ryan Welcher, Sébastien SERRE, Saeed Fard, Sal Ferrarello, Salar Gholizadeh, Samaneh Mirrajabi, Sami Keijonen, Samuel Elh, Santiago Garza, Sara Cope, saracup, sarah semark, Scott Arciszewski, Scott Reilly, Sebastian Pisula, Sekineh Ebrahimzadeh, Sergey Biryukov, SergioEstevao, sgastard, sharifkiberu, Shashank Panchal, 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, TobiasBg, TomHarrigan, tonybogdanov, Tor-Bjorn Fjellner, Toro_Unit (Hiroshi Urabe), torres126, Torsten Landsiedel, Towhidul Islam, Tracy Levesque, Umang Bhanvadia, Vaishali Panchal, vrimill, WebFactory, Weston Ruter, WFMattR, William 'Bahia' Bay, William Earnhardt, williampatton, Willscrlt, Wolly aka Paolo Valenti, wrwrwr0, Yoav Farhi, Yui, Zebulan Stanphill, and Česlav Przywara.

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!

WordPress.org blog: WordPress 5.2 “Jaco”

Wordpress Planet - Tue, 05/07/2019 - 21:03
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:

Aaron D. Campbell, Aaron Jorbin, Adam Silverstein, Adam Soucie, Adil Öztaşer, Ajit Bohra, Alain Schlesser, Alda Vigdís, Alex Denning, Alex Kirk, Alex Mills, Alex Shiels, Alexis, Alexis Lloyd, allancole, Allen Snook, André, andraganescu, Andrea Fercia, Andrea Middleton, Andrei Lupu, Andrew Dixon, Andrew Duthie, Andrew Nacin, Andrew Ozz, Andrey "Rarst" Savchenko, Andrés Maneiro, 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, Dave Whitley, DaveFX, davetgreen, David Baumwald, David Binovec, David Binovec, David Herrera, David Roddick, David Smith, 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, ecotechie, Eduardo Toledo, Ella Van Durpe, fabiankaegy, Faisal Alvi, Farhad Sakhaei, Felix Arntz, Franklin Tse, Fuegas, Garrett Hyder, Gary Jones, Gennady Kovshenin, Girish Panchal, Grzegorz 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 Wong, Jeremy Felt, Jeremy Green, Jeremy Herve, jitendrabanjara1991, JJJ, Joe Dolson, Joe McGill, Joen Asmussen, Johan Falk, Johanna de Vos, John Blackbourn, Jonathan Desrosiers, Jonathandejong, joneiseman, 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 Fernandes, Marco Peralta, 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, Pratik K. Yadav, Presskopp, psealock, Punit Patel, 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, Scott Reilly, 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 Stanphill.

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!

WPTavern: Registration for WordSesh 6 Is Now Open

Wordpress Planet - Tue, 05/07/2019 - 20:45

Registration for the sixth installment of WordSesh is now open and thanks to Pantheon, those who attend the conference live will be able to watch all of the sessions for free. WordSesh is a virtual WordPress conference with speakers from around the world sharing knowledge.

This year’s event has 14 speakers with topics that include, the benefits of being the first to market with a Gutenberg user course, three ways to embrace the entrepreneurial roller coaster, and the rhythms of remote teams. Ten of the presentations will be live with four pre-recorded sessions.

WPSessions will transcribe each presentation live and will also store the recordings so that registered members can view them at a later date. There will also be a virtual hallway track where participants can network with each other.

If you’d like to watch with a group of people in the same physical location, WordSesh has a list of watch parties that are taking place.

If you’re hosting a watch party, you’re encouraged to contact WordSesh with the details so your event can be added to the list. WordSesh 6 begins May 22nd at 9:30AM Eastern on Crowdcast.

Pages