Got this error while trying to install:
Fatal error: Class Drupal\commerce_sell_once\SellOnceChecker contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Drupal\commerce_stock\StockCheckInterface::getTotalAvailableStockLevel) in C:\xampp\htdocs\fabricremnants_dev\drupal8\web\modules\contrib\commerce_sell_once\src\SellOnceChecker.php on line 11
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare
Comments
Comment #3
karlsheaCan you see if the 1.0.x-dev version works for you? I haven't updated the site I'm using this module on to commerce_stock 1.0 yet.
Comment #4
jdcllns commented1.0.x-dev Seems to work fine. Once installed, I used Views Bulk Operations to update the products' Sold value to False. I was able to use the Sold value in various Views. Once I purchased an item, its "Add to cart" button changed to "Out of stock". I did get it to crash by going back into the purchased item, bumping its Stock Level back up to 1, then hitting Save. My opinion is that the module should gracefully handle this situation. But if I switch to this module, I'll remove the Stove Level widget from the form.
This is a very useful module that I would very much like to put into production ASAP.
I'm also concerned that "This project is not covered by Drupal’s security advisory policy." Can that be corrected?
Comment #5
karlshea> bumping its Stock Level back up to 1
This doesn't use stock levels. It's either sold (commerce_sell_once_sold field is true) or not (false). For the site I'm using this module on, the default stock service is "Always in stock", and the service for the particular product variation is "Sell Once".
> I'm also concerned that "This project is not covered by Drupal’s security advisory policy." Can that be corrected?
I've opted-in to security coverage, but there isn't a stable release yet. If having a stable covered release is a requirement for you, I could tag something since the module has been working in production for me.
Comment #6
jdcllns commentedI can use it the way it is. Thanks.
Comment #7
karlsheaGood luck with your build!