Wishlist Submodule for Silverstripe Shop

Allows customer to maintain multiple wishlists. Can be maintained from the WishListPage on the frontend. Originally supported both ss-shop and ecommerce modules, but ecommerce support is now only in the "agnostic" and "ecommerce" branches. For ongoing features I've chosen to specialize on ss-shop., _(*1)

USAGE:

Install module via composer (markguinn/silverstripe-wishlist) or the old-fashioned way. Add the following to mysite/_config/config.yml:, _(*2)

Product:
  extensions:
    - CanAddToWishList

Make sure to dev/build?flush=1. You can add this extension to any Buyable model. It should work with non-sitetree models but that has not been tested., _(*3)

You may need to include the WishListButtons.ss template or update your existing one in the spirit of the one included with this module., _(*4)

TODO:

Add to alternate list from product page
Ajaxify product page
View in CMS
"Save an idea" feature
public/private lists
share with link
Apply to ProductVariations and test

DEVELOPERS:

Mark Guinn - mark@adaircreative.com

Pull requests always welcome. Follow Silverstripe coding guidelines., _(*5)

LICENSE (MIT):

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:, _(*7)

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software., _(*8)

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE., _(*9)