Upgrade From v3.2 to v3.2c


Upgrade or not to.. ?

Upgrading Rapid Classified v3.2 installation to v3.2c is recommended if no substantial customization was made to web pages. For the most part v3.2c is the same as v3.2 except for the built-in plug-ins and a few new features and improvements listed here. Only database content (ads, client accounts, categories structure, settings ...etc) would remain intact after the upgrade. All pages, images, content templates, pages in config folder would be replaced. If any of the pages were amended in v3.2 based web site, then after the upgrade respective pages should be amended over again.

Rapid Classified v3.2c do not support Regular or Light CSS templates any longer. Only XL templates are available for selection in Admin Preferences. If you currently use non XL template at your site, then you would have to choose one of the XL template after the upgrade (XL css template name starts with [xl_] prefix, like: xl_metallica.css).

Note: Direct upgrade from v3.1 to v3.2c is also not supported. If you own a license for older premium v3.1 (not to confuse with license "A" for free v3.1), and need to upgrade to v3.2c, then upgrade site to v3.2 first and then to v3.2c.

Upgrade Steps

For successful upgrade please follow instructions below. Do not skip or change the order of steps.

Note: If you have a third party plug-in installed at your current installation, then you may wish to postpone the upgrade until third party developer releases an update or a note about plug-in upgrade.

  1. Backup current installation. That literally means - download entire content of the current installation along with all pages/folders/subfolder to your computer via FTP.
     
  2. Go to Content Management and make a list of "True Content Pages" and "Custom Inclusive" templates (just write down template names).
     
  3. Download upgrade script: http://www.4u2ges.com/zips/upgrade32to32c.zip

    Unzip and copy upgrade32to32c.asp into the current Rapid Classified installation. Manually navigate to this page in a browser. If running installation with MySQL or MSSQL, then type ID and password for SQL account, which has right to create tables (it would most likely be the same ID and password as you entered in config/config.asp during initial classified setup).

    Click "Modify Database" button. You would receive a message about database upgrade.

     
  4. If your site configured with Regular style sheet template, then before upgrading you must select any template which starts with [xl_] in Design Style at Admin Preferences page. You may select other, one of 30 available templates after the upgrade.
     
  5. Delete the following from current Rapid Classified installation at the web site:

    - All pages/subfolders from "ads" folder
    - All pages from "config" folder
    - All pages from "content" folder
    - help.mdb from database folder (folder name specified in config/config.asp as dbFolder)
    - All images  from "img" folder. You may leave "icons" subfolder intact
    - "scripts" folder itself
    - "sql_setup" folder itself
    - All pages/files from the root of Rapid Classified installation
     
  6. Upload the following to the Rapid Classified installation from RC v3.2c package:

    - All pages from "config" folder into "config" folder at the installation
    - "css" folder (this is a new folder for v3.2c)
    - All pages from "content" folder into "content" folder at the installation
    - help.mdb from "db" folder into database folder at the installation
    - All images from "img" folder into "img" folder at the installation (you may skip "icons" subfolder)
    - "script" folder into installation
    - "sql_setup" folder into installation
    - All pages/files from the root of the "RC" folder into the root of the installation (except setup pages which start with [!])
     
  7. If you had any custom logo or other images in "img" folder, then upload them into "img" folder from installation backup.
     
  8. If you had "True Content Pages" or "Custom Inclusive" templates (you had to create a list in step 2), then upload them from installation backup into the "content" folder at current installation.

    Note: Templates in "content" folder have the same name as templates name in the list. The only difference is, .asp file extension. That is if you had "my_custom_template" inclusive template in the list, then corresponding file in "content" folder would be "my_custom_template.asp".

    Important: Do NOT upload any other template types other than "True Content Pages" or "Custom Inclusive" templates from installation backup. If you customized other templates, such as logo, menu, portals, side bars templates, then you would have to repeat customization when upgrade is finished. Uploading old templates from v3.2 into v3.2c "content" folder, may result in ASP or HTML errors at the installation.
     
  9. Open "language/language.asp" page from installation backup and the same page from RC v3.2c package in an editor. Copy section between '### ADDED FOR V3.2c and '### END ADDED FOR V3.2 in newer page and paste it at the end of backed up page. Save backed up "language.asp" page and upload it into the "language" folder at the current installation.
    If "language" folder at the current installation does not have "search_language.asp" page in it, then upload this page from "language" folder of the v3.2c package (translate it if necessary).
     
  10. Since all pages in "config" folder were replaced in step 6, you would need to customize some of them.

    config.asp - make sure to properly select database type, path to folders, database connection credentials ..etc. Use backed up file as reference or setup_manual.pdf in "Manuals" folder within the package.
    helpconfig.asp - make sure the dbFolder path variable is the same as in "config.asp".
    tn_config.asp - there are few new variables added to this configuration file. Change tn_encode_key value to any string. Change secure_content value to any string. The value you set for secure_content would be your new password to Content Management page and at the same time for Database Conversion Tools page (if you ever use it).
    unique.asp - if you amended this file at the old installation, then make same amendments to the page at the current installation.
    cache_config.asp - if you have "Cache Light" plug-in installed, then you may upload older cache_config.asp page from a backed up instillation into the "config" folder at current installation.
     
  11. Set "modify" permission for "css" folder and its entire content. The procedure for setting permissions is the same as when you initially installed RC v3.2 package.
     
  12. If you made any amendments to RC pages at the old v3.2 installation, then you would need to make respective amendments to newly installed pages. Do NOT ever use pages from older v3.2 at the new v3.2c installation.
     
  13. If you properly followed above steps, then installation is complete. Navigate to your site, logon to admin page open admin preferences. Make a selection for a new configuration - "Image Resizing and CAPTCHA  method". You may select ASPJpeg or ASP.NET methods. If selected ASPJpeg method, then make sure this component is installed on web server (consult hosting support). ASP.NET method preferred as it is available on most any IIS web server.
     
  14. If you had ads caching enabled, then click "Manage Ads Cache" and then click "Start Caching" to re-create ads cache in "ads" folder.
     
Additional steps for owners of "Authorize.net" and / or "Ads Import Tools" premium plug-ins.

If you purchased and installed "Authorize.net" or "Ads Import Tools" plug-in at your current installation, then you would need to reinstall them according to the instructions below from a new plug-in released for RC v3.2c. New plug-in packages could now be downloaded from the premium download page. In case you have purchase a plug-in but do not see the link for a new plug-in at the premium download page, send a note via contact form.

Important: Do not use older plug-in you have previously downloaded for v3.2. Installing older plug-ins would result in errors throughout the application and might require a complete application reinstall.

Authorize.net

  1. Upload "config/auth_config.asp" page from backed up installation into the current "config" folder at the installation.
  2. Download a new "Authorize.net" for v3.2c package.
  3. Upload all pages from "Web Pages" folder within the plug-in package into the root of current RC installation.
  4. If you made any amendments for plug-in pages, then you would have to repeat the amendments over again for newly uploaded pages.
  5. Navigate to Authorize.net admin page. You would have to re-enter and save encrypted key values. Enter your current "Transaction Key" and click "Save" next to it. Enter your current "Secret Word" and click "Save" next to it.

Ads Import Tools

  1. Upload "config/import_config.asp" page from backed up installation into the current "config" folder at the installation.
  2. Upload "Import" folder from backed installation into the current installation.
  3. Download a new "Ads Import tools" for v3.2c package.
  4. Upload all pages from "Web Pages" folder within the plug-in package into the root of current RC installation.