Upgrading and Version Numbering

[sparky672]

I was wondering if you could start putting an Ion Auth version number in the file header(s) someplace, similar to how CodeIgniter puts its version number in the core file. As it stands, I'm really having a difficult time figuring out if the various Ion Auth version(s) I'm using across several projects are up to date.

Also, I realize that some of the included files are only for sample/demo and can be modified to suit any individual project. For example, I've typically modified the Ion Auth Controller and View files for each project. Again, when a newer version of Ion Auth is released, updating each project is a daunting task, with line-by-line examination and file difference comparisons.

Am I approaching this wrong? Is it possible to just keep my custom Ion Auth Controller and only upload the other new files?

I'm thinking there has to be a better way to keep Ion Auth up to date without always having to do line-by-line file comparisons.

[benedmunds]

I rarely (if ever) allow backwards compatibility breaks to be introduced so you should be able to simply replace the following files to update:

/models/ion_auth_model.php
/libraries/ion_auth.php

As long as you are on v2. The easiest way to see if you are on v1 or v2 is to check if you have a “meta” table. v1 has “meta”, v2 does not.

I agree though that versioning would at least make ensuring you are up to date easier so will look at adding that. I should probably start tagging releases to go along with that.

-Ben Edmunds
706.289.4115
ben.edmunds@gmail.com

On Friday, April 18, 2014 at 11:51 AM, sparky672 wrote:

I was wondering if you could start putting a, Ion Auth version number in the file header(s) someplace, similar to how CodeIgniter puts its version number in the core file. As it stands, I'm really having a difficult time figuring out if the various Ion Auth version(s) I'm using across several projects are up to date.
Also, I realize that some of the included files are only for sample/demo and can be modified to suit any individual project. For example, I've typically modified the Ion Auth Controller and View files for each project. Again, when a newer version of Ion Auth is released, updating each project is a daunting task, with line-by-line examination and file difference comparisons.
Am I approaching this wrong? Is it possible to just keep my custom Ion Auth Controller and only upload the other new files?
I'm thinking there has to be a better way to keep Ion Auth up to date without always having to do line-by-line file comparisons.

—
Reply to this email directly or view it on GitHub (#577).

[sparky672]

Thank-you. I appreciate both items very much. One last small suggestion, perhaps you can put that information about the two critical files into a "how to upgrade" section of your docs. I only mention it because otherwise I'll be searching for this GitHub thread next time I need to update.

[Venefilyn]

Seeing as I love the work of this library I could add a initial version tagging to everything similarly to what @sparky672 says

[benedmunds]

Thanks for the offer @SpyTec but I just pushed this.

There is now a version number in the top of the library, config, and model files. Plus it is tagged in GH. We're on 2.5.2, I used to tag versions so starting where we left off.

[benedmunds]

Also added an upgrading section to the docs.