We recently moved drupal commerce over to a MongoDB via: http://drupal.org/project/mongodb which I encourage most of community to do as the performance of commerce has been a night and day difference (also apply the upcoming patch to only pull needed fields in the field info call, but back on topic). I am not aware of the inner working of commerce coupon module, but there is most definitely a conflict with the two modules. My guess is that commerce coupon is using a sql specific command to apply coupons to orders.

I say this because the coupons are saving correctly and are available in the admin, and yes they are active, but return an invalid coupon code system message during validation when trying to apply to an order via the checkout cart.

Relavent Modules (All most recent dev):
Commerce
Checkout
Order
Commerce Coupon
Percentage Coupon
Fixed Coupon
MongoDB
MongoDB fields (sub-module)

Steps to reproduce:

Enable the above modules, create a coupon through the admin ui, and try to apply the coupon after adding a product to the cart. I will mention that we use a custom module to display the coupon form on the actual cart page, but I have also received the same result trying to use the default provided Coupon Pane

Comments

pcambra’s picture

pcambra
he/him
Primary language Spanish
commented
Title: Conflict with MongoDB Project » Compatibility with MongoDB Project
Category: bug » feature

Definitely a feature request

jmomandown’s picture

jmomandown commented

@pcambra: fair enough, as a temporary solution where would be the points in the module, read and write, to which I could force the use of the MySQL database with direct SQL calls?

jmomandown’s picture

jmomandown commented

@pcambra: After uninstalling and re-installing the coupon related modules, everything seems to be working properly in the relation to MongoDB when trying to save or apply a coupon. The problem seems to come from trying to proceed through the checkout with a more common issue:

<?php
EntityMetadataWrapperException: Unknown data property commerce_coupon_order_reference. in EntityStructureWrapper->getPropertyInfo()
?>
jmomandown’s picture

jmomandown commented
Status: Active » Closed (works as designed)

The two modules are already compatible. The Coupon module must be enabled AFTER the mongodb module for the Coupon dependent fields to be in the right place and the modules to function properly

jmomandown’s picture

jmomandown commented
Issue summary: View changes

updated verbiage