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

Get core upgrades from calmpress.org and change the logic of available upgrades displayed to the user #58

Closed
markkap opened this issue Sep 17, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@markkap
Copy link

commented Sep 17, 2018

Obviously core upgrades can not be retrieved from wordpress.org as at best this will result in overwriting forked code.

What we will do is do implement a new upgrade information retrieval API which will let us know about all actively maintained versions at calmpress.org, and let the client decide on its preferred upgrade path to display to the user. Initially there is going to be two different upgrade paths, one from production enviroment in which it will suggest upgrade to stable releases, and one from development enviroment in which development releases will be suggested as well as stable ones.
For simplification, development enviroment will be identified by having WP_DEBUG set to true.

@markkap markkap added the upgrade label Sep 17, 2018

@markkap markkap added this to the 0.9.9 milestone Sep 17, 2018

@markkap markkap changed the title Get core upgrades from calmpress.org and change its version selection logic Get core upgrades from calmpress.org and change the logic of available upgrades displayed to the user Sep 17, 2018

markkap added a commit that referenced this issue Sep 18, 2018

sort the possible core updates based on how easy and useful an upgrad…
…e should be from the currently active version #58

markkap added a commit that referenced this issue Sep 18, 2018

markkap added a commit that referenced this issue Sep 22, 2018

we are using different zip structure, one without a wordpress root, t…
…ake this into account in upgrade, and don't report to wordpress.org #58

markkap added a commit that referenced this issue Sep 23, 2018

embed minimum requirements information in the code of update-core its…
…elf. Ugly but better than trying have two required files to drive an install #58
@markkap

This comment has been minimized.

Copy link
Author

commented Sep 23, 2018

This was very complex so probably there will be bugs discovered later, but for now things seem to work

@markkap markkap closed this Sep 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.