Bigcommerce Change Logs – January 2016

$

Bigcommerce Change Logs – January 2016

Change Log Summary & Notable Changes

We have organized a list of all the changes made to the Bigcommerce platform during January 2016. A few changes listed in the Bigcommerce change logs that we thought should be highlighted are included in our summary list.

  • Multiple fixes were put in place regarding “payments”. Including Paypal and Authorize.net, the two most common payment gateways. We recommend reading the payments section in the full list to understand if you are affected by these changes.
  • New API Features – 2x new additions to the Bigcommerce API now allow for custom fields on orders and customers to be retrieved. This is important because a lot of times you will want to collect additional information on you orders and dynamically integrate with another service or export the data. This is now possible!
  • Blogs can now have a different title (a new field was added) than what you name the blog in the back-office.
  • Product cost now comes across in the order export feature. This is used to generate accurate profit and loss statements and is a long-awaited feature.
  • Product Filtering Fix – The limit of “30” filters has been removed. Now a “show more” link will appear to allow the customer to view more filters.

Complete Bigcommerce Change Logs – January 2016

The complete list of available Bigcommerce change logs are posted below and was collected from the Bigcommerce forum. The arrangement has changed and is sorted chronologically per section type.

Payments

[bug-fix]
For stores that have PayPal Website Payments Pro set up, after an item has been added to cart on the store front, the shopper clicks the “Checkout with PayPal” button on the View cart page. The shopper is redirected to the PayPal checkout page which did not include the order description. We have fixed this by including the order description with the store name and order total in the description.

[bug-fix]
For stores using the PayPal Payflow Pro payment gateway, when merchants login to PayPal Manager, the invoice number field was blank. We have fixed this by sending the Bigcommerce order ID information to PayPal.

[bug-fix]
For PayPal Website Payments Pro (US), there was no error message on failed payments for manual orders. We have fixed this.

[bug-fix]
Merchants who use Authorize.net payment gateway has been notified that the they are implementing Akamai network technology changes and there are new transaction URL’s that have been created to replace the old one. Bigcommerce has updated our code to utilize these new URL’s. There is no action needed from the merchants regarding these changes. More details of the Authorize.net changes can be found on https://www.authorize.net/support/akamaifaqs/

Shipping

[bug-fix]
Enable Endicia for shipping and set up an Australian shipping zone with at least one valid shipping method. When attempting to print a shipping label using a “To: address” in Australian Capital Territory, the label failed to print. This has been fixed.

[bug-fix]
In Endicia, if you have created a shipment for a product that has a product list option, and that option is configured to factor for shipping “weight only”, the label printing modal encounters an error. This has been fixed.

[new-feature]
Shipper HQ app has now been updated to support multi-users in the store.

[bug-fix]
We have fixed a regression that showed “invalid shipment dimensions” error when merchants try to create a shipment with a product that has no dimension (all width, height and length fields are set to zero).

[bug-fix]
Configure the shipping method as Canada Post on a store and set the “shipping from” address to an address in Canada. An error is generated when the merchants attempt to use it to generate a quote for a product with a valid weight and dimensions. We fixed the issue and a valid quote is now returned.

[bug-fix]
Customers place an order on store front and add a company name to the ship-to address. Merchants go through the process of creating a shipping label for that order. The company name that was entered for the shipping address did not appear on the shipping label. This has been fixed.

API

[new-feature]
We have added support to return any custom form fields for Customers and Customer’s address endpoints. In other words, issue a GET on /api/v2/customers/{your_customer_id} and you will see the field (with its label) in the custom_fields array. Also, issue a GET on /api/v2/customers/{your_customer_id}/addresses and you will see the field (with its label) in the custom_fields array. This new feature is on a gradual roll-out plan and merchants can expect to see this update in their stores in the next few weeks.

[new-feature]
We have added support to return any custom form fields for Orders and Order’s shipping address endpoints. In other words, issue a GET on /api/v2/orders/{your_order_id} and you will see the field (with its label) in the custom_fields array. Also, issue a GET on /api/v2/orders/{your_order_id}/shipping_addresses and you will see the field (with its label) in the custom_fields array. This new feature is on a gradual roll-out plan and merchants can expect to see this update in their stores in the next few weeks.

Discounts / Coupons / Gift Certificates

[bug-fix]
If a coupon code has special characters in the actual code, attempting to view the orders that use the coupon does not encode those special characters. Some characters in particular, such as “&” and ?, can make it so that you cannot search for orders that use those coupons since it doesn’t get encoded and breaks the URL parameters. Both the link to View Orders under Marketing > View Coupon Codes > Action > View Orders, as well as the link that you are taken to when you go to Orders > Search Orders and enter a coupon code to search by, did not return the orders that used the coupon. This has been fixed.

[bug-fix]
When “Specify a list of allowed gift certificate amounts” is selected in Marketing > Gift Certificates, empty parentheses are left on the purchase gift certificate page under the amount field. We have fixed this issue.

Blogging

[new-feature]
When merchant creates a blog post, the default page title is just the title of the blog post. We have added capability to allow merchant to specify a custom page title if they would like to use one.

Checkout

[bug-fix]
Shoppers were unable to checkout as they were being looped to the first step of checkout. This happens for products that have the file upload option and if the shopper uploaded a file that has file size > 85 Mb. Once they chose a payment method and try to proceed to step 6, an HTTP 500 error was returned. This has been fixed.

Import / Export

[bug-fix]
Having an option name with commas in it will cause a re-import of those options to ignore the values preceding the commas and create a new option. This has been fixed.

[bug-fix]
Order data was not exported when using a custom export template. This affects both CSV and XML downloads. Using a built-in template (e.g., “Default”) works fine. We have fixed this.

[new-feature]
We have added “product cost” for order exports. This enhancement allows merchant to accurately calculate P&L statements, gross margin, etc.

Taxes

[bug-fix]
In Avalara, after an order is either partially refunded or fully refunded, the previous tax code (if the client specifies a specific tax code for the product) is not consistent, instead it will default over to “P0000000” (which is a “Tangible Personal Property (TPP)” according to the toolkit). This is not a desired behavior because non-taxable items (specified by the tax code from the tool kit) will have a tax refund associated to the product. We have fixed this by retaining the tax code after an order is refunded.

Control Panel

[bug-fix]
In Settings > Account Sign-up Form, click the action button (gear symbol) on one of the field and choose edit. In the pop-up window, the cancel text disappears when hovering over the button. This has been fixed.

[bug-fix]
All administrator user accounts, regardless of permissions, are able to access various sections (tax, DNS, Legacy API, Shipping, Payment, Store Settings, etc) of the control panel and make changes to it. This is problematic for merchants who want to give limited access to their store to certain employees. For example, to allow contractors to write blog posts only. We have fixed this issue by only allowing access if permissions are explicitly given for that user.

Ebay

[bug-fix]
In the new control panel, select a currency other than the standard currencies for US, UK, Australia or Canada. Navigate to Marketing > “Sell on eBay”, and the page is redirected to the control panel front page. There was no error message explaining why eBay settings are currently not available to them and that they need to enable a valid currency for one of the above countries. An error message has now been added.

Product Options

[bug-fix]
We have fixed a bug that caused an option set to not be editable when a special character (e.g. single quote) is used as part of the name of an option or filter.

Product Filtering (faceted search)

[new-feature]
We have added warning message to ask the merchant to verify their product filters whenever a change to product custom fields that will result in a change to currently visible product filters.

[bug-fix]
If a product contains a product option or custom field with the same name as a built-in facet (eg. brand, category, rating etc.), then the product filtering management page fails to show any available filters and the feature can’t be used. This is fixed by preventing the creation of filters with the same name as the built-in ones.

[new-feature]
When using faceted search, there is a limit of 30 values to display for any single facet. We have added a new feature to display a “show more” link when there is more than 30 values. This new feature is currently being tested and will roll out to all merchants soon.

Orders

[bug-fix]
We have fixed a regression that happened to a subset of merchants, when there was no past or current orders displayed for customers on the View Customers page. This regression was caught and fixed within a couple of hours since it was introduced.

Order Installation Service