VanGo 2.10 Released

VanGo 2.10 has been released. Please contact our support team  if you would like to upgrade to this version.

The following defects were addressed in this release:

• #2609: Hard-Coded Checkout errors

  • Problem: Several VanGo error messages were hard-coded in the product. 
  • Resolution: Code update to allow modification of error messages by customers.
   

• #2610: VanGo Account Management Order Confirmation Issue

  • Problem: The checkout email confirmation and the Account Management "email me my order confirmation again" do not include the same info. When resending the order confirmation, it contained no information identifying the receipt as being from any organization.
    
  • Resolution: Code changes to add this to the email confirmation.
   

• #2611: VanGo Bug frequently updating web.config

  • Problem: Older versions of VanGo included a line in the VanGo global.asax.cs code that was writing to the web.config to update the Request.Url.Authority.ToString key causing a serious performance issue for high traffic sites as the IIS app restarts every time the web.config changes.
  • Resolution: A temporary solution was put into place for customers while this issue was being resolved, and the fix is now officially released as a part of 2.10.
   

• #2613: Category "Not Visible" sets to active=0

  • Problem: Marking a category to Not Visible onlineset it to active=0 in the VanGo Database. This caused an issue on the next page load where it made the category red and uneditable (including making a change to set the category to Visible).
  • Resolution: Code changes to update the way this is handled in the database.
   

• #2614: % of Shipping for Handling computing off Total, not Item Cost

  • Problem: The handling charge set up in iMIS to compute as 10% of the order, up to a maximum of $10.  When the cart charge is figured, it appeared to base it on the total cart - so a maximum of $10.00 is computed and charged. VanGo needed to charge the amount only on the Orders module and not the entire shopping cart presented a challenge, since the iMIS iBOs that are computing the charge and the calculation were in the iMIS code and not the VanGo code.
  • Resolution: All applicable VanGo and iBO code was updated and VanGo 2.10 now has a fix in place that resolves this issue for any clients experiencing this problem.
   

• #2616: Multi-Select Event Question options running together

  • Problem: Previous to the release of VanGo 2.10, many clients experienced display issues when using Multi-Select Event Questions (lines were running together).
    
  • Resolution: Updates to the code that change the way Multi-Selects are handled by VanGo.
   

• #2617: Address field pulling State Code, not State Description

  • Problem: VanGo Address pages pull the state code rather then the description of the state (NY instead of New York).
    
  • Resolution: For consistency, we have updated VanGo so that the address page uses the description, not the code.