Categories
Core

CoCart Lite v3.1 Release Candidate 3

I’m excited to announce that CoCart v3.1 Release Candidate 3 is now available for testing! You can either download it directly from GitHub or install the CoCart Beta Tester plugin.

This release fixes a couple of bugs but I couldn’t help my self in adding something mind blowing for developers. Check what’s new below for more.

For a full recap on what’s new in v3.1 see the following previous posts before continuing:

What’s New since CoCart v3.1 Release Candidate 2?

  • NEW: Ability to set the customers billing email address while adding item/s to cart. Great for capturing email addresses for cart abandonment.
  • NEW: Ability to return only requested fields for the cart response before fetching data. Just like how GraphQL functions. Powerful speed performance.
  • Fixed: Issue with merging carts should one be empty.
  • Fixed: Coupons duplicating on each load.

Capture customers email

Pass the customers email address and it will be set in session ready for when it comes to creating the order. Should the custome left the store with the cart unfinished. The email address is there ready for you to use which is great for cart abandonment purposes.

curl -X POST https://example.com/wp-json/cocart/v2/cart/add-item \
  -H "Content-Type: application/json" \
  -d '{
    "id": "71",
    "quantity": "1",
    "email": "mindexploding@awesome.dev"
  }'

Get cart with limited fields

Here is an example of only getting the cart for the following fields: cart_key, items and totals. Simply list them as a string followed by a “,” and the response will only return those fields.

curl -X GET https://example.com/wp-json/cocart/v2/cart \
  -H "Content-Type: application/json" \
  -d '{
    "fields": "cart_key,items,totals"
  }'

Database changes

This release does not introduce any changes to the database.

Documentation

Currently being updated. Check again soon or follow CoCart on Twitter for updates.

Testing

If you discover any bugs during the testing process, please let me know by logging a report on the GitHub repository. There I can manage it better and get on the issue asap.