User Tools

Site Tools


update:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
update:start [2013/06/17 19:57]
jonyo [Version Release Numbers]
update:start [2021/10/27 18:16] (current)
jonyo [Full Update Instructions]
Line 3: Line 3:
  
 There are 2 versions of the update instructions, the [[#Quick Update Instructions]] or the [[#Full Update Instructions]].  If this is the first time updating the software, or if you are updating from a version before **7.0.0**, or if you just like having all the instructions right in front of you with nothing left out, see the [[#Full Update Instructions]]. There are 2 versions of the update instructions, the [[#Quick Update Instructions]] or the [[#Full Update Instructions]].  If this is the first time updating the software, or if you are updating from a version before **7.0.0**, or if you just like having all the instructions right in front of you with nothing left out, see the [[#Full Update Instructions]].
- 
-The [[http://geodesicsolutions.com/support/installation-migration-services/80-professional-installation-service.html|Professional Installation or Update Service]] is also available, if you'd like to have our techs perform a single update for you. 
  
 ===== Full Update Instructions ===== ===== Full Update Instructions =====
Line 12: Line 10:
 We highly recommend using these instructions as they are much more thorough and include every step you might need.  As long as you follow every single step in the instructions, you should have a smooth update. We highly recommend using these instructions as they are much more thorough and include every step you might need.  As long as you follow every single step in the instructions, you should have a smooth update.
  
-**[[http://geodesicsolutions.com/support/updates/|Full Update Instructions]]**+**[[https://geodesicsolutions.org/update-instructions/|Full Update Instructions]]**
  
 <html> <html>
Line 30: Line 28:
   - Download the latest update package from the [[https://geodesicsolutions.com/geo_store/customers/|client area]]. <   - Download the latest update package from the [[https://geodesicsolutions.com/geo_store/customers/|client area]]. <
   - If your preferred downloaded package was:   - If your preferred downloaded package was:
-    * **Wizard**: If you choose the "wizard" package, double-click on the downloaded executable file, and follow through the steps.  Problems with executable [[installation/wizard/troubleshoot/start|see here]].  If the wizard does not automatically start up the "web based" portion of the update script, follow step IV in the zip instructions below. <+    * **Wizard**: If you choose the "wizard" package, double-click on the downloaded executable file, and follow through the steps.  Problems with executable [[installation/wizard/troubleshoot/start|see here]].  If the wizard does not automatically start up the "web based" portion of the update script, follow step III in the zip instructions below. <
     * **Zipped**:      * **Zipped**: 
       - Un-zip the file to your PC.       - Un-zip the file to your PC.
       - Upload the files to your site.       - Upload the files to your site.
-      - Upload the following 3 files in BINARY MODE:  //classes/php5_classes/products.zend.php// , //classes/php5_classes/DataAccess.class.zend.php// , and //upgrade/updateFactory.zend.php//. 
       - Run the update script on your site at **upgrade/index.php**.       - Run the update script on your site at **upgrade/index.php**.
 < <
 < <
-  - If you have purchased any addons, download the latest version of the addon from the client area and upload them to your addons directory.  See the applicable installation instructions for each addon for more info on how to do that. < 
   - Restore any custom files if they were over-written.  These are the custom files you "put aside" in step 3.<tip c w>**Warning:** Do NOT attempt to do this with a PHP file, where you keep using the same old PHP file in newer versions.  Instead if you have made PHP modifications, re-apply your modifications to the new PHP file in the new version.</tip> <   - Restore any custom files if they were over-written.  These are the custom files you "put aside" in step 3.<tip c w>**Warning:** Do NOT attempt to do this with a PHP file, where you keep using the same old PHP file in newer versions.  Instead if you have made PHP modifications, re-apply your modifications to the new PHP file in the new version.</tip> <
   - Go to [[admin_menu/Addons/Manage Addons/start|Addons > Manage Addons]] and update any addons that need updating.  When updating, be sure to read any messages given in case special instructions for updating are needed. <   - Go to [[admin_menu/Addons/Manage Addons/start|Addons > Manage Addons]] and update any addons that need updating.  When updating, be sure to read any messages given in case special instructions for updating are needed. <
Line 48: Line 44:
 <tip c n>**Note:**  If you have //custom// **system**, **module**, or **addon** templates((This is not typical, which is why it is not part of the quick update instructions, or even the full update instructions.  If you have customized system, module, or addon templates, you should know already, this is just a reminder.)), don't forget to check to see if adjustments are required for your update!  See [[tutorials/design_adv/replace_system_templates#Geo Updates & Customized Templates]] for instructions and tips to help you do this.</tip> <tip c n>**Note:**  If you have //custom// **system**, **module**, or **addon** templates((This is not typical, which is why it is not part of the quick update instructions, or even the full update instructions.  If you have customized system, module, or addon templates, you should know already, this is just a reminder.)), don't forget to check to see if adjustments are required for your update!  See [[tutorials/design_adv/replace_system_templates#Geo Updates & Customized Templates]] for instructions and tips to help you do this.</tip>
  
-===== What is "Over Written" in an Update? =====+===== What is "Overwritten" in an Update? =====
  
 Are you worried you will have to re-apply your settings?  Or wondering if your site design will be reset when you update?  Below we answer some of the most asked questions about what an update will affect. Are you worried you will have to re-apply your settings?  Or wondering if your site design will be reset when you update?  Below we answer some of the most asked questions about what an update will affect.
Line 83: Line 79:
 Here at Geodesic Solutions, we have gone through different policies as far as how to name a release. Beginning back with 3.0.0, we started a standardized method for the version numbers, to make it easy to know the nature of a new version just by looking at the release number. Below are the latest release naming policies.  Note that these may change over time, so a "beta" release may have meant something different for a release in the past than what is defined below. Here at Geodesic Solutions, we have gone through different policies as far as how to name a release. Beginning back with 3.0.0, we started a standardized method for the version numbers, to make it easy to know the nature of a new version just by looking at the release number. Below are the latest release naming policies.  Note that these may change over time, so a "beta" release may have meant something different for a release in the past than what is defined below.
  
-==== The Number ====+==== The Number (Updated Feb 2016) ====
  
-Each normal version will have 3 numbers in it, separated by dots, for instance **5.6.7**. For the sake of illustration, below I am going to use a made-up version, **5.6.7**. Below is what each part of the number signifies:+Each normal version will have 3 numbers in it, separated by dots.
  
-**5.6.7: what the numbers mean:**+The first two numbers in a GeoCore version now represent the YEAR and MONTH of that particular version's releaseThe third number will begin at zero and increment for any secondary releases (usually maintenance-level fixes) within a given month.
  
-  * **5** (first number)- Major feature release - If this number changesit signifies major changes in the software. Upgrading to a new major release is only recommended if you want one of the features listed in the new version. If you have highly "customized" code, keep in mind it will be a lot of work to re-do all of the changes on the new version. Upgrading may require additional steps that the upgrade script is not able to do automatically for one reason or another. It is especially important that you have backed up your existing database and files before you start((Although this is something you "should be" doing for every update!)). For example, for version 6.0.0 the change to use 6 was mainly because the 3rd party library Smarty was updated to a new version, that could potentially break a lot of custom designsand for some it would require adjustments to templates to continue to work correctly+For example, the first GeoCore release of February 2016 would be version 16.02.0. If another release is needed during February, it would be numbered 16.02.1. A release the following April would be 16.04.0.
-  * **6** (second number) - Minor feature release - Think of this as a "stair-step feature release" If this number changes, it means the release will have new features. To decide if you want to upgrade, read the changelog for the new version. If any of the new features sound like something you want to use, then get the upgrade. Most likely updates will be very easy, and usually not require many extra steps beyond the normal update instructions+
-  * **7** (third number) - Maintenance Release - If this number changes, it means the release will have "**bug fixes**" and/or changes to make the software work under new circumstances (as an example, a while back Authorize.net changed something so that transactions failed, so we released a new maintenance release to accommodate the changes). Upgrading the software for a maintenance release is always recommended if it fixes anything that affects your installation. To find if you should update, read the changelog for the release, and if any of the changes fix something that applies to your installation, then do the update. These updates will usually be the easiest, but as always, make sure to back up your current files and database and follow the rest of the normal update uproceedures.+
  
 ==== Special Releases ==== ==== Special Releases ====
Line 111: Line 105:
 **beta1** - Signifies **Beta Release** 1 - This is a beta release, for testing or feedback purposes, usually to test or get feedback on a specific feature or set of features. This is the most "common" type of special release. **beta1** - Signifies **Beta Release** 1 - This is a beta release, for testing or feedback purposes, usually to test or get feedback on a specific feature or set of features. This is the most "common" type of special release.
  
-Beta releases are **not for everyone**.  It is provided for anyone that has the time and desire to try out new features we are working on and give feedback.  They are not suitable for everyone, if you do not have the time or desire to do the extra work required to try out a beta version, we recommend to not use it.  We are not forcing anyone to use beta versions, they are simply provided as service to clients that do have the extra time and want to see the latest and greatest.+Beta releases are **not for everyone**.  It is provided for anyone that has the time and desire to try out new features we are working on and give feedback.  They are not suitable for everyone, if you do not have the time or desire to do the extra work required to try out a beta version, we recommend to not use it.  The point is that these are here as an added service for those that wish to use it, no one is forced to use a beta version :-)
  
 A beta release **may not be as stable** as the normal releases. We do not recommend it to be used on a live site, at least not until you have tested it for yourself on a test location. The Geocore license is able to be installed on 2 locations, one for your live site and one for testing purposes so that you can create a test installation to try things out if you wish. If you do not have a test installation yet, you can find instructions for creating one using the [[tutorials:server:migration:start|]] guide. A beta release **may not be as stable** as the normal releases. We do not recommend it to be used on a live site, at least not until you have tested it for yourself on a test location. The Geocore license is able to be installed on 2 locations, one for your live site and one for testing purposes so that you can create a test installation to try things out if you wish. If you do not have a test installation yet, you can find instructions for creating one using the [[tutorials:server:migration:start|]] guide.
Line 117: Line 111:
 These are available to anyone with GeoCore Classifieds, GeoCore Auctions, or GeoCore MAX, and have a current download access.  If you aren't sure, just try to download the beta version, if it allows you to download then you have current access. These are available to anyone with GeoCore Classifieds, GeoCore Auctions, or GeoCore MAX, and have a current download access.  If you aren't sure, just try to download the beta version, if it allows you to download then you have current access.
  
-It is sometimes released weeks or even months before the final release, it shouand may or may not already contain all of the features we plan to add for the final release.  New features are subject to change between a beta release and a final release.  If the "minor feature release" can be thought of as a stair-step release to allow us to rapidly push out new features, beta releases can be thought of a further extension of that:  releases "in between" feature releases where sometimes only one or 2 new features are added, just so you can try out those one or 2 new features.  We do not do all of the normal internal testing for beta releases.  We also do not do the normal changelog.  Depending on the release, we may make a post about it in the forums.  For beta releases, on the admin home page, it will list the latest "beta release" available, that way you will know when there is a new beta release.  Normal (non-beta) releases will only show the latest "normal" release.  There are a few different reasons we may build a beta release: +In the admin on the home page, where it lists the latest version available, beta releases will have their own checks and will show if there is a new beta version.  When using a "normal" release, the latest version displayed will always be the latest "normal" release (non-beta release).
-    * Allow client(s) to try out "sponsored" feature as soon as it is readywithout having to wait for the rest of the features to be finished that are planned for the "final" release. < +
-    * Same, but for a "popular" feature that a lot of clients are looking forward to. < +
-    * If we feel a feature is "highly likely" to introduce new bugs due to complexity or whatever that we feel we may not be able to catch everything, we'll release a beta version and sometimes give instructions on specifically what new feature to try out+
-+
 ===== Troubleshooting ===== ===== Troubleshooting =====
  
update/start.1371499067.txt.gz · Last modified: 2014/09/25 16:55 (external edit)