ClassicPress / ClassicPress-Network

Old code repository for *.classicpress.net - Do not use!
5 stars 4 forks source link

GitHub download links need updating #50

Closed nylen closed 5 years ago

nylen commented 5 years ago

Links from https://www-new.classicpress.net/get-classicpress/, probably also appear in other places on the site.


The link to download the migration plugin is currently:

https://api.github.com/repos/ClassicPress/ClassicPress-Migration-Plugin/zipball/1.0.1

but it should be this instead:

https://github.com/ClassicPress/ClassicPress-Migration-Plugin/releases/download/1.0.1/switch-to-classicpress.zip

See https://github.com/ClassicPress/ClassicPress-Migration-Plugin/releases for details. The existing code that gets a list of GitHub releases is probably not flexible enough to handle this situation yet.


The link to download the latest ClassicPress release is currently:

https://api.github.com/repos/ClassicPress/ClassicPress/zipball/1.0.1+dev

but it should be this instead:

https://github.com/ClassicPress/ClassicPress-release/archive/1.0.1.zip

(note different URL format, and also ClassicPress-release instead of ClassicPress repository).

EvoRay commented 5 years ago

I don't understand. I thought Omukiguy's Latest Github Release plugin tracked the latest version in a repo. Did the repo change?

nylen commented 5 years ago

No, it just doesn't do all it needs to do yet. Also, ClassicPress has two repositories, one for development and one for releases. Using the ClassicPress/ClassicPress-releases repository instead of ClassicPress/ClassicPress will fix part of this issue, and updating the plugin code will fix the rest.

BlueSkyPhoenix commented 5 years ago

Has someone connected w/ Omukiguy to have him update his plugin? Is this all set from that perspective, at least?

nylen commented 5 years ago

@bahiirwa see above, https://github.com/bahiirwa/Latest-Github-Release needs an update to its URL logic before we can use it on the new site. I had originally suggested using the zipball_url from the API response, but that isn't going to work for us. Here is a refinement:

Also, these links shouldn't have target="_blank".

Are you able to take a look at this sometime? Otherwise I will submit a PR over there.

bahiirwa commented 5 years ago

I have pushed changes to this effect on Github

nylen commented 5 years ago

Still needs a couple more fixes, we have been chatting about this via DM

nylen commented 5 years ago

This is fixed on the site, and I've submitted the changes back to the original plugin: https://github.com/bahiirwa/Latest-Github-Release/pull/1