How WordPress is dropping PHP End of Life versions

I was writing the Site Health Check notes from the update meeting the group had at WCUS, and thought they might be useful for people outside the WordPress community too.

Some context

At the 2018 State of the Word, it was announced that WordPress was in the process of increasing the minimum supported version of PHP. This is great news as a PHP developer, but a task like this is not a simple feat.

Lots of work has been happening in the background for years. All the work has now allowed the project to be in a state where WordPress can drop PHP versions which already have EOL. The rest of this post will explain more about how the WordPress project is intending to roll this out.


Site Health Check Project review at WCUS 2018

The Site Health Check project is a collaborative multi-team project with a focus on encouraging better site maintenance.

This project benefits not just WordPress users, but also the surrounding PHP ecosystem as a whole. Our hope is that this will prompt a lot of PHP updates across the web.

It started as a project to focus efforts on getting users to update their hosting version of PHP from 5.2 to something where the End of Life has not already passed.

The project was initially called ServeHappy, homage to the BrowseHappy project which was a global tech effort to move away from Internet Explorer 6. The problem with the project name was that, when tested with users who did not know about the ins and outs of the project, the name was confusing and was not clear what the project’s intentions were.

The project is now known as the Site Health Check project. It encourages and hints to users that if they run a website, they should have a routine of checking and updating not just WordPress but underlying technologies that the site is built on. It also builds positive website ownership and habits.

The project is split into what can be considered 3 parts – changes to WordPress core itself, a site health check plugin and the site health check community support.

Upcoming changes to WordPress Core

The core-centric side of the project still reflects the Servehappy origins. This includes:

  • An information page on WordPress.org explaining the importance of updating PHP. The team has been working on improving the language used to benefit non technical people and have clear instructions of what to do if they find out their site is running an old version of PHP.
  • A dashboard notice that will inform users if their site is running on a PHP version that WordPress considers outdated and plans to drop support for in a future update.
    • The version shown in the dashboard is API-driven which means that WordPress leadership has a centralized “knob” to tune the PHP version distribution.
    • The dashboard includes a link to the previously mentioned information page on WordPress.org which has generic information on what the notice means and how to update PHP.

  • There will be an environment variable or a filter which allows hosting companies to modify the link to the “Update PHP” page on their servers so that it goes to something more relevant for their customers.
    • There are some concerns of security problems and abuse over the link redirection.

  • The team has been working on a feature to add white screen protection, which the hosting group felt was helpful and cool. The white screen protection catches any fatal errors that a PHP update might produce. From the front facing side of the website, the site will still be white screened, but with the protection in place, the user can still access the admin panel.

  • There was a discussion whether it would be better for the site to be slightly broken rather than completely broken, but the general consensus was that it is better to white screen because from the Core Team perspective, they cannot be sure of what the PHP error causes, and thus can’t be sure that all the information being shown is meant to be public.

    It is better to white screen the whole website but ensure that access to the admin panel is still accessible. Once logged in, there will be a general notification regarding the WSOD.

PHP minimum required headers

Plugins

For a while, WordPress plugins have been able to set a minimum PHP required comment as part of the plugin header. To date it has not done anything but set the intention that the plugin author is able to declare what PHP minimum version they are willing to support.

Work is being done so that the Add New Plugin admin screen will show all plugins a user searches for, but will not be able to install any plugins that require a newer version of PHP without updating that first. Another task being worked on is blocking plugin updates if the newer version requires a higher version of PHP, same as it currently works if the update requires a higher version of WordPress.

This gives plugin authors better control of what PHP versions they are willing to support, and will hopefully encourage people to upgrade their version of PHP at the same time.

This change will allow plugin authors the choice to use more modern PHP functionality and syntax without worrying their plugin will break for the end user.

Themes

For themes, the Requires PHP header is not implemented yet, as they didn’t have the same readme.txt file up until recently: https://make.wordpress.org/themes/2018/10/25/october-23rd-theme-review-team-meeting-summary/

Now that new themes do have that requirement, there is an expectation that the header will be implemented as well in the foreseeable future. Here’s a ticket for that: https://meta.trac.wordpress.org/ticket/3718

Relevant Trac Tickets

The latter two trac tickets are currently slated for 5.1 as well, planned for February 21: https://make.wordpress.org/core/5-1/

The feature merge deadline is January 10 though, so it needs to be discussed at the next #core-php meeting whether making it into 5.1 is still feasible.

A prerequisite for these changes is the WSOD protection that needs to be completed and committed by the deadline: https://core.trac.wordpress.org/ticket/44458

Join in

The group has weekly meetings on Mondays 16:00 UTC on in the #core-php channel of WordPress Slack.

GitHub: https://github.com/WordPress/servehappy

Site Health Check Plugin

The site health check plugin is a way for users to be able to see technical details of their website setup without going into the server side of things. It is useful to conducting top level investigation work without accessing the server directly.

The beta version of the plugin takes the best practices from the Hosting Team’s documentation and checks the server against that. This includes: WordPress version number, plugins and themes are up to date, PHP version number, if HTTPS is active across the whole site as well as a number of other things.

When Health Check gives notifications about upgrading things, it hands users off to plain English documentation to walk them through the process. For example: https://wordpress.org/support/update-php/. Notifications for plugins and themes being up to date are based on the version inside the plugin and theme repo. If a theme or plugin is not present in the repo, it will assume it is up to date and will not give an error.

Eventually, a lot of the Site Health Check plugin will be in core.

The Site Health Check Plugin uses a traffic light system to flag up the importance of a suggested change. The definition of critical vs non-critical update notifications is from a security perspective. If it is a security issue, it’s critical.

Early user testing with the community has shown that the plugin suffers from a lack of designer eye. During WCUS, we have had a designer volunteer to review the interface and give feedback.

This should help with the usability of the plugin and balance it between positive reinforcement of things that are set up as guided by best practices whilst not over-burdening people with extra technical information.

There is some useful documentation on how to use the Site Health Check Plugin: https://make.wordpress.org/support/handbook/appendix/troubleshooting-using-the-health-check/

Join in

– Github: https://github.com/wordpress/health-check

– WP.org : wordpress.org/plugins/health-check

Site Health Check Desks & Community Support

In-person support is invaluable. When a user is unsure of what to do, they can find in-person support at their local meetup and WordCamps. To omit any surprises, we can encourage our community to pre-warn and prepare as many people as possible.

The idea of Site Health Check desks has been tested in 3 different WordCamps and 1 meet-up with improvements and suggestions being fed back to the plugin and fliers.

Site Health Checks is an extension of the Happiness Bar, and by asking the simple question “Do you know what version of PHP your website is running?”, people either

  • Know & it is up to date – get a high-five. Thank them for keeping PHP up today and encourage them to keep up the good work. Pre-warn the next EOL of PHP Dates.
  • Know & it is out of date – highlight the EOL date has already passed and recommend they update their PHP version.
  • If they don’t know – check if they know how to check. If they do, suggest that they check and that they want it to be 7.2 or higher. 7.1 EOL is in a year.
  • If they don’t know, and don’t know how to check, invite them to sit down and the volunteers can help them check using the Site Health Check plugin. DO NOT scrape the site. They can end up being blocked off the servers.

Postcards were created with 5 core things to check. As well as printable table toppers. They are used as fliers for people to know where to download the site health check.

Meetup organisers have also shown an interest in running the site health check and promoting it at their meet-ups.

This is where much of the user testing of both the “Update PHP” information page and the Site Health Check plugin is happening.

Plugins and Themes Plans

Plugins and Themes served from WordPress.org can be automatically checked and updated to be compatible with 7.X. This is because there is access to the SVN where these plugins are being pushed from.

Ideally, plugin authors who have a plugin in the plugin repo will update their plugins to be compatible with PHP 7.X. There are already plugins such as the PHP Compatibility Checker which people can use to check how compatible their websites are with a version of PHP.

How are premium plugins and themes going to be handled?

The plugin team at WordPress.org can contact authors, but ultimately it is up to the plugin author to action the suggestions that are made from the WordPress.org team.

If there is no answer, or the author does not wish to fix errors, then this is a dead end.

Target Dates

WordPress 5.1  ->  ServeHappy notice + White Screen of Death protector

WordPress 5.2 ->  Site Health Check plugin

Where hosting companies come into play

We would like hosting companies to go aggressively, pushing their communities forward before WordPress does.

We know that, as a hosting company, many of you will see the same issues come up during a PHP update. It would be useful to the rest of the group if any information of any PHP errors that are being seen repeatedly and information about which plugin or theme is causing it. It will allow the rest of the team to prioritise which plugins and themes need attention to be fixed across the whole community.

It will also help the support team if any solutions are found to be shared, so that they know what to be suggesting in the forums. We may be able to add notices before a PHP update into the health check which highlights problematic plugins.

Hosts with PHP lower than 5.6 may see some initial notifications before that date.

Hosting company teams are most likely to know other people working in the hosting sector. Above all else – get the word out.  Big hosts are represented well here, but as a community we are aware and worried about the smaller, independent hosters. Talk to your hosting friends. Let them know this is coming. Invite the small hosting companies to join the Hosting Team on WordPress.org for up to date information of what is upcoming and will be effecting hosters.

The more we can update in batches the less burden there is across the whole industry.

Where plugin and theme authors come into play

If plugin and theme authors ensure that their plugins have a PHP minimum version set in their required header, then their plugins and themes will be ready once the PHP requirement is being enforced.

Plugin and theme authors should also ensure that their plugins are compatible with PHP 7.X. Tools such as PHP Code Sniffer (PHPCS) or the PHP Compatibility Checker as mentioned above should help.

Where developers come into play

(This section is not in the original notes)

There are many different skill sets amongst developers. Knowledge sharing and supporting each other getting plugins, themes and custom code PHP 7+ compatible is important. There are many resources already out there from when the PHP community was moving to PHP7+ but many of those resources have not been shared with the WordPress community.

Sharing those resources once again would be a great help to the whole community. We can learn from what has come before.

Actions from the meeting

– Ensure there is communication with the hosting team regarding release date plans.

–  #core-php should be cross posting ServeHappy notes to the Hosting P2 as well.

– WordPress.hosting has been taken, unsure by who. It would be handy to have WordPress.hosting symlink to Hosting Team P2 to help getting other hosting companies to join the Hosting Team

– Recommend that Hosting Team check and sync up the Best Practices documentation.

– Can someone from the hosting team please review and ensure that Health Check plugin is checking against everything that exists in the “Hosting Best Practices” doc.

– Recommended to Health Check plugin to check out Lighthouse plugin UI.

– Write up more in-depth info for meetup and WordCamp organisers, have postcard and table toppers online so they can be shared and translated easily.

Thanks

The effort to raise the minimum PHP version requirement of WordPress is a big cross- team effort. Big thanks to

2018

The year I called it a day on a 12 year relationahip. What ever hopes, dreams and plans I had for 2018, they all came to a pretty conclusive stop as I moved around looking for somewhere to call home and trying to stay emotionally afloat. 

It’s times like that where letting life do its thing rather than trying to be in control of it all has been helpful. Its has meant that many intentions have gone unactioned and for everyone that has affected, I’m truly sorry. 

I took chances in my life I never thought I would and I’m glad I did. I’m really thankful for everyone’s patience, support and space when I needed it the most. 

I stopped talking to many people i consider friends. The lack of willingness on my part of wanting to talk about what happened was not something I wanted to do on repeat and I’m really grateful I have friends who understood all I wanted was a hug and to know I could talk to them when I wanted. I’m really sorry the downside has been that for many of my friends it has meant I have been pretty silent. 

I hope to do better this year. 

I ended the year with a house I’m now calling home, surrounded by a group of friends, playing monopoly, and drinking tea. 

2018, you started with hopes that came crashing down one night. But you taught me that sometimes things come to its natural end. I called it a day on one chapter and it allowed me to open up another.  You taught me dynamics in a relationship can change and from darkness, friendships can bloom.

Thanks for the reminder that I can stand on my own two feet.

Love, 

Jenny

Starting a conversation at a conference

I’ve been asked a few times how to start a conversation with people. It’s not easy or always natural or something you want to be in the mood for so I’ve compiled some stuff i share with people when i give talks. 

Make sure you eat well and stay hydrated!

Make sure we’re fuelled up and not hangry.If I’m hungry i’ll be in a bad mood, starting conversations with people only makes peopel dislike me. I can usually solve this with food and a cup of tea.

Assign yourself the Greeter role.

Toastmasters have this role called a Greeter at their meetups. When it’s a designated role that you are assigned, it helps me give myself permission to talk to other people.

The Greeter's role is to welcome everyone to the club meeting, particularly visitors and people who are new. Making everyone feel welcome at our club is important, as this may be the start of their journey.
Toastmaster’s definition of the  Greeter’s Role 


Tweet out you want to meet new people.

It might seem wierd, but many people attend events on their own and are looking to meet new people. Use the Hashtag of the event and tweet out that you want to meet new people and would love to talk to people about partiulcar topic.Include a picture of what you are wearing  so people know what you look like and can find you.

Start a conversation.

Starting a conversation isnt easy. Having conversation starter questions helps. Here is a bunch of questions I frequently ask:

  • Have you travelled far?
  • What kind do you do with WordPress?
  • What session are you planning?
  • Been to any interesting sessions?
  • What did you think of the topic?
  • How did you get started with WordPress?
  • Comment on the weather.

Engage Pac-Man rule

If you haven’t heard about the pac-man rule, then read more about it  on Eric’s blog post about it.The it tries to solve the problem of allowing new people to join conversations, by giving people explicit permission to join groups.

The rule is:

When standing as a group of people, always leave room for 1 person to join your group.

More memorably, stand like Pac-Man!

The new person, who has been given permission to join your group, will gather up the courage, and join you! Another important point, the group should now readjust to leave another space for a new person.

Leaving room for new people when standing in a group is a physical way to show an inclusive and welcoming environment. It reduces the feeling of there being cliques, and allows people to integrate themselves into the community.

Eric Holscher

Break the Clique

It is habit that we all hang out. we’re comfortable with each other as a company as its less effort for us overall. Eric also wrote a post called Break the Clique.

The Community++ Rule [1]

The rule is:

For every year you have attended the event, you should try to meet that many new people each day.

An example makes it clear:If you have attended this event for three years, you should try to meet three new people each day.

Consider this your encouragement to do the Community++ Rule.

Eric Holscher

People are just people

People don’t always want to talk about work, or tech, they are people afterall, so ask a random question to break the ice.

Set yourself a challenge to meet X number of new people and find out if they prefer cats or dogs, if they are Team Tea or Team Coffee.

You’ve got this.

You at some point already met a bunch of new people. We are continually doing this and the event you are going to will be no different.

You’ve got this.

Have a personal favourite? 

If you have any tips or tricks on how you start conversations with people, please share them. I would love to know how others cope with meeting new people. 

It’s going to be ok – thoughts on WordPress 5.0

Morning! 5.0 is set to launch today.

It’s the release of hard work across the community-vocal & non vocal. Thank you for that hard work regardless in what format.

It means we can stop debating when the release is which will at least curb my anxiety.

I hope it means we can move forward and ship other improvements that are not Gutenberg related.

An upside is that it means Gutenberg codebase will be less violatile, which means we know what we are getting.

Another upside is that this is not a security release which means it will not trigger WordPress’s auto update. Which means ( I don’t believe I’m saying this ) you don’t need to update to 5.0 straight away. Do it when you are ready and comfortable.😀

I suspect once the release is out, many people will be blogging and writing tutorials of how to do stuff as we learn together.

Let’s make a conscious effort to make our tutorial and blog code examples show off accessible code. You know we’re going to be copying it. 😜

I haven’t fully kept up to date with the progress of core, because i have faith in the team. They are not concerned so I’m not. The HM team will have 100 paper copies of our Gutenberg white paper at , find a HM team member for a copy.

This WordPress release is not where I would have liked to have seen it or what I would have hopedto have invluded, but my focus has been elsewhere and I wasn’t the release lead.

Once Gutenberg has been shipped and is out of the limelight, we can get back to shipping other things. E.g. the Site Health Check project, which means we can encourage everyone to understand and continually update their version up to 7.1 and above.

Also means all the privacy teams work can go back in and I heard the multisite team have a bunch of improvements too.

I’m really grateful we’ve all been vocal about our concerns and many of us are excited by the new editor but dissatisfied with some of the process around it. Whether that’s the accessibility, HTML markup, the moving target date, the communication, the long form experience etc. People will learn from it. I’ve seen improvements, and there’s room for more improvements.

I’m excited by and other projects people have spun from all this. I think choice is great ( as long as it’s an open source choice ) Our sites and our content is our digital memories and we need to own these things rather than giving ownership to others.Open source allows us to own our own content. And that’s what I care about. The choice of open source CMS is ours and I look forward to a more colourful future of choices!

🌻🌻🌻🌻🌻🌻

Useful GitHub Features

Nearly everyone at work uses GitHub so I shared some neat GitHub features I had recently come across. This post is a edited version of that post.

Note that many of these features interlink with each other so if you are going to use any of these features do think carefully which order you do things otherwise you will be going back on yourself to update links etc.

If you have any questions feel free to ask questions here or on Twitter.

P.S.

I just finished writing this and realise it’s rather long. Sorry!

I hope it’s useful to you. 🙏


Continue reading “Useful GitHub Features”

A proposal for changing the WordPress versioning scheme

History

Currently, WordPress uses a incrementing numeric versioning system. XX.YY.ZZ could be read as ma.jor.patch which means version 4.8.1 can be read as version 48.1.

At the 2017 community summit, someone suggested that as WordPress project moves towards 5.0, that after 4.9 the versioning system should switch to semantic versioning by multiplying the versioning number by 10. This would mean the next version number after 4.9 woudl be version 50. The idea was shot down because if an end user is on 4.9 and then all of a sudden see the next version of WordPress was version 50; they would wonder where version 5-49 will freak out.

Proposal

I propose that at the point of 4.9 we switch to semantic-like versioning.

Semvar is designed to be

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards-compatible manner, and
  • PATCH version when you make backwards-compatible bug fixes.

Since WordPress has a don't break backwards compatiblity mentality, it would not make sense to follow the Semvar 2.0 spec.

Instead I propose something similar but in WordPress terms.

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR – New Feature : when there is a major feature change,
  • MINOR – Bug Fixes : when you add scheduled bug fixes in a backwards-compatible manner, and
  • PATCH – Security : when you make security fixes in a backwards-compatible manner.

It would mean that 4.9 is a minor changes from 4.8 and does not require any major feature releases. It would also mean that until there is a major feature change, version numbers can keep increasing as minor updates. This would mean until the next major feature drop, bug fixes and gardening releases can be scheduled in a timely manner in versions 4.10.0, 4.11.0 etc release cycles.

It would also mean that we can wait till a large feature drop before upping the versioning number to 5.0 and then from then onwards any major feature drops or breaking changes can pulled into the next major versioning number.

Notes

  • After throwing this idea around with a few developers to see what the inital reaction would be, some developers have asked whether it would mean that we would never get to 5.0 because *major = breaking changes*. I disagree that a major release has to be a breaking change. From my understanding of semantic versioning methodology, we should be able to define what `major`, `minor` and `patch` means to the WordPress team and run with that.
  • I know this is a far-fetch idea that will not be popular with many people, but if we were ever going to switch versioning number, I think this is a realistic method of doing so. Doing it now would mean that we don’t have to wait till WP5.0 before any more minor releases come out.
  • I am sure there are many flaws in this idea that some people who are way more clued up with the WordPress versioning and rollout process can point out. Just remember its a proposal/ idea/ a dream. I’m ok with it staying just that.
  • WordPress is not the only popular piece of software not on Semvar and it seems to be developers who care about the software versioning system of the project.
  • If you want to read up more about different software versioning systems; Wikipedia is your friend.

 

Stage Fright

Last week I did the opening keynote for PHPUK.

It’s not the first time I have keynoted, but it is the first opening keynote.

Do I get scared?

Many people since have asked if I get scared or stage fright beforehand.

Yes, i get scared.

It doesn’t matter if I am standing in front of a user group or a conference hall full of people, I will always get stage fright. It is usually the worse the last hour before I’m due on.

My brain runs through various issues:

  • What if i am too negative?
  • What if I forget the bridging phrase / point?
  • What if I am too monotone?
  • What if I have no colour of variety in my voice?
  • What if people fall asleep?
  • What if I mispronouce someone’s name?
  • What if there is a spelling mistake I missed?
  • What if my ankle gives way on stage?
  • What if I have a wardrobe malfunction?
  • What if I am too bossy?
  • What if my laptop breaks?
  • What if I drink some water and spill it on my laptop?

So on and so forth.

I don’t think these worries have gotten better or worse over time. The most I can do is control as much of it as possible.

Someone once told me that

No one wakes up wanting to see you fail.

This is open source community. From everything I have experienced in the last 8 years in this community, people are always cheering you on to do your best and are cheering you on to be your best.

So as long as i try my best, do my best, I’m ok accepting that stage fright is part of the parcel for me.

Controlling Stage Fright

There are a few things i do to control my stage fright and not let it run a drift.

Hopefully this will help you:

  • Have a USB copy of the presentation  with font files and images in Keynote, PPX and PDF.
  • Have a public dropbox folder of the presentation  with font files and images in Keynote, PPX and PDF shared with the organisers, yourself, and a friend in the room.
  • Test out the wardrobe choice on a night out with friends. If it passes a fun night out with friends where you are more likely to be moving around, it will be fine on stage where you don’t move around so much.
  • Break new shoes in. I tend to go on a trip with new shoes and walk a lot to break them in.
  • Have backup batteries for your clicker in the bag
  • Go to tech test early.
  • Have a version of your slides with a white background and a version with a black background. Depending on how bad the projector is, you can switch colour contrast quickly.
  • Have versions both in 16:9 and 4:3 because seriously the effort v the stress isn’t worth it.
  • Do not change slides on the day unless you REALLY have to. People will not miss one extra meme.
  • Set a run-though date with friends a week a head of time to :
    1. Force me to have a draft version of my talk  “ready”
    2. Give you feedback where it doesn’t flow and help you tweak the talk.
    3. Remember to write down the feedback
  • Video your practise runs. It means you can go back and write down that cool phrase you just made up which helped bridge two parts together as speaker notes.
  • Practise in front of people who don’t care about the content is useful. I found they tend to concentrate on your speaker style and point out things that are nothing related to the content.
  • Ask someone you trust and knows the subject to review the content.
  • Always leave a caveat and be honest if you are uncertain about data.
  • If my talk is in the morning, I have a super big dinner the night before. I know I will not stomach anything in the morning so i just eat ahead of time. Also I carry snack bars so I can eat straight after I come off stage.
  • Turn off the air con in the hotel room, and wrap that neck up! I find air cons dry out my voice and my voice breaks easily if its cold so i wear a scarf to stop that from happening. Airplane air cons are just as bad.
  • Know where the bathroom is so you can do a last minute bathroom run.  Nothing like drinking lots of tea to warm up the voice and then needing the bathroom 🤭
  • Whether you submitted to a CFP or got a invite, the organizers of the event are the people who curated the schedule so trust them. They thought your talk was interesting enough to put on stage.
  • Have a playlist of your favourite tunes and stick your headphones on and forget the world. I find that I have far too much adrenaline before i go on stage so if I can, I spend a bit of time before my talk where I  stick in my headphones and listen to a playlist I have saved offline.  I find I only really get through the first 5 songs at most so make sure the first song is one that ground you! This is my go to  playlist:
  • The talk is only going to be [ Insert session time amount here ]. In a year/ life time that is going to equate to a very insignificant amount of your time.
  • We’re not performing heart surgery.
  • You’ve got this. 

Hello SiteGround!

Today I’ve move my hosting to something I’m going to maintain myself again.

It’s been a while since I bothered to actually deal with any hosting providers of any sorts.

Work has a servers team, and beforehand all my personal sites have been hosted on my partner’s server. Both these things were making me insanely lazy when it came to caring about hosting and running a site.

I figured it was making me rusty and out of touch with what people have to deal with.

I’ve not seen a cpanel in such a long time! It hasn’t changed a bit! Still the same ugly 90s icons. It’s like a little time warp.

Moving server I decided to build teh site from scratch.

Things i did :

– use wp auto installerto install a multisite setup using sub directories. ( It didn’t give me a choice )

– forgot to save the admin password that was geenrated so ended up adding ssh keys to be able to  ssh into the box via terminal and use wp-cli to update the user’s password.

– Set up domain mapping plugin

– Use https://casabona.org/2016/12/migrating-wordpress-multisite-from-media-temple-to-siteground/ to understand how to set up domain mapping for domains registered on Gandi and the site hosted on SiteGround. The article details how to do it for a site being moved, but in my case, everything was from scratch.

  • There was some notable doh moments.
    • Wasn’t sure if Let’s Encrypt is a domain issue or a hosting issue – It’s hosting.
    • Needed to create a Let’s Encrypt Cert for every domain. There is a Cpanel icon to do just that; keep scrolling down in Cpanel to find it.
    • Set up DNS records on the domain registar to point to SiteGround
    • use cpanel’s <code>add-on domain</code> to link the domain hosting to the WordPress installation of the primary site
    • SSH key password doesn’t seem to like the auto generated passwords that i created with 1password. I suspect there was a symbol i needed to escape but i couldnt be bothered so just used the built in password generator in SiteGround’s SSH Key generator to get a password it would be happy with and saved it to 1password. It seems like an obvious thing, but I’m too used to creating all my passwords via 1password.
    • Waiting for DNS to update.