Changes for the week 2017-04-16

  • v2.0: Updating some core code for better compatibility with future infrastructure improvements.
  • v2.0: Including custom shipping fields with [data-fc-shipping-custom-field] set on the checkout in the data set to the custom shipping rate request endpoint.
  • v2.0: fix for the styling on the checkout shipping rates returned where there is an error.
  • v2.0: Fix for Omnipay based gateways (such as Stripe) not sending the address line 1 and 2 information properly.
  • v2.0: Fixing a minor issue with our endpoint for charging past due subscriptions related to today’s earlier rollout.
  • hAPI: Updating some documentation, adding a missing applied_coupon_codes link relationship.
  • hAPI: Fixing an issue which wasn’t allow customer passwords to be updated when using the bcrypt password hashing mechanism.
  • v2.0: Fixed a bug when paying with Amazon which was removing additional checkout fields.
  • v2.0: Adding gateway support for EMSPay.eu
  • v2.0: Fixing a bug which was removing the save customer information option for all checkouts using pay with Amazon.
  • v0.7.2, v1.0, and v1.1: Removing the x_type parameter when sending to eProcessingNetwork to enable their AVS tools.
  • hAPI: Adding the template_config resource which should take the place of the template_set config value. For now, both values will work properly, meaning if you save new information in one place it will also show up in the other. The template_set config property, however, should be considered deprecated.
  • hAPI: Adding the template_set_uri and language properties to the Cart and Transaction resources.
  • hAPI: Adding require_signed_shipping_rates and is_maintenance_mode booleans and the app_session_timetime in seconds to the Store resource.
  • hAPI: Adding dutch to our language validation test as it was missing.
  • hAPI: Adding past_due_amount_handling, reset_nextdate_on_makeup_payment, expiring_soon_payment_reminder_schedule, and send_email_receipts_for_automated_billing to the store subscription settings resource.
  • hAPI: Adding the template_config resource which should take the place of the template_set config value. For now, both values will work properly, meaning if you save new information in one place it will also show up in the other. The template_set config property, however, should be considered deprecated.
  • All Versions: Adding notices to the admin for stores in maintenance mode.