The entry point for my site is www……/PGV where PGV is currently a file link to <webroot>/PGV4.2.3. This is a 4.2.3 installation without a modules.php. There are no optional modules like the googlemaps one because I haven't had time to learn about them.
I now also have a 'PGV424full' directory with a full 4.2.4 installation in it, including all the bits I need to learn about. It works if I browse specifically to it, accessing the same database tables that my users use through the 4.2.3 installation.
It occurs to me that I could add a 'PGV424' directory (no 'full' in the name) with a 4.2.4 installation without optional modules. I could flip the /PGV file link to that installation so that my users would then be on 4.2.4. Meanwhile I can specifically work through 'PGV424full' with the full installation, and play and learn about the modules. Both would use the same database entries.
Is this workable, or a path to disaster?
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can just change the directory name where the "full" installation was done, and then delete all of the unused modules.
If you're using media, you might find these modules useful: GEDFact_assistant, JWplayer, lightbox, slideshow
You need to ensure that the server URL in the "config.php" file is empty.
Since there weren't any database changes between 4.2.3 and 4.2.4, you should be OK, but you'll need to ensure that the "synchronize GEDCOM" options in both installations are set to "no". The other thing you might consider is to have both installations share the "index" directory by relocating it outside the web-addressable file space on the server and having both the 4.2.3 and 4.2.4 sites point to that same location.
You probably can also use the media firewall as long as the protected media directory is the same in both installations. The media firewall uses .htaccess files in each installation's "media" directory to redirect calls to missing media files to their protected locations.
To set this up, you'll need to move all of the media files (use the Manage Media page) from their normal locations in one installation to the protected directory. In the other installation, you'll need to move these media files from the protected location to the normal nprotected location and then back again. PGV builds the .htaccess files when you move media to the protected directory, and these .htaccess files contain pointers to the PGV installation path.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Both installations would be 4.2.4, but one (for users) would have no optional modules, the other (for me) would have the optional modules installed with some enabled. I would set up optional modules via 'my' route. When they worked I would copy the modules across and enable them in the standard copy. That way my users don't get confused with half working stuff.
I have a very few images without using the media firewall. That's one thing that confused by users while I was setting it up wrongly and then more correctly. I would start again with media firewall via my installation and copy it across when I got it working.
I am using the same index directory above webroot for both (current 4.2.3 and 4.2.4) installations and have the GEDCOM unsynchronised.
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The entry point for my site is www……/PGV where PGV is currently a file link to <webroot>/PGV4.2.3. This is a 4.2.3 installation without a modules.php. There are no optional modules like the googlemaps one because I haven't had time to learn about them.
I now also have a 'PGV424full' directory with a full 4.2.4 installation in it, including all the bits I need to learn about. It works if I browse specifically to it, accessing the same database tables that my users use through the 4.2.3 installation.
It occurs to me that I could add a 'PGV424' directory (no 'full' in the name) with a 4.2.4 installation without optional modules. I could flip the /PGV file link to that installation so that my users would then be on 4.2.4. Meanwhile I can specifically work through 'PGV424full' with the full installation, and play and learn about the modules. Both would use the same database entries.
Is this workable, or a path to disaster?
David
You can just change the directory name where the "full" installation was done, and then delete all of the unused modules.
If you're using media, you might find these modules useful: GEDFact_assistant, JWplayer, lightbox, slideshow
You need to ensure that the server URL in the "config.php" file is empty.
Since there weren't any database changes between 4.2.3 and 4.2.4, you should be OK, but you'll need to ensure that the "synchronize GEDCOM" options in both installations are set to "no". The other thing you might consider is to have both installations share the "index" directory by relocating it outside the web-addressable file space on the server and having both the 4.2.3 and 4.2.4 sites point to that same location.
You probably can also use the media firewall as long as the protected media directory is the same in both installations. The media firewall uses .htaccess files in each installation's "media" directory to redirect calls to missing media files to their protected locations.
To set this up, you'll need to move all of the media files (use the Manage Media page) from their normal locations in one installation to the protected directory. In the other installation, you'll need to move these media files from the protected location to the normal nprotected location and then back again. PGV builds the .htaccess files when you move media to the protected directory, and these .htaccess files contain pointers to the PGV installation path.
Thanks Gerry
Both installations would be 4.2.4, but one (for users) would have no optional modules, the other (for me) would have the optional modules installed with some enabled. I would set up optional modules via 'my' route. When they worked I would copy the modules across and enable them in the standard copy. That way my users don't get confused with half working stuff.
I have a very few images without using the media firewall. That's one thing that confused by users while I was setting it up wrongly and then more correctly. I would start again with media firewall via my installation and copy it across when I got it working.
I am using the same index directory above webroot for both (current 4.2.3 and 4.2.4) installations and have the GEDCOM unsynchronised.
David