How about having the best of both worlds? Instead of just pulling the version number from the server, also pull a "disaster" flag. If the disaster flag is not set, the user just gets a warning about the new version, but doesn't have to update. If the disaster flag is set, only then do you disable the old version.Phil wrote:The Support Toolkit contains a wide variety of tools that are more than capable of damaging or destroying your forum in the event of a bug; consequentially, we've opted to disable older released when updates are released so that any severe bugs are no longer allowed to propagate after they are fixed. Fortunately, we have yet to experience and incident where this would have otherwise been an issue, however, we prefer to err on the side of caution.
Than the disaster flag would be set for most updates, especially those made after an phpBB update as an phpBB update breaks certain parts of the STK as they relay on information that isn't available until an update is released.Pony99CA wrote:How about having the best of both worlds? Instead of just pulling the version number from the server, also pull a "disaster" flag. If the disaster flag is not set, the user just gets a warning about the new version, but doesn't have to update. If the disaster flag is set, only then do you disable the old version.Phil wrote:The Support Toolkit contains a wide variety of tools that are more than capable of damaging or destroying your forum in the event of a bug; consequentially, we've opted to disable older released when updates are released so that any severe bugs are no longer allowed to propagate after they are fixed. Fortunately, we have yet to experience and incident where this would have otherwise been an issue, however, we prefer to err on the side of caution.
That's user-friendly and protection when you need it.
Interesting idea, though I'm not sure how easily something like that could be implemented.Pony99CA wrote:That's user-friendly and protection when you need it. (You could be even more friendly by having a disaster flag for each tool, and only disabling the tools that had the severe bugs.)
The STK requires an administrative login to use, so it's only as safe as you make it. It does allow you to generate a temporary password, but that requires file access to upload and enable it. At that point, your site has already been compromised.Popp Singh wrote:What about the safety aspects ? How many other things can you turn of on our sites ? Doesnt it open a back door for hackers to try to use and get even more acsess to our sites ?
Which is the same way that phpBB checks whether your install is up to date. The only difference is what the code tells the script to do when it is found to be outdated.Zulcun wrote:I would hardly call it a "Back Door" into your server! All it does is use a simple PHP function to grab a text file from the phpBB servers, which only contains the latest version number, if the version numbers match then nothing happens, if they don't then it shuts down.
It is a one way thing, phpBB cannot access your server in any way so there is no reason to worry.