override createMessage in LoggerPrinter like this:

1:
// return args == null || args.length == 0 ? message : String.format(message, args);
if (args == null || args.length == 0) {
return message;
}
String pattern = "(%\d)?$(a|b|c|d|e|f|g|h|n|s|tx)";
Pattern p = Pattern.compile(pattern);
Matcher m = p.matcher(message);
if (m.find()) {
return String.format(message, args);
} else {
t(me

Ticket: #1434

There are some limitations when getting posts from other pages in a multisite network. Specifically, when you fetch posts from other blogs, you’ll have to prepare the data in advance.

The linked issue has a very good example for this, that I’ve run into myself, too. I think we should document that in a new Multisite Guide.

There’s also some functionality in the [`Timber

I add just one line to get this tutorial working in the single.php file.

This is the tutorial part:

{% extends "single.twig" %}

{% block headline %}
    <h1><img src="/wp-content/uploads/2014/05/jareds-face.jpg" alt="Jared’s Mug"/></h1>
{% endblock %}

That the line i need to add in the single.php file:

Add an option for a front-page.twig template in page.php.

Code is very similar to what we have in index.php

<?php
global $post;

$context   = \Timber\Timber::get_context();
$templates = [ 'page-' . $post->post_name . '.twig', 'page.twig' ];

if ( is_front_page() ) {
	array_unshift( $templates, 'front-page.twig' );
}
Timber::render( $templates, $context );

Timber's various configuration parameters do not consistently support pulling values via a {:system, "VAR_NAME"} tuple. For example, Timber.Config.api_key/0 does, yet [Timber.Config.http_url/0](https://github.com/timberio/timber-elixir/blob/20ec4a520fe94f15b5812337cfc8a54528aff

The bundle command is really handy for installation, but can be a bit "magical." We should put a note in the output (and the configuration file) about what it's actually doing and make sure it is obvious and easy to change.

cc @edisgreat

Issue
The removal of the image sizes automatically generated when uploading an image done here makes the wordpress function image_get_intermediate_size() always return the full size image. However, if the full size image is wider or higher than 2000px, Yoast SEO rejects it as an og:image.