Update From Earlier Version Of AShop Deluxe
Previous  Top  Next

Update your existing AShop Deluxe installation from any earlier version to version 3.9.3

AShop Preinstallation Test
Before uploading the new program files, we recommend that you first test the site to make sure that the ionCube encoded script files will run on the server and that all of the requirements are met. Download the AShop Pre-install Test from the program download page. Instructions are included with it in a text file. Run the ashoptest.php script from a browser. If all of the tests pass, go ahead with the installation.

IonCube Disclaimer
The encoded scripts run fine on at least 95% of servers. We do not guarantee that the ionCube decryption will work on all servers. Troubleshooting of server configurations is not included in our free software support. If you have trouble with ionCube decryption and cannot resolve it with your hosting service or system administrator, then we recommend changing to a hosting service
that supports the requirements of the AShop program.

Update Instructions

1.Make a backup of the AShop directory and SQL database.  
 
2.Upload and replace all of the files from the update folder to their corresponding AShop directory location.  
Note: the admin/config.inc.php, page template files, and logo.gif are not included in the UPDATE folder so you can upload the entire file structure without accidentally replacing the configured files in your existing installation.  
 
Notes about sites that have modified some of the scripts.  
 
USING THE OFFLINE CREDIT CARD PAYMENT OPTION  
The accepted credit cards, such as Visa, Mastercard, Amex, are set in the admin/gateways/offline.gw file. (Or admin/gatewaysuk, gatewayseu, etc.) After uploading the update files, edit the offline.gw file if necessary to remove unaccepted cards.  
 
CUSTOM IMAGE FILES  
If you have replaced the language specific image files in the images directory, do not upload the images directory.  
 
LANGUAGE AND RECEIPT TEMPLATE FILES  
If you have modified any of the language or receipt template files, make the same mods in the new files or compare the files. The only language that have been changed is delivery.inc.php. A new receipt template is added in the admin directory; receipt-en.txt for the plain text receipt option. (used in retail catalogue only)  
 
3a.As of 3.8.0, Ensure that the file permissions for admin/config.inc.php are 777. When the install.php script runs, it will rewrite the config.inc.php file with the same database settings and new code below it. A config.incEXAMPLE.php file is included with the update package for comparison if needed.  
 
3b.If you are updating from pre version 3.6.9 and using an offline credit card option. Set the accepted credit cards and security code option in the admin/offline.gw file. Note also that as of version 3.6.9, the URL for product file downloads, which is included in receipts for downloadable products, is now deliver.html (not to be confused with the delivery.html page template). The deliver.html page redirects to deliver.php. This is changed to reduce the possiblity of receipts being blocked by spam filters.  
 
3c.If you are updating from pre version 3.6.5 and wish to use the fulfilment features or non-US currencies, chmod permissions of the following new directories to 777.  
admin/gatewaysgbp  
admin/gatewayseur  
admin/fulfilment  
 
3d.If you are updating from pre version 3.6, change permissions of the "updates" directory to 777 if the Send Update feature is to be used.  
 
3e.If you are updating from pre version 3.5, change the name of the file admin/config.incEXAMPLE.PHP to config.inc.php and set the database values. The install.php script will set the path and URL. Preferences are stored in the database as of this release.  
 
Note: As of version 3.5, the following files are no longer used and may be deleted from the admin directory.  
template.inc  
checklogin.inc  
ashopfunc.inc  
ashopconstants.inc  
The download folder may also be deleted.  
 
4.Run update.php by opening the file in a browser.  
Example: http://www.yourdomain.com/ashop/update.php  
This will update the database and rewrite config.inc.php without affecting existing data.  
 
Note: As of version 3.6.3, only the database settings are stored in config.inc.php. If updating from a version prior to 3.6.3, install.php will automatically save the other settings to the database and rewrite config.inc.php.  
 
5.If you are updating from version 3.5.3 or earlier, login to AShop Administration Panel > Layout and set the thumbnail image size. Early versions of AShop had this hard coded to 100 x 100 pixels.  
 
6.As of version 3.6.7, there is a new page template named thankyou.html. This template is only used for the payment confirmation pages and delivery.html is no longer used for payment confirmation pages. Many payment gateways get the payment confirmation page from AShop and render it within a secure page on their server. All links and image URL's used in the thankyou.html page template should be absolute. Image URL's should be https to avoid browser security warnings.  

Version 3.6.3 Or Earlier - Ensure that the config.inc.php file is overwritten!
As of version 3.6.3, all of the configuration preferences (variables) except the database settings are stored in the database table 'preferences' instead of in the config.inc.php file. This is done for increased security. Running the update.php script adds and modifies database tables and should also rewrite the config.inc.php file to look in the database for the preferences.

After updating AShop Deluxe to version 3.6.3 or higher from a version prior to 3.6.3, view the admin/config.inc.php file to ensure that it has been overwritten with the new content. The new config.inc.php should only have database settings and some code. An example file, named config.inc.phpEXAMPLE, is included in the update folder. The program will run from the old config.inc.php variables, but it may cause trouble if you are using any of the new features that have preferences set in the database 'preference' table.

There are a few conditions for the config.inc.php file to be overwritten by update.php.

1.The preferences table must be empty (if it isn't it would mean that this has already been done).  
2.There must be a correct value for $ashoppath in the old config.inc.php.  
3.The config.inc.php file must be writeable by the web server. This usually requires permission settings of 777.  

After performing the update and ensuring that the config.inc.php file was overwritten, the permissions for the config.inc.php file should be changed to 755.