Geodesic Solutions Community Wiki

User Tools

Site Tools

You are here: Auction and Classified Software Support Home » Software Updates
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 [2012/11/14 17:39]
geomatt 		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]].
- 
-There is also [[http://geodesicsolutions.com/support/installation-migration-services/80-professional-installation-service.html|Professional Installation or Update Service]] available. 
  
 ===== 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 79: Line 75:
 For anything not in that list, the general **//rule of thumb//** is this:  If it is a **file**, it will most likely get **over-written** in an update.  If it is something you **change in the admin panel**, it will most likely **not change** in an update. For anything not in that list, the general **//rule of thumb//** is this:  If it is a **file**, it will most likely get **over-written** in an update.  If it is something you **change in the admin panel**, it will most likely **not change** in an update.
  
 +===== Version Release Numbers =====
 +
 +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 (Updated Feb 2016) ====
 +
 +Each normal version will have 3 numbers in it, separated by dots.
 +
 +The first two numbers in a GeoCore version now represent the YEAR and MONTH of that particular version's release. The third number will begin at zero and increment for any secondary releases (usually maintenance-level fixes) within a given month.
 +
 +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.
 +
 +==== Special Releases ====
 +
 +Sometimes you will see a release that looks like 4.2RC1 or 6.5beta1, these are "special" releases. Typically, a special release will only be made for major or minor feature releases, not for maintenance releases (see above).  As such, many times the 3rd number is omitted, so that the "special" part of the version replaces the 3rd number.  For example, **6.5beta1** rather than <del>6.5.0beta1</del>.
 +
 +Across the net, the terms may hold different meanings. Below is what each of them mean for Geodesic Product releases:
 +
 +=== Release Candidates ===
 +
 +**RC1** This signifies **Release Candidate** 1. It means we have done all the internal testing, and are ready to release the software, but are first releasing it to anyone interested in "trying it out". Typically we will only have Release Candidates on major feature releases, but we might sometimes also have them on minor feature releases too. We especially do this if there is some reason that a particular release has a "high chance" of causing problems.  If anyone finds a bug in a release candidate that was not caught in the internal testing, we will fix the bug, do all the internal testing again, and then release a second Release Candidate. Once a release candidate has been out for a long enough time, with no bugs found, we make the final (non-special) release.
 +
 +=== Preview Releases ===
 +
 +**pre1** - Signifies **Preview Release** 1 - We rarely use this one.  This is a release intended **primarily for 3rd party developers**, to give them a preview, or a "head start" on making sure their addons or code modifications are compatible with the next release. The "state" of the software for a preview release will vary, but typically the release will be considered "unstable", since it is being released sometimes weeks or months before the normal release, and should not be used in a live environment.
 +
 +=== Beta Releases ===
 +
 +**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.  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.
 +
 +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.
 +
 +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).
 ===== Troubleshooting ===== ===== Troubleshooting =====
  
update/start.1352914799.txt.gz · Last modified: 2014/09/25 16:55 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki