No Updates Found Migrating to Winter on Non-Composer Install

[NixFey]

• Winter CMS Build: October build 471
• PHP Version: 7.4.3
• Database Engine: MySQL
• Plugins Installed: RainLab.Builder 1.0.26, RainLab.GoogleAnalytics 1.3.0, PanaKour.SendGrid 1.0.0

Description:

I'm trying to migrate my October CMS installation to Winter using the updateServer method. I've set the updateServer in the cms.php to https://api.wintercms.com/marketplace, but when I check for updates in the UI or on the CLI with october:update, it says that no updates are available. I'm not sure if this is just an issue with my environment or maybe a bigger issue with the cms.php method of migrating away from October.

Steps To Reproduce:

• Be on October CMS (non-composer install)
• Change updateServer to the Winter CMS one as described in migration instructions
• Have disableCoreUpdates false
• Check for updates on UI or CLI

[LukeTowers]

@evanlihou the update file isn't yet available from the marketplace API, should be available in a week at most.

[NixFey]

Thanks for the update @LukeTowers! If the marketplace API isn't yet distributing the new version, you might want to consider noting that in the blog post.

I'm really excited to see where this project goes, and I'm glad to see the maintainers keeping a FOSS version alive. Keep up the good work!

[LukeTowers]

@evanlihou updated the blog post, thanks!

[zlobec]

@LukeTowers Is there any information about when the marketplace API will be available?

[LukeTowers]

@zlobec @bennothommo is currently working on the API for the core updates, hopefully soon. This month has been extremely busy for me as we just bought our first house so I've been running around like a chicken with its head cut off trying to deal with everything that entails and move.

[zlobec]

No worries ... I'm too in the middle of a move... and yeah... Keep up the good work.

[bennothommo]

We've all hit our roadblocks at the same time - mine is a grizzly newborn, hence why progress has been slow. I'm still slowly chipping away at the core updates - once that's done, the installer should be out shortly afterwards. I can't commit to a timeframe yet though, so I can only say "soon" as @LukeTowers said.

[graphixela]

Congrats on the move and the baby but am I missing something? It still says no updates...

[LukeTowers]

@graphixela nope, not missing anything. Priority for me this week is getting 1.1.4 out and then I can pick up work on the update delivery system through the marketplace again.

[graphixela]

Okay, thanks. It's marked as closed. A bit confusing.

[NixFey]

I closed this issue because my original question was answered, but maybe it should stay open until the API is actually implemented? @LukeTowers / @bennothommo is there another ticket that this is a duplicate of? If not feel free to open this back up and use for updates.

[NixFey]

Have there been any updates on this? It's starting to feel like this feature is never coming and I imagine it's quite important for people trying to migrate away from their October installations

[LukeTowers]

@evanlihou it is still coming, I've just been busy with personal stuff and client projects. All of that should be wrapping up in the next month so I should be able to crank it out in September / October. In the meantime, there's always the composer route for people who need to swap over immediately.

[github-actions]

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[NixFey]

Just commenting to keep this open

[github-actions]

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[fpomidoro]

hello all, is there any news or ETA on this? thanks!

[LukeTowers]

It's actively being worked on @fpomidoro, see #438

[github-actions]

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[fpomidoro]

Just keeping this open! Thanks!

…

On Fri, Apr 8, 2022, 21:24 github-actions[bot] ***@***.***> wrote: This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue. If this issue is critical to your business, consider joining the Premium Support Program <https://wintercms.com/premium-support> where a Service Level Agreement is offered. — Reply to this email directly, view it on GitHub <#120 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHUC62KKM5E7VTKHV7HF7Q3VEDE2BANCNFSM43SXA66A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[github-actions]

This issue will be closed and archived in 3 days, as there has been no activity in this issue for the last 6 months.
If this issue is still relevant or you would like to see it actioned, please respond within 3 days.
If this issue is critical for your business, please reach out to us at [email protected].

[fpomidoro]

Keeping it open. Thanks!

[github-actions]

This issue will be closed and archived in 3 days, as there has been no activity in this issue for the last 6 months.
If this issue is still relevant or you would like to see it actioned, please respond within 3 days.
If this issue is critical for your business, please reach out to us at [email protected].

[fpomidoro]

Comment to keep it open, any updates and/or ETA? Thanks!

[LukeTowers]

Still hard at work on it @fpomidoro, should be ready in the next month or so we're hoping. Working on a refresh of our main website (both design and infrastructure) and a lot of behind the scenes organizational things at the same time.

[github-actions]

This issue will be closed and archived in 3 days, as there has been no activity in this issue for the last 6 months.
If this issue is still relevant or you would like to see it actioned, please respond within 3 days.
If this issue is critical for your business, please reach out to us at [email protected].

[NixFey]

If the devs aren't planning on implementing this feel free to close but just in case I'll keep it open.

I know priorities are constantly pulling in different directions, but I do hope this does get done eventually :)

[bennothommo]

We're definitely working on it. We're all just very, very busy at the moment, so it's not as fast as we'd like. :(

[fpomidoro]

Hi! Just checking if there is any clear roadmap/date on this? Thanks!

[LukeTowers]

We're working on a necessary refactor to the entire plugin management / update management system right now (#1259) after which we'll be able to work on the update delivery system. For now, the best option is still just composer.