-
Notifications
You must be signed in to change notification settings - Fork 5
Error upgrading to WordPress 4.9.2 #86
Comments
This says that support for The require-dir in the current yarn.lock though is already specified as 0.3.2. I'm not sure what that script is doing (where can I see it again?), but it looks like the incorrect node libs are installed (which is resolved by running Also, if you update composer.json, you must also run Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them. |
Cheers @nicksellen, the update script is here, if it is any help the server is running: node -v
v8.9.4 I'll install yarn tomorrow, don't have the time right now, thanks for looking at this :-) |
Ok, I'd suggest switching the |
So,
Something needs changing in the update script: I guess? This is the full output:
Incidently I could enable SSH access which would allow people with public keys on the server to do things like use WP-CLI and everything else… |
Random internet trawling, but from composer/composer#754 (comment), could you add |
Thanks @lwm, but there is still this warning:
And also the updates still haven't been applied and there are now also three more outstanding:
|
Perhaps that is a clue — none of the latest three ACF plugins with updates apper to be listed in the composer.json file — could someone have installed plugins using the WordPress web interface and this has stopped updates via |
The repository should hold a valid combination of The current state of json/lock files in the repo (dev branch) is invalid, as running Running
It's specified as 1.8 which doesn't seem to exist, so I swapped it to 1.8 and ran composer update, and all went fine (I pushed those changes to https://github.com/cotech/website/tree/fixup-composer - all from dev branch, not sure which branch you are working on). |
Cheers @nicksellen, I'm working on the |
I clicked the update link here and now there is a 1.8, sorry I didn't see that error before. |
However I'm afraid there is still the core problem outstanding the updates haven't been applied and I still don't understand why. |
Thanks for your help with this @nicksellen, I needed to RTFM 😊, however the site hasn't updated to WordPress 4.9.2 — is that because |
Sorry there is a tag for 4.9.2. |
So, I'm suck again I'm afraid, the dev site is promoting for an update, but the files are updated:
What am I doing wrong now? |
I have just tried updating to WordPress 4.9.4, see 78183af, but again this hasn't made a difference to the version the dev site is running — anyone have any idea what am I doing wrong? |
Ah, sorry it's been so frustrating @chriscroome, especially when you are very happy doing these things using the normal way of using wordpress. At the moment I am suspecting it's because in the setup script wordpess is installed if it's not already there. It might be that it only copies the wordpress files across at that point. I have not confirmed this theory though. I'll add it to my task list to investigate that :) |
Thanks @nicksellen, the weird thing is that it used to work without a problem, for example I'm sure we didn't have this problem in November, also the servers hosting the dev and live sites are not running the site in Docker so I'm not sure how the |
Aha! I've found the issue, it was the switch from https://discourse.roots.io/t/johnpbloch-wordpress-moved-to-a-new-configuration-and-wp-goes-missing/9124/45 has a few details, might need a cache clear. Locally now (using docker-compose setup), I can switch between the versions and it all works fine, the steps for changing the version are:
On server, it should just be:
|
I pushed updates to dev branch (I actually meant to push to another branch but mangled my git commands :/ ) |
That does sound like the probably cause of this issue, the update script is run after changes in the repo, via a crontab and that contains: WP=$(which wp)
composer install
${WP} core update-db But the dev site still hasn't updated… so we arn't quite there yet… |
I tried this suggestion on the dev server: cd ~/sites
composer remove johnpbloch/wordpress
composer clear-cache
composer require johnpbloch/wordpress:4.9.4 And that seems to have done the trick :-) |
Great :) I think/hope that's just a one-off thing to run, seems like johnpbloch totally changed what is in the package but gave it the same name and versions (as they match the wordpress ones), which would understandably confuse composer. |
For some reason this doesn't appear to work on the live server, I'm not sure why, it was fine on the dev server:
The odd thing is that the
Are this is what we have in the repo. so did I mess the merge request up? I wanted to merge dev into master... |
Do'h, the merge hasn't been completed! |
I have updated
composer.json
on thedev
branch to change these lines:When the update script it run it generates this error:
Anyone know what the problem is and how to fix it?
The text was updated successfully, but these errors were encountered: