Chore: Update all links in the codebase and documentation to https (#…

…2947)

* chore: update all http:// instances in codebase to https://
* docs: search/replace from http:// to https://

.editorconfig

@@ -2,7 +2,7 @@
 # editorconfig.org
 
 # WordPress Coding Standards
-# http://make.wordpress.org/core/handbook/coding-standards/
+# https://make.wordpress.org/core/handbook/coding-standards/
 
 root = true
 

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -17,7 +17,7 @@ body:
 
       Thanks for taking the time to fill out the issue form. We can help best if you provide as much information as possible.
 
-      Is this a support or usage question? Please post it to [Discussions](https://github.com/timber/timber/discussions) or on Stack Overflow (http://stackoverflow.com/questions/tagged/timber) using the *Timber* tag.
+      Is this a support or usage question? Please post it to [Discussions](https://github.com/timber/timber/discussions) or on Stack Overflow (https://stackoverflow.com/questions/tagged/timber) using the *Timber* tag.
 - type: textarea
   attributes:
     label: Expected Behavior

.github/ISSUE_TEMPLATE/config.yml

@@ -1,4 +1,4 @@
 contact_links:
   - name: Support or usage question for Timber
-    url: http://stackoverflow.com/questions/tagged/timber
+    url: https://stackoverflow.com/questions/tagged/timber
     about: Is this a support or usage question? Please post to Stack Overflow using the Timber tag.

.github/SUPPORT.md

@@ -1,6 +1,6 @@
 # Looking for support? We want to help
 
-Please post your question to Stack Overflow (http://stackoverflow.com/questions/tagged/timber) using the Timber tag.
+Please post your question to Stack Overflow (https://stackoverflow.com/questions/tagged/timber) using the Timber tag.
 
 ## Other places
 

composer.json

@@ -36,7 +36,7 @@
       "homepage": "https://github.com/timber/timber"
     }
   ],
-  "homepage": "http://timber.upstatement.com",
+  "homepage": "https://timber.upstatement.com",
   "support": {
     "issues": "https://github.com/timber/timber/issues",
     "source": "https://github.com/timber/timber",

docs/v1/getting-started/setup.md

@@ -14,7 +14,7 @@ Underneath this text you will find an extensive list with guides and the reasons
 
 ### ~~Via WordPress.org (easy)~~
 
-~~You can grab the all-things-included plugin at [WordPress.org](http://wordpress.org/plugins/timber-library/) either through the WordPress site or through the Plugins menu in the backend. Then skip ahead to [using the starter theme](#use-the-starter-theme).~~
+~~You can grab the all-things-included plugin at [WordPress.org](https://wordpress.org/plugins/timber-library/) either through the WordPress site or through the Plugins menu in the backend. Then skip ahead to [using the starter theme](#use-the-starter-theme).~~
 
 ### Via Composer (recommended)
 

docs/v1/getting-started/theming.md

@@ -189,7 +189,7 @@ $args = array(
 $context['posts'] = Timber::get_posts( $args );
 ```
 
-You can find all available options in the documentation for [WP_Query](http://codex.wordpress.org/Class_Reference/WP_Query).
+You can find all available options in the documentation for [WP_Query](https://codex.wordpress.org/Class_Reference/WP_Query).
 
 ### Use a WP_Query string
 

docs/v1/getting-started/twig-tools.md

@@ -7,9 +7,9 @@ The purpose of this page is to identify helpful tools for working with Twig.
 ## Text editor add-ons
 
 * Text Mate & Sublime text bundle – [Anomareh's PHP-Twig](https://github.com/Anomareh/PHP-Twig.tmbundle)
-* Emacs – [Web Mode](http://web-mode.org/)
+* Emacs – [Web Mode](https://web-mode.org/)
 * Geany – Add [Twig/Symfony2 detection and highlighting](https://wiki.geany.org/howtos/geany_and_django#twigsymfony2_support)
-* PhpStorm – Built in coloring and code hinting. The Twig extension is recognized and has been for some time. [Twig Details for PhpStorm](http://blog.jetbrains.com/phpstorm/2013/06/twig-support-in-phpstorm/).
+* PhpStorm – Built in coloring and code hinting. The Twig extension is recognized and has been for some time. [Twig Details for PhpStorm](https://blog.jetbrains.com/phpstorm/2013/06/twig-support-in-phpstorm/).
 * Atom – Syntax highlighting with the [Atom Component](https://atom.io/packages/php-twig).
 
 ## WordPress tools
@@ -19,9 +19,9 @@ The purpose of this page is to identify helpful tools for working with Twig.
 
 ## Other
 
- * [Watson-Ruby](http://nhmood.github.io/watson-ruby/) – An inline issue manager. Put tags like `[todo]` in a Twig comment and find it easily later. Watson supports Twig as of version 1.6.3.
+ * [Watson-Ruby](https://nhmood.github.io/watson-ruby/) – An inline issue manager. Put tags like `[todo]` in a Twig comment and find it easily later. Watson supports Twig as of version 1.6.3.
 
 ## JavaScript
 
 * [Twig.js](https://github.com/justjohn/twig.js) – Use those `.twig` files in the Javascript and AJAX components of your site.
-* [Nunjucks](http://mozilla.github.io/nunjucks/) – Another JS template language that is also based on [Jinja2](http://jinja.pocoo.org/docs/)
+* [Nunjucks](https://mozilla.github.io/nunjucks/) – Another JS template language that is also based on [Jinja2](https://jinja.pocoo.org/docs/)

docs/v1/getting-started/video-tutorials.md

@@ -35,7 +35,7 @@ You can find a guide on [how to get started with Composer](https://getcomposer.o
 
 ### Option 3: Via WordPress plugins directory (for non-developers)
 
-If you’d prefer one-click installation, you should use the [WordPress.org](http://wordpress.org/plugins/timber-library/) version.
+If you’d prefer one-click installation, you should use the [WordPress.org](https://wordpress.org/plugins/timber-library/) version.
 
 * * *
 
@@ -45,7 +45,7 @@ Now just activate in your WordPress admin screen. Inside of the timber directory
 
 ## 2. Including a Twig template and sending data
 
-[![Installing Timber](http://img.youtube.com/vi/SlMonnwVi5M/0.jpg)](http://www.youtube.com/watch?v=SlMonnwVi5M)
+[![Installing Timber](https://img.youtube.com/vi/SlMonnwVi5M/0.jpg)](https://www.youtube.com/watch?v=SlMonnwVi5M)
 
 In which we use an existing WordPress template and implement a very simple Timber usage.
 
@@ -76,7 +76,7 @@ Timber::render( 'welcome.twig', $context );
 
 ## 3. Connecting Twig to your WordPress Admin
 
-[![Connecting Timber](http://img.youtube.com/vi/C7HtYkaG2DQ/0.jpg)](http://www.youtube.com/watch?v=C7HtYkaG2DQ)
+[![Connecting Timber](https://img.youtube.com/vi/C7HtYkaG2DQ/0.jpg)](https://www.youtube.com/watch?v=C7HtYkaG2DQ)
 
 ```php
 <?php
@@ -100,7 +100,7 @@ Timber::render( 'welcome.twig', $context );
 
 ## 4. Converting HTML to Twig Templates
 
-[![Connecting HTML Templates](http://img.youtube.com/vi/BxazrNBLK-0/0.jpg)](http://www.youtube.com/watch?v=BxazrNBLK-0)
+[![Connecting HTML Templates](https://img.youtube.com/vi/BxazrNBLK-0/0.jpg)](https://www.youtube.com/watch?v=BxazrNBLK-0)
 
 ```php
 <?php
@@ -121,7 +121,7 @@ Timber::render( 'home-main.twig', $context );
 
 ## 5. Using Custom Post Types with Timber + Twig
 
-[![Using Custom Post Types with Timber](http://img.youtube.com/vi/19T0MStDLSQ/0.jpg)](http://www.youtube.com/watch?v=19T0MStDLSQ)
+[![Using Custom Post Types with Timber](https://img.youtube.com/vi/19T0MStDLSQ/0.jpg)](https://www.youtube.com/watch?v=19T0MStDLSQ)
 
 **home-main.twig**
 

docs/v1/guides/acf-cookbook.md

@@ -2,7 +2,7 @@
 title: "ACF Cookbook"
 ---
 
-Timber is designed to play nicely with (the amazing) [Advanced Custom Fields](http://www.advancedcustomfields.com/). It's not a requirement, of course.
+Timber is designed to play nicely with (the amazing) [Advanced Custom Fields](https://www.advancedcustomfields.com/). It's not a requirement, of course.
 
 While data saved by ACF is available via `{{ post.my_acf_field }}` you will often need to do some additional work to get back the _kind_ of data you want. For example, images are stored as image ID#s which you might want to translate into a specific image object. Read on to learn more about those specific exceptions.
 
@@ -161,7 +161,7 @@ Similar to repeaters, get the field by the name of the flexible content field:
 		<p class="caption">{{ Image(media_item.image).caption }}</p>
 		<aside class="notes">{{ media_item.notes }}</aside>
 	{% elseif media_item.acf_fc_layout == 'video_set' %}
-		<iframe width="560" height="315" src="http://www.youtube.com/embed/{{ media_item.youtube_id }}" frameborder="0" allowfullscreen></iframe>
+		<iframe width="560" height="315" src="https://www.youtube.com/embed/{{ media_item.youtube_id }}" frameborder="0" allowfullscreen></iframe>
 		<p class="caption">{{ media_item.caption }}</p>
 	{% endif %}
 {% endfor %}
@@ -237,7 +237,7 @@ $context["acf"] = get_field_objects($data["post"]->ID);
 
 ## Query by custom field value
 
-This example that uses a [WP_Query](http://codex.wordpress.org/Class_Reference/WP_Query) array shows the arguments to find all posts where a custom field called `color` has a value of `red`.
+This example that uses a [WP_Query](https://codex.wordpress.org/Class_Reference/WP_Query) array shows the arguments to find all posts where a custom field called `color` has a value of `red`.
 
 ```php
 <?php

docs/v1/guides/cookbook-images.md

@@ -26,7 +26,7 @@ Note: If the WordPress size (e.g `medium`) has not been generated, it will retur
 
 ## Arbitrary resizing of images
 
-Want to resize an image? Here we’re going to use [Twig Filters](http://twig.symfony.com/doc/filters/index.html).
+Want to resize an image? Here we’re going to use [Twig Filters](https://twig.symfony.com/doc/filters/index.html).
 
 ```twig
 <img src="{{ post.thumbnail.src|resize(300, 200) }}" />
@@ -95,7 +95,7 @@ Unfortunately, it’s not possible to use the `|retina()` filter in combination
 
 ## Using images in custom fields
 
-Let’s say you're using a custom field plugin (like the amazing [Advanced Custom Fields](http://www.advancedcustomfields.com/)). You can use the resulting images in your Twig templates very easily.
+Let’s say you're using a custom field plugin (like the amazing [Advanced Custom Fields](https://www.advancedcustomfields.com/)). You can use the resulting images in your Twig templates very easily.
 
 When setting up your custom fields you’ll want to save the `image_id` to the field. The image object, url, etc. _will_ work but it’s not as fool-proof.
 

docs/v1/guides/custom-page-templates.md

@@ -29,7 +29,7 @@ This is telling PHP to first look for a Twig file named `page-{{slug}}.twig` and
 
 ## Custom PHP File
 
-If you need to do something special for a page in PHP, you can use the standard WordPress [template hierarchy](http://codex.wordpress.org/Template_Hierarchy) to gather and manipulate data for this page. In the example above, you would create a file
+If you need to do something special for a page in PHP, you can use the standard WordPress [template hierarchy](https://codex.wordpress.org/Template_Hierarchy) to gather and manipulate data for this page. In the example above, you would create a file
 
 `/wp-content/themes/my-theme/page-about-us.php`
 
@@ -51,7 +51,7 @@ Create a file with the following comment header:
 
 In the WordPress admin, a new entry will be added in your page’s list of available templates like so:
 
-![](http://codex.wordpress.org/images/thumb/a/a3/page-templates-pulldown-screenshot.png/180px-page-templates-pulldown-screenshot.png)
+![](https://codex.wordpress.org/images/thumb/a/a3/page-templates-pulldown-screenshot.png/180px-page-templates-pulldown-screenshot.png)
 
 * Name it something like `/wp-content/themes/my-theme/template-my-custom-page.php`.
 * Do **NOT** prefix the filename with `page-` or WordPress will get very confused due to [WordPress template hierarchy](https://developer.wordpress.org/themes/basics/template-hierarchy/#single-page).

docs/v1/guides/debugging.md

@@ -124,7 +124,7 @@ The [**Timber Debugger**](https://github.com/djboris88/timber-debugger) package
 
 ## Using Timber Debug Bar plugin
 
-There’s a [Timber add-on](http://wordpress.org/plugins/debug-bar-timber/) for the [WordPress debug bar](https://wordpress.org/plugins/debug-bar/).  
+There’s a [Timber add-on](https://wordpress.org/plugins/debug-bar-timber/) for the [WordPress debug bar](https://wordpress.org/plugins/debug-bar/).  
 **Warning:** this currently requires PHP 5.4.
 
 ## Using (Legacy) Timber Filters

docs/v1/guides/escapers.md

@@ -14,7 +14,7 @@ if ( class_exists('Timber') ) {
 
 ## General Escapers
 
-Twig offers a variety of [escapers](http://twig.symfony.com/doc/filters/escape.html) out of the box. These are intended to escape a string for safe insertion into the final output and there are multiple functions to conform to the strategy dependant on the context. In addition, Timber has added some valuable custom escapers for your WP theme. To use the escaper (see documentation link above) you use pipe your content through a function `e` if you want to use a custom escaper you would supply an argument to the function, e.g. `e('wp_kses_post')`
+Twig offers a variety of [escapers](https://twig.symfony.com/doc/filters/escape.html) out of the box. These are intended to escape a string for safe insertion into the final output and there are multiple functions to conform to the strategy dependant on the context. In addition, Timber has added some valuable custom escapers for your WP theme. To use the escaper (see documentation link above) you use pipe your content through a function `e` if you want to use a custom escaper you would supply an argument to the function, e.g. `e('wp_kses_post')`
 
 This all follows the WordPress (and greater development philosophy) to:
 
@@ -57,7 +57,7 @@ Uses WordPress' internal `esc_url` function on text. This should be used to sani
 
 **Output**
 
-`<a href="http://google.com"></a>`
+`<a href="https://google.com"></a>`
 
 * * *
 

docs/v1/guides/filters.md

@@ -4,7 +4,7 @@ title: "Filters"
 
 ## General Filters
 
-Twig offers a variety of [filters](http://twig.symfony.com/doc/filters/index.html) to transform text and other information into the desired output. In addition, Timber has added some valuable custom filters for your WP theme:
+Twig offers a variety of [filters](https://twig.symfony.com/doc/filters/index.html) to transform text and other information into the desired output. In addition, Timber has added some valuable custom filters for your WP theme:
 
 ## excerpt
 
@@ -61,7 +61,7 @@ Runs a function where you need. Really valuable for integrating plugins or exist
 Converts an absolute URL into a relative one, for example:
 
 ```twig
-My custom link is <a href="{{ 'http://example.org/2015/08/my-blog-post' | relative }}">here!</a>
+My custom link is <a href="{{ 'https://example.org/2015/08/my-blog-post' | relative }}">here!</a>
 ```
 
 ```html

docs/v1/guides/performance.md

@@ -6,7 +6,7 @@ Timber, especially in conjunction with WordPress and Twig, offers a variety of c
 
 ## tl;dr
 
-In my tests with Debug Bar, Timber has no measurable performance hit. Everything compiles to PHP. @fabpot has an [overview of the performance costs on his blog](http://fabien.potencier.org/article/34/templating-engines-in-php) (scroll down to the table).
+In my tests with Debug Bar, Timber has no measurable performance hit. Everything compiles to PHP. @fabpot has an [overview of the performance costs on his blog](https://fabien.potencier.org/article/34/templating-engines-in-php) (scroll down to the table).
 
 
 ## Cache Everything
@@ -106,9 +106,9 @@ This does not cache the _contents_ of the variables. This is recommended as a la
 
 ## Cache the PHP data
 
-Sometimes the most expensive parts of the operations are generating the data needed to populate the twig template. You can of course use WordPress’s default [Transient API](http://codex.wordpress.org/Transients_API) to store this data.
+Sometimes the most expensive parts of the operations are generating the data needed to populate the twig template. You can of course use WordPress’s default [Transient API](https://codex.wordpress.org/Transients_API) to store this data.
 
-You can also use some [syntactic sugar](http://en.wikipedia.org/wiki/Syntactic_sugar) to make the checking/saving/retrieving of transient data a bit easier:
+You can also use some [syntactic sugar](https://en.wikipedia.org/wiki/Syntactic_sugar) to make the checking/saving/retrieving of transient data a bit easier:
 
 **home.php**
 

docs/v1/guides/testing.md

@@ -43,7 +43,7 @@ $ cd /srv/www/timber
 $ phpunit
 ```
 
-You should see a bunch of gobbledygook across your screen (the whole process will take about 3 mins.), but we should see that WordPress is testing successfully. Hurrah! For more info, check out the [Handbook on Automated Testing](http://make.wordpress.org/core/handbook/automated-testing/).
+You should see a bunch of gobbledygook across your screen (the whole process will take about 3 mins.), but we should see that WordPress is testing successfully. Hurrah! For more info, check out the [Handbook on Automated Testing](https://make.wordpress.org/core/handbook/automated-testing/).
 
 ## Writing tests
 

docs/v1/guides/woocommerce.md

@@ -103,7 +103,7 @@ Create a Twig file according to the location asked by the above file, in this ex
 
     {% do action('woocommerce_before_single_product') %}
 
-    <article itemscope itemtype="http://schema.org/Product" class="single-product-details {{ post.class }}">
+    <article itemscope itemtype="https://schema.org/Product" class="single-product-details {{ post.class }}">
 
         <div class="entry-images">
             {% do action('woocommerce_before_single_product_summary') %}

docs/v1/guides/wp-integration.md

@@ -18,7 +18,7 @@ This differs from `{{ post.post_content }}`, which will display the raw text sto
 
 ## Hooks
 
-Timber hooks to interact with WordPress use `this/style/of_hooks` instead of `this_style_of_hooks`. This matches the same methodology as [Advanced Custom Fields](http://www.advancedcustomfields.com/resources/#actions).
+Timber hooks to interact with WordPress use `this/style/of_hooks` instead of `this_style_of_hooks`. This matches the same methodology as [Advanced Custom Fields](https://www.advancedcustomfields.com/resources/#actions).
 
 Full documentation to come.
 

docs/v2/getting-started/template-inheritance-and-includes.md

@@ -77,7 +77,7 @@ If you look at **single.twig** again, you see opening and closing block declarat
 
 Twig will take the content inside the `{% block %}` tag and put it where you defined your block in **base.twig**. Everything in between `{% block content %}` and `{% endblock %}` in your **single.twig** will go into your `<main>` tag in your **base.twig**.
 
-Blocks are one of the most important and powerful concepts in managing your templates. The official [Twig Documentation](http://twig.symfony.com/doc/templates.html#template-inheritance) has more details.
+Blocks are one of the most important and powerful concepts in managing your templates. The official [Twig Documentation](https://twig.symfony.com/doc/templates.html#template-inheritance) has more details.
 
 While you can define your own custom number of blocks, you can also create any number of base files to extend from (we use the name "base" as a naming convention, but it’s not required).
 

docs/v2/guides/cheatsheet.md

@@ -30,9 +30,9 @@ Timber::render('single.twig', $context);
 
 
 ## Theme
-* `get_template_directory_uri()` => `{{ theme.uri }}` Template directory URI for the active (parent) theme (ex: `http://example.org/wp-content/themes/my-timber-theme`)
-* `get_template_directory_uri()` => `{{ theme.parent.link }}` Explicitly return directory uri of parent theme (ex: `http://example.org/wp-content/themes/my-timber-parent-theme`)
-* `get_stylesheet_directory_uri()` => `{{ theme.link }}` Template directory URI for the active (child) theme (ex: `http://example.org/wp-content/themes/my-timber-theme`)
+* `get_template_directory_uri()` => `{{ theme.uri }}` Template directory URI for the active (parent) theme (ex: `https://example.org/wp-content/themes/my-timber-theme`)
+* `get_template_directory_uri()` => `{{ theme.parent.link }}` Explicitly return directory uri of parent theme (ex: `https://example.org/wp-content/themes/my-timber-parent-theme`)
+* `get_stylesheet_directory_uri()` => `{{ theme.link }}` Template directory URI for the active (child) theme (ex: `https://example.org/wp-content/themes/my-timber-theme`)
 * `get_template_directory()` => `{{ theme.parent.path }}` Explicitly return relative directory path of parent theme  (ex: `/wp-content/themes/my-timber-parent-theme`)
 * `get_stylesheet_directory()` => `{{ theme.path }}` Relative directory path for the active (child) theme (ex: `/wp-content/themes/my-timber-theme`)