Documentation You are here: start » v » 1.0 » upgrading

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

v:1.0:upgrading [2012/08/16 22:59]
sparkweb Note Server Timezone
v:1.0:upgrading [2014/02/19 20:44] (current)
foxybrett old revision restored (2014/02/19 07:02)
Line 10: Line 10:
   * All FoxyCart templates (cart, checkout, receipt, email) are now fully customizable via the [[.:​templates|Twig template language]].   * All FoxyCart templates (cart, checkout, receipt, email) are now fully customizable via the [[.:​templates|Twig template language]].
   * Zip Code based tax rates are now built in. [[.:​taxes|More info.]]   * Zip Code based tax rates are now built in. [[.:​taxes|More info.]]
-  * Very cool new country+state autocompleter. Country-specific language when it comes to state/​province/​county/​etc.,​ and it also displays the country flag for an added visual confirmation that the correct country is selected. [[.:​checkout|More info.]] +  * Very cool new country+state autocompleter. Country-specific language when it comes to state/​province/​county/​etc.,​ and it also displays the country flag for an added visual confirmation that the correct country is selected. ​ 
 +  * Option to include or not include past due amounts when processing subscriptions. 
 +[[.:​checkout|More info.]]
 ==== Bug Fixes and Changes to Existing Behavior ==== ==== Bug Fixes and Changes to Existing Behavior ====
 There are many, many bug fixes to v1.0 noted on the changelog, but none of them (in our opinion) should cause problems even for advanced integrations. That said, make sure to read through the changelog thoroughly if you have a very advanced integration. Downgrading from version 1.0 is not recommended as zip-code based taxes are not supported in previous versions and may cause problems for your store. 1.0 comes with our new pricing plans. If your store is already live, you will be asked to confirm your new pricing plan when you upgrade. If your store is not yet live, the pricing plan selection will take place when you go live There are many, many bug fixes to v1.0 noted on the changelog, but none of them (in our opinion) should cause problems even for advanced integrations. That said, make sure to read through the changelog thoroughly if you have a very advanced integration. Downgrading from version 1.0 is not recommended as zip-code based taxes are not supported in previous versions and may cause problems for your store. 1.0 comes with our new pricing plans. If your store is already live, you will be asked to confirm your new pricing plan when you upgrade. If your store is not yet live, the pricing plan selection will take place when you go live
  
  
-===== Upgrading ​from v1.0 =====+===== Upgrading ​to v1.0 =====
 ==== ACTION REQUIRED: All Users ==== ==== ACTION REQUIRED: All Users ====
 === Separate Receipt Template Required === === Separate Receipt Template Required ===
Line 25: Line 26:
  
 If you have a more advanced integration,​ you can now use [[.:api|the API]] to retrieve the latest includes code as needed (via the ''​store_includes_get''​ method). If you have a more advanced integration,​ you can now use [[.:api|the API]] to retrieve the latest includes code as needed (via the ''​store_includes_get''​ method).
 +
 +
 +=== Custom Shipping Scripts: Change to the FC.locations Object ===
 +Due to a change to an associative array for the countries javascript object (FC.locations),​ [[:​snippets:​start|custom scripts]] using an iterator based loop to navigate countries like this will no longer work:
 +<​code>​for (var i = 0; i < countries.length;​ i++) { }</​code>​
 +Instead you can reference the country you are looking for directly by its ISO 3166-1 alpha-2 code like '​US',​ '​GB'​ etc. If you need to loop over all of the countries, you can do that using a key-value loop like so:
 +<​code>​for (var code in countries) { }</​code>​
 +The structure changed from
 +<​code>​[{...},​{...},​{...},​...]</​code>​
 +to
 +<​code>​["​AZ":​ {...}, "​AU":​ {...}, ...]</​code>​
 +
  
 ==== ACTION POSSIBLE: Some stores may be impacted ==== ==== ACTION POSSIBLE: Some stores may be impacted ====
 === API date filters now respect the store'​s timezone === === API date filters now respect the store'​s timezone ===
 The API filters for ''​transaction_date_filter_begin''​ and ''​transaction_date_filter_end''​ now correspond to the store timezone settings, not the server timezone (Pacific Time). If you're using these filters you probably want to adjust or at least make sure your integration continues to work as desired. The API filters for ''​transaction_date_filter_begin''​ and ''​transaction_date_filter_end''​ now correspond to the store timezone settings, not the server timezone (Pacific Time). If you're using these filters you probably want to adjust or at least make sure your integration continues to work as desired.

Site Tools