CoCart v2.0.0-beta.2

This release applies a couple of tweaks and one fix.

  • Fixed: $this error with getting cart to check if item is in cart.
  • Tweaked: Check if cart is empty before removing an item.
  • Tweaked: Re-ordered registry of routes to be in alphabetical order.
  • Updated: POT file.

Release Date

I’m hoping to release CoCart v2 next Tuesday, 25th June 2019 so please test and report feedback for any issues before then.

P.S. Again, please only test on a local environment or staging site. If you come across an issue, please report it via the GitHub repository. Thank you 🙂

Coming in v2: Totals

Fetching the cart totals is one of the most important parts of the CoCart API and while you do get all the information you need, they were not always returned in the same format when it came to the actual totals and did not have the currency symbol applied.

I’m sure developers would have to convert the values and apply the currency symbol after fetching the totals which could also increase load time for their app with the additional code required.

For version 2, I wanted to make it faster and easier for developers by returning the results pre-formatted ready to simply display them.

All totals can now return as a string with the currency symbol automatically applied according to the store currency set in the WooCommerce settings.

To get these results, simply set the new property as true.

See documentation for example.

That’s it!

Feedback Required!

CoCart v2 is now available for beta testing.

CoCart v2.0.0-beta.1

CoCart v2 is now ready and available for testing.

It’s now more powerful for developers to take full advantage of the REST API to add items and manage the cart.

Not only that, the API is now faster as it is separated from WooCommerce’s REST API and runs it’s own namespace with better returned responses to reduce API requests, more item data and getting a specific customers cart.

CoCart v2 is also backwards compatible so you can still use the current API available but unless you upgrade to the new API you will miss out on the new supported features.

FYI

It’s also recommended that you are using WooCommerce v3.6 or above for CoCart v2 to function properly.

Here is a comparison of the API routes.

Current API

  • wc/v2/cart
  • wc/v2/cart/add
  • wc/v2/cart/calculate
  • wc/v2/cart/cart-item
  • wc/v2/cart/clear
  • wc/v2/cart/count-items
  • wc/v2/cart/totals

New API

  • cocart/v1/get-cart
  • cocart/v1/add-item
  • cocart/v1/calculate
  • cocart/v1/clear
  • cocart/v1/count-items
  • cocart/v1/item
  • cocart/v1/totals

The new API still uses the same properties the only difference for some of them is the endpoint is renamed.

Before v2 is made available to the public I require your feedback for suggestions, issues or bugs that need to be squashed. View the new documentation available for details on the new API.

Please only test on a local environment or staging site. If you come across an issue, please report it via the GitHub repository.

Thank you and enjoy.

Coming in v2: Responses

Getting the correct returned response are important when using the REST-API so providing the option to return the whole cart without the need to call it again is also important.

Now when you add an item to the cart, update item quantity, remove item or restore an item. You can now return the whole cart contents rather than the default response if requested.

For e.g. by default when adding an item to cart, only that item would return it’s details. So before that happens if the return cart parameter is used, the whole of the cart is instead returned with that added item.

Pretty sweat right!

I’m sure developers will find this useful. What do you think of this improvement coming?


Version 2 is still in development so please come back for more news as it develops.

Thank you.