Fork me on GitHub
Subscribe 4

Ticket #878 (open enhancement)

Improve update check

  • Created: 2013-08-08 16:36:29
  • Reported by: Studio384
  • Assigned to: None
  • Milestone: None
  • Component: upgrading
  • Priority: normal

The update check in FluxBB should display an actual warning when an update for FluxBB is available. This can be done in combination with GitHub, this way, the script can check for updates every time the page reloads, without the need to cache it (as long as it is a negative).

$latest_version = trim(@file_get_contents(''));
if (version_compare(FORUM_VERSION, $latest_version, '<=')) { echo
	"There is an update available for FluxBB.";

This way, people stay better up-to-date wich is verry important in cases like we had with 1.5.3.


Franz 2013-08-08 20:52:49

Why would this not need to be cached? I dislike relying on a third party like that (even if it's GitHub).

Studio384 2013-08-08 20:58:14

  • Description changed. (Diff)

I actualy mean that this shouldn't be cached as long as the result is negative. Added that to the text.

Franz 2013-08-08 21:07:15

That's still what I mean. I don't want the server to send a HTTP request every time I visit an admin page.

GitHub is down often enough for this to be annoying.

adaur 2013-08-09 19:48:51

What about a compromise? A cache file that renewed every week does not seem like something that would overload a server.

Franz 2013-08-09 20:45:55

Exactly. smile

XAOS-Eric 2014-02-12 04:17:30

How about we do something like this? … check.json

and if the new version is more than the old version, the update is downloaded, and installed?

Franz 2014-02-12 19:41:27

That's basically how we do it now: However, this has to be done manually by clicking a link. What we want for 2.0 is an automatic notification in the admin panel that shows the admin that a new version is available. Automatic upgrades are a little bit much for now.

Studio384 2014-02-12 20:02:45

I would say that it should be possible to install from the dashboard (of course), but no automatic updates, we could consider it for patch releases (I hope that we will move on to FluxBB 2.1, 2.2 and so on, a little bit faster than today, more like a WordPress release schedule (of course, we'll have less new stuff, but a faster release cycle won't be a problem)), but not for feature releases. Also, I've a little cache system that checks for updates for FluxBB 1.5 every day until there is a new release, and a notification shows on the admin index. Might post a modification for FluxBB later on. smile Also, maybe something to port into core in the 1.x branches?