Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wp update checksum locale issue #74

Open
runningman84 opened this issue Jul 6, 2018 · 1 comment
Open

wp update checksum locale issue #74

runningman84 opened this issue Jul 6, 2018 · 1 comment

Comments

@runningman84
Copy link

runningman84 commented Jul 6, 2018

I have a bunch of machines which have been updated to the latest 4.9.7 release. These machines have a cronjob which daily executes this:

wp core update --minor

These machines also have the German locale pack installed. In order to prevent security issues we also check the ckecksum every hour:

/usr/local/bin/wp checksum core

Recently the update bump wordpress release from 4.9.8 to 4.9.7. Unfortunately all machine showed checksum errors because the wp-config-sample.conf had German content.

I haven't been able to reproduce this. Replacing the wp-config-sample.conf from the English wordpress release fixed it.

Funny enough you cannot force an update to the English installation once you have the German locale pack installed:

www-data@<some-host>:/data/backend/wordpress$ /usr/local/bin/wp core update --locale=en_US
Updating to version 4.9.7 (de_DE)...
PHP Warning:  mkdir(): Permission denied in phar:///usr/local/bin/wp/php/WP_CLI/FileCache.php on line 265
Warning: mkdir(): Permission denied in phar:///usr/local/bin/wp/php/WP_CLI/FileCache.php on line 265
Herunterladen der Aktualisierung von https://downloads.wordpress.org/release/de_DE/wordpress-4.9.7.zip …
Entpacken der aktualisierten Version …
Success: WordPress updated successfully.
@schlessera
Copy link
Member

@runningman84 I ran some tests with the --locale flag.

It seems to work if you use both a specific version ( --version=4.9.7 ) and add the --force flag.

This seems to be a bug in the parameter parsing logic, that should either be smarter about how to trigger the update, or give a warning that the --force flag or a specific version is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants