The Section "Preparing the distribution files" in the Upgrade WIKI, I think says to Delete the config.php file of the upzipped distribution, and to keep the old file on the server.
Then under "Copy the new distribution files to the server", it says to "Please remember to update /config.php (set permissions first".
I'm confused. How does one update /config.php? Copy the new distribution config.php to the server?
If this is not the right place to ask such a question, where do i ask question?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry Greg, you are loosing me. You must be reading a different WIKI page since i can not find the sentence "In case you are changing the name of the directory".
Ok, i found what you are talking about, but my question still remain… Do i go with the new config.php or the old one. the new config.php is different (updated) from the old one. So it seems that the new one should be used…
Dietmar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You should ignore the "please remember to update …" sentence. If you're replacing an existing installation by deleting all of the files except the ones listed, there should be no need to make any changes to the existing file "/config.php" from that old installation.
However, sometimes new features in PGV require an update to the "/config.php" file if you're not happy with the defaults that have been set. In this case, you need to make sure that the old "/config.php" file is writable before you launch the Install wizard that guides you through the various options in that "/config.php" file.
PGV 4.2.3 should not have a "config.php" file, so you shouldn't even need to delete it from the set of files you downloaded and then unzipped. That sentence is in there in case somebody built the distribution file set incorrectly.
Sometimes, when upgrading from the SVN file set that we developers use, you'll see that "config.php" file. This is an error that has occurred a few times. When it does happen, that "config.php" file should be removed from SVN promptly by one of the developers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I get what your are saying.
In the "CLean up the current files on the server" section, it says to keep your old config.php. I guess this is not needed for 4.2.3.
It's hard to make universal documentation in a changing environment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dietmar - in my previous post I said that I would remove that sentence. I did so immediately - so you won't find it.
Gerry "PGV 4.2.3 should not have a "config.php" file". I'm sorry, but it does. (The build script - build.xml - renames the SVN file build.dist to build.php).
So, Dietmar. Keep your old config.php. Delete the new one that you downloaded. The section "Preparing the distribution files" explains this.
I realise that the upgrade instructions are complicated. The problem is that PGV stores lots of data in lots of places. We are working to simplify this, but the upgrade instructions need to work with every combination of old-version and new-version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dietmar
In my own humble opinion, there is actually no harm in using the new CONFIG.php, but when upgrading, you usually desire to use the exact same setup of files, db names, passwords and file locations as the previous installation. To do so with the 'new' config.php would require you to remember each setting perfectly, as previously recorded. Despite your best efforts, there is always a significant chance you would vary the information in some small way, breaking the installation and raising your blood pressure and frustration. Hence why it is recommended that you use the existing config.php file, rather than a new one.
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Section "Preparing the distribution files" in the Upgrade WIKI, I think says to Delete the config.php file of the upzipped distribution, and to keep the old file on the server.
Then under "Copy the new distribution files to the server", it says to "Please remember to update /config.php (set permissions first".
I'm confused. How does one update /config.php? Copy the new distribution config.php to the server?
If this is not the right place to ask such a question, where do i ask question?
I think it is referring to the previous sentence "In case you are changing the name of the directory".
I can't image why you would combine a relocation with an upgrade. I'll remove this.
Greg
Sorry Greg, you are loosing me. You must be reading a different WIKI page since i can not find the sentence "In case you are changing the name of the directory".
My questions pertain to the section "Preparing the distribution files" on the WIKI page:
http://wiki.phpgedview.net/en/index.php?title=Upgrading.
Dietmar
Ok, i found what you are talking about, but my question still remain… Do i go with the new config.php or the old one. the new config.php is different (updated) from the old one. So it seems that the new one should be used…
Dietmar
You should ignore the "please remember to update …" sentence. If you're replacing an existing installation by deleting all of the files except the ones listed, there should be no need to make any changes to the existing file "/config.php" from that old installation.
However, sometimes new features in PGV require an update to the "/config.php" file if you're not happy with the defaults that have been set. In this case, you need to make sure that the old "/config.php" file is writable before you launch the Install wizard that guides you through the various options in that "/config.php" file.
PGV 4.2.3 should not have a "config.php" file, so you shouldn't even need to delete it from the set of files you downloaded and then unzipped. That sentence is in there in case somebody built the distribution file set incorrectly.
Sometimes, when upgrading from the SVN file set that we developers use, you'll see that "config.php" file. This is an error that has occurred a few times. When it does happen, that "config.php" file should be removed from SVN promptly by one of the developers.
Ok, I get what your are saying.
In the "CLean up the current files on the server" section, it says to keep your old config.php. I guess this is not needed for 4.2.3.
It's hard to make universal documentation in a changing environment.
Dietmar - in my previous post I said that I would remove that sentence. I did so immediately - so you won't find it.
Gerry "PGV 4.2.3 should not have a "config.php" file". I'm sorry, but it does. (The build script - build.xml - renames the SVN file build.dist to build.php).
So, Dietmar. Keep your old config.php. Delete the new one that you downloaded. The section "Preparing the distribution files" explains this.
I realise that the upgrade instructions are complicated. The problem is that PGV stores lots of data in lots of places. We are working to simplify this, but the upgrade instructions need to work with every combination of old-version and new-version.
Got it, so even though the new config.php has changed (updated), I should keep the old one, which will not have the new changes.
Dietmar
In my own humble opinion, there is actually no harm in using the new CONFIG.php, but when upgrading, you usually desire to use the exact same setup of files, db names, passwords and file locations as the previous installation. To do so with the 'new' config.php would require you to remember each setting perfectly, as previously recorded. Despite your best efforts, there is always a significant chance you would vary the information in some small way, breaking the installation and raising your blood pressure and frustration. Hence why it is recommended that you use the existing config.php file, rather than a new one.
-Stephen
Greg:
Thanks for correcting my flase and misleading statement about the distribution of the "config.php" file.
Thanks guys for your responses.
Dietmar