IntegraMOD

With the (hopefully) new release seemingly just around the corner, I do have one suggestion that would probably put a little more work on people's shoulders but also be more beneficial to the masses.

I propose that when we have "upgrades" such as the various upgrades for 1.4.0 to phpbb 2.0.17, to phpbb 2.0.18, to phpbb 2.0.19, etc, that since we have the upgrade path already built for each of them, instead of every new user of the software to automatically need to upgrade right after they download integramod, just release a new version of the software with that upgrade previously installed. I feel like we've done this in the past but i'm not sure.

The situation at hand is that if you download 1.4.0 for a new installation, as I did last night because I'm starting another website, you're downloading a version of integramod that is ridden with security problems until you upgrade your forums all the way from phpbb 2.0.17 up to 2.0.21 and install the phpbb security update as well. Now this is not hard stuff...takes roughly about 15 minutes, but the average joe who has never used this website would have no clue that they need to seek out all these upgrades before they can safely use their forums.

Is this something that is in the plans for the future? I feel like once we get 1.4.1 out, we can get THIS version of integramod up to where it belongs in the pre-modded phpbb world, and that is at the top. But I think that's one thing that has to happen eventually or else a security bug could give this software a bad name really fast if a lot of new people start using IM.

Just a tip. File it in your filing cabinets for the future <img> I'd be happy to be in charge of this if need-be.

Zac

A great idea, all new updates and patches should be added to the current version as soon as they become available, so that people are downloading and installing the latest releases, this will hopefully stop the regulaer questions on upgrading and security issues.

Didn't we do this at some point before?

I believe I remember 1.3.2 having like a 1.3.2a 1.3.2b, etc but I can't remember what that was for.

Zac

During im140's time on the old site, this was done for some time. Releases were called revisions or revs. I think that keeping the download updated to the latest patch is a necessity that I'm sure will be done in the future. As long as the SVN server is up and 141 is on there, this can be done quite easily.

we discussed this in great detail for 140 and decided not to update the basic install due to the flood of vauge support requests where the user had no idea what version he had downloaded.

That's a good point. We can always increase the version number for each patch, as I think they'll become fewer and farther between from now on?

Awesome.

Yeah and for the new versions you can go on a letters basis or numbers basis... whichever you guys think is necessary. Just have it show up in the admin panel so if somebody doesn't know what they have you can just tell them to get in their admin panel and scroll to the bottom.

I figured this was probably already in the plans anyways. It just hit me last night because I set up a buddy of mine on IM 1.4.0 a few weeks ago and I remembered I had to go through and patch it all the way up so that it was current and then about 2 days ago I started another site of my own and realized I need to patch it as well but I haven't done that yet. Still working on the template.

Zac

all the file edits are done up to 2.0.21 in the phpbb to IM140 upgrade. The file structure of that zip is such that you can safely overwrite your current directory without overwriting your config.php file then just run the security mod sql and update to latest.php