WordPress version bumped to 5.2.2

[robert-skarzycki]

Hi, @ellefsen, I've bumped WordPress version on this package - to 5.2.2. Do you have an idea how to deploy it to my already deployed page on Heroku?

[ellefsen]

Thanks! - I'll check it out. You should be able to clone your existing Heroku repo, git clone https://git.heroku.com/your-project.git, update the composer files and push back to origin master to see the changes reflected.

[robert-skarzycki]

Hmm... @ellefsen, I don't understand this: when I do git clone of repo of my app (app that was deployed with instructions here and which is properly working WP page) - it clones an empty repo. So, how does it work: if the repo is empty and the buildpack is just https://github.com/heroku/heroku-buildpack-php - so where are the wordpress-heroku files deployed? 🤔

[john-shaffer]

When you create a new Heroku app, its repository is empty. In this case, you want to pull your branch into your local repo and then push to Heroku. Here's how I did it:

$ heroku create --stack cedar --buildpack https://github.com/heroku/heroku-buildpack-php
Creating app... done, ⬢ agile-chamber-65793, stack is heroku-18
Setting buildpack to https://github.com/heroku/heroku-buildpack-php... done
https://agile-chamber-65793.herokuapp.com/ | https://git.heroku.com/agile-chamber-65793.git

(Set up addons as described in the readme.)

$ heroku git:clone -a agile-chamber-65793
$ cd agile-chamber-65793/
$ git pull https://github.com/robert-skarzycki/wordpress-heroku-php.git
$ git push heroku master

However, your change won't have any effect. After changing composer.json, I had to run composer update in order to update composer.lock. Then I ran

git add .
git commit -m "Update composer.lock."
git push heroku master

Whenever I use composer update (with or without changing the WordPress version), I get a blank 500 page due to changes in the WordPress path. At the moment I'm testing Amazon LightSail for WordPress. They have 5.1.1 preinstalled which I was successfully able to update to 5.2.2.