Upgrade from previous version

This section details out the process of upgrading from 3.1 to 3.5. It also includes important notes to be aware of before and after upgrading to v3.5

  1. Make a backup of all files in the web folder
  2. Stop the IIS app pool
  3. Make a backup of the current database
  4. Delete the following folders from the web application root folder:
    • /bin
    • /Scripts
    • /Views

  5. Rename robots.txt to "robots.txt.old" - It will be automatically imported into the new CMS area.

Note: The robots.txt file is now managed from the Admin Control Panel > CMS > Content area. If the robots.txt file still exists in the web application root folder, crawlers will receive a 500 error. Delete the robots.txt instead of renaming it to "robots.txt.old" if no important information needs to be imported from the existing file.

  1. Copy the contents of the installation package /Web folder to the web application root folder, overwriting all files.

Note: If you have made any changes to web files, those changes will need to be re-implemented into the new web files. (See below: Customizations and upgrading )

  1. Changes to the web.config file:
    • database connection string
    • license key

    • Base URL (https://example.com/) The URL and Secure URL settings have been removed from the Admin Control Panel and replaced by this web.config setting.

    • SMTP settings
  2. Execute the following SQL Scripts:
    • AuctionWorx.sql

Note: If you have made any changes to the stored procedures, be sure to back them up separately and re-implement them after running the SQL scripts.

  1. Restart the IIS app pool
  2. Once the site is active go to [Base URL]/Account/Logon
  3. Log in as an admin user and go to [Base URL]/Admin/Checksite

 

Important changes in v3.5 and Additional Steps After Deployment

  • AuctionWorx 3.5 uses Stripe Intents. The Stripe account will need changes from the Stripe Dashboard to work correctly.
    • AuctionWorx will automatically setup the Webhook Endpoints when you navigate to the Admin Control Panel > Billing & Fees > Stripe page and add your Stripe Client Id and API Keys.

    Additional Info: https://www.rainworx.com/rwkb/Update-Stripe-3.5.8333.htm

     

  • If Sub-Navigation is used on the Site Header, update the Site Header Style setting to Original from the Admin Control Panel > Site Preferences > Display page.

     

  • AuctionWorx 3.5 uses reCAPTCHA version 3. Generate new reCAPTCHA keys for the Admin Control Panel > Site Preferences > Contact page.

    Additional Info: https://www.rainworx.com/rwkb/Recaptcha-v3-Setup.htm

     

  • In AuctionWorx 3.5 we have standardized custom fields for both Phone Number and Company Name. If Custom User Fields Phone or Company were already in use prior to the upgrade, you'll want to use the included SQL script to copy the data from the old fields to the new standardized fields. Then delete the old custom fields (AuctionWorx_CopyCustomUserProperties.sql )

     

Customizations and upgrading

If your site has had any customizations done, any custom changes you want to keep will need to be migrated over or re-implemented to the latest version codebase.

Depending on the overall size and kind of customizations done, you might be able to try a 3-way merge as part of the process.

 

Overview for doing a 3-way Merge

We recommend using a diff tool that supports a three-way merge such as Beyond Compare 4 Pro from Scooter Software: http://www.scootersoftware.com

With this tool, you click “Folder Merge” from the home screen, then enter the following paths:

  1. The original build package (“ancestor path”)
  2. The new build package (“left path”)
  3. Your modified files (“right path”)
  4. Optionally, the folder where the results should be copied (“Merge To” path)

This will perform a folder compare with the new build folder on the left hand side and a copy of your current MVC Project files on the right hand side. It is frequently the case that almost all files will have been modified either on one side or the other, so these differences will be handled automatically. Just the changed file will be copied to the result location.

There will inevitably be some cases where the file changed on both sides, and will need to be merged manually. Most of the time it will be obvious which lines need to be copied from each side (e.g. line 10 changed on the left, and line 500 changed on the right, so both changes are assumed to be needed in the result). This process is facilitated by Beyond Compare taking an educated guess of the appropriate changes – you mostly just need to review the recommended merge result and save it.

Rarely, the same line, or lines right next to each other, have been changed on both sides and you have to determine which side is more correct based on the intent of the changes. These situations are highlighted and marked graphically by Beyond Compare to bring your attention to the conflict.

Once all merge conflicts have been handled you can then copy the results to replace your current project, and then re-compile and publish as usual.

If anything goes wrong, to rollback: Restore your backed up database then copy your backup web root back into your production web folder (with overwrite).