Idea - An easier way to update Core

[burt]

ps, if everyone agrees I might split this updater out into its own thread.

[tessthepup]

@burt I am quite happy to give it a go although as said I cannot devote 100% of my time to it, nothing ventured nothing gained lol

If you're happy to take ownership of that, that would be appreciated by the community I think, @tessthepup.

I've not ever looked at that add-on before. As a rule, I avoid examining third-party work unless the original author explicitly requests input. It avoids any future ambiguity if I happen to develop something in a similar space.

--

On each release, I publish a .zip package in the update thread, here are a list of them all:

app.php/tag/phoenix-update

You should be able to download the relevant archive and generate the required "update" file from one of the contained files within each UPDATE_from_x_y.zip. Then use the fileset contained within as the source update files.

Untested and untried, but hope to, at least, give you a pointer. You might try it on the next available from 1095, found here: viewtopic.php?f=10&t=2573

[burt]

@burt I am quite happy to give it a go although as said I cannot devote 100% of my time to it, nothing ventured nothing gained lol

Thank you, I really appreciate that. Please don’t feel any pressure to give more time than you comfortably can - even 5 minutes here and there is genuinely helpful. Small, consistent contributions make more difference than people realize.

It's not about anyone carrying a huge load. It's just about a few people being willing to get involved where and when they can. That's how things gradually build momentum.

And for anyone else quietly following along - this is a good example of how to help: no big declarations, just a simple `I'll give it a go.`

Thanks again, @tessthepup . It's very much appreciated by me and I hope by the rest of the community.

[burt]

Please note that this discussion originated in the `One Thing` thread:

viewtopic.php?f=43&t=3185

As it's likely to develop into a more in-depth exchange, I've moved it into its own dedicated topic to keep things organised and hopefully easier to follow.

I’ll tag a few members who've previously shown interest in `easy update` approaches, with the aim of inviting them to contribute to the discussion - particularly around ideas, prototyping, and testing.

[Dan Cole]

@burt I am quite happy to give it a go although as said I cannot devote 100% of my time to it, nothing ventured nothing gained lol

@tessthepup I'm not a code monkey...I know just enough to be dangerous but if I can help in anyway please let me know.

Dan

[Dan Cole]

@BrockleyJohn Before @tessthepup gets too far along with this I'm wondering if you are planning to update the CE Phoenix Upgrader Utility or perhaps even working on it now?

Dan

[BrockleyJohn]

Actually yes, I have been working on it... updated to use the json that came with previous releases rather than having things hardcoded (though I don't think there was one with 1.1.0.6)

I got a bit sidetracked with a diff viewer so you can see if picked up changes actually matter.

It would be nice for it to pull the info needed to the store instead of having to download a new version of the addon.

[frankl]

I always think it's a pain to upload an addon, then go to all the different screens to enable modules etc.

Also (sometimes) trying to work out which module goes with which addon.

I haven't thought through how this would work, but what about a Settings page for each addon? You could turn on or off modules and hooks, enter required settings, etc etc.

[Kofod95]

[...] Settings page for each addon? You could turn on or off modules and hooks, enter required settings, etc etc.

It would, of course, depend on add-on creators to use such a system, but I'm for it!
Maybe under Tools in Admin have a new page for add-ons, where each add-on populates an infoBox with settings (or just links to the settings and modules)? If all add-on files checked for a configuration-constant specific for that add-on and returned nothing if not true, an on/off switch could control all of the add-on.
Not sure how it would work with override though.

//Daniel

[Omar_one]

I always think it's a pain to upload an addon, then go to all the different screens to enable modules etc.

Also (sometimes) trying to work out which module goes with which addon.

I haven't thought through how this would work, but what about a Settings page for each addon? You could turn on or off modules and hooks, enter required settings, etc etc.

-app.php/addons/paid_addon/modules_control_pro/ @raiwa

on the old days there was module for something like this
- modules_content replacement for Phoenix @K.Reima