I haven't testet this utility yet but I want to write my ideas about such an untility:
There are 3 important points for me while upgrading from an older version to a newer.
1.) The data inside the authenticate.php has to be completely copied from the older version. For this phpgedview should be compatible to older versions. That means if there are new user-vars inside a new version these should be written while editing the user or while logging in to phpgedview.
The internal routines of phpgedview should check (with isset()) if the new variables exist in the old authenticate.php and if not, they need to be added.
2.) The used privacy-files (as you know there may be more than one) have also to be copied into the new version.
3.) The data inside /index needs also to be copied without losing any data inside pgv_changes.php and all xxx_conf.php
1,2,3 are important because a new version of phpgedview brings this php-files as empty or predifined ones. Just copying over an old version would destroy the old files.
Point 1 also needs to be implemented by John.
bye, Kurt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-11-22
Hey Kurt,
Thank you for your input. Let me go by your points.
1. The file authenticate.php here is totally empty. Almost ;) There is only 1 line in it. Or are you talking about the config.php file? That is not yet implemented to do a comparison between the new and old. That will be the next release. If you mean something else, please let me know.
2. The privacy files are now overwritten when the copying is done. Should this be different? I just saw there is a new configuration screen for the privacy files. I just need to find out to which file it writes the new settings to. I am not so familiar with the privacy settings yet.
3. The data in the /index folder is not being copied. Let me explain how it works. The way it works now is that the new files are copied to the old location. In other words. Your current setup is upgraded. This means, if you have a new version of phpgedview and copy the index folder, the only file overwritten will be the readme.txt file.
Yes, I agree with you, just copying over would destroy a setup but if it would be that simple, anybody can do it ;)
Same as the config.php file is not being copied unless specified. When it does copy, it means, it will be overwritten with an empty one.
Regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Let me just answer to point 1 of your message. Later I will read the other points and will answer them :-)
I know that the authenticate.php is almost empty in new vers of phpgedview ;-)
What I meant was:
If phpgedview works for some days there are some new entries inside the actual authenticate.php because I added new entries or users registered themselves.
If a new version of phpgedview comes and an upgrade utility is used this utility should not just overwrite the old authenticate.php with its contents.
It should drop the "new" and "empty" authenticate.php and should use the old authenticate.php.
Hope you could understand what I meant :-)
As I wrote in my first message, I didn't try the utility yet, so I don't know if this point is off-topic, because you have already implementet it.
bye, Kurt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In regards to the authenticate.php file. Between versions the old file can just be kept. All new user fields will be added the next time the user data is updated. If the fields don't exist for a user they will take on the default value.
In the MySQL version the authentication.php file will detect if there is an outdated database an automatically run the SQL commands to update the user table.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That is correct. You do not need to copy the authenticate.php file when upgrading to a new version.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-11-26
Thanks. I have removed the authenticate.php file from the copy sequence. It will never be copied now.
Regards,
Roland.
P.s. thanks for the pointer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-11-29
John,
I have the script ready that compares the old and new config file and add the new variables to the old config file (this is the original file ppl are working with).
What I would like to know is, at which position should they be inserted? My guess is before the line that says start gedcom configuration.
Regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It doesn't really matter where the new config vars are located in the file, but for consistency it would be better if they were all located together before the //-- start gedcom configuration comment
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-11-29
Yes, that is what I counted on and implemented it that way. You can see it for yourself in the 0.4 version. ;)
I am actually surprised I was able to finish it all in 1 day ;)
Up to the next step ;)
Regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all,
A new version of the upgrade utility is available in the patches section:
http://sourceforge.net/tracker/index.php?func=detail&aid=828788&group_id=55456&atid=477081
Read all about it in the patch posting.
Have fun,
Roland
Hi Roland,
I haven't testet this utility yet but I want to write my ideas about such an untility:
There are 3 important points for me while upgrading from an older version to a newer.
1.) The data inside the authenticate.php has to be completely copied from the older version. For this phpgedview should be compatible to older versions. That means if there are new user-vars inside a new version these should be written while editing the user or while logging in to phpgedview.
The internal routines of phpgedview should check (with isset()) if the new variables exist in the old authenticate.php and if not, they need to be added.
2.) The used privacy-files (as you know there may be more than one) have also to be copied into the new version.
3.) The data inside /index needs also to be copied without losing any data inside pgv_changes.php and all xxx_conf.php
1,2,3 are important because a new version of phpgedview brings this php-files as empty or predifined ones. Just copying over an old version would destroy the old files.
Point 1 also needs to be implemented by John.
bye, Kurt
Hey Kurt,
Thank you for your input. Let me go by your points.
1. The file authenticate.php here is totally empty. Almost ;) There is only 1 line in it. Or are you talking about the config.php file? That is not yet implemented to do a comparison between the new and old. That will be the next release. If you mean something else, please let me know.
2. The privacy files are now overwritten when the copying is done. Should this be different? I just saw there is a new configuration screen for the privacy files. I just need to find out to which file it writes the new settings to. I am not so familiar with the privacy settings yet.
3. The data in the /index folder is not being copied. Let me explain how it works. The way it works now is that the new files are copied to the old location. In other words. Your current setup is upgraded. This means, if you have a new version of phpgedview and copy the index folder, the only file overwritten will be the readme.txt file.
Yes, I agree with you, just copying over would destroy a setup but if it would be that simple, anybody can do it ;)
Same as the config.php file is not being copied unless specified. When it does copy, it means, it will be overwritten with an empty one.
Regards,
Roland
Hi Roland.
Let me just answer to point 1 of your message. Later I will read the other points and will answer them :-)
I know that the authenticate.php is almost empty in new vers of phpgedview ;-)
What I meant was:
If phpgedview works for some days there are some new entries inside the actual authenticate.php because I added new entries or users registered themselves.
If a new version of phpgedview comes and an upgrade utility is used this utility should not just overwrite the old authenticate.php with its contents.
It should drop the "new" and "empty" authenticate.php and should use the old authenticate.php.
Hope you could understand what I meant :-)
As I wrote in my first message, I didn't try the utility yet, so I don't know if this point is off-topic, because you have already implementet it.
bye, Kurt
Hi Kurt,
In regards to the authenticate.php file. Between versions the old file can just be kept. All new user fields will be added the next time the user data is updated. If the fields don't exist for a user they will take on the default value.
In the MySQL version the authentication.php file will detect if there is an outdated database an automatically run the SQL commands to update the user table.
--John
Thanks John.
This was what I wanted to hear :-)
John,
That means, the authenticate.php never needs to be copied?
Regards,
Roland
Roland,
That is correct. You do not need to copy the authenticate.php file when upgrading to a new version.
--John
Thanks. I have removed the authenticate.php file from the copy sequence. It will never be copied now.
Regards,
Roland.
P.s. thanks for the pointer.
John,
I have the script ready that compares the old and new config file and add the new variables to the old config file (this is the original file ppl are working with).
What I would like to know is, at which position should they be inserted? My guess is before the line that says start gedcom configuration.
Regards,
Roland
Roland,
It doesn't really matter where the new config vars are located in the file, but for consistency it would be better if they were all located together before the //-- start gedcom configuration comment
--John
Yes, that is what I counted on and implemented it that way. You can see it for yourself in the 0.4 version. ;)
I am actually surprised I was able to finish it all in 1 day ;)
Up to the next step ;)
Regards,
Roland