Patch release notes for Workarea 3.2.36.
Fix Exact Match Functionality Being Triggered By a Partial Name Match
Depending on how boosts and name phrase match storing are configured,
multiple "exact matches" can be found from a single partial match in
Elasticsearch. To prevent this, Workarea will only
return the single
match if it is indeed a singleton, not if there are multiple exact
Backport Update to Payment Factory
After builds noticed inexplicable failing tests in v3.2.x when
installing workarea-reviews, it was discovered that the updates to
#capture_order factory method didn't get backported to earlier
versions. This change allows workarea-reviews tests to pass against
v3.2.x, since it makes use of that method.
Improve Consistency of Order Pricing Display
When viewing an order summary in the storefront, the price of each item
matches its original price, with no discounts applied. This is somewhat
confusing as the totals don't add up to the subtotal of the order. The
order summary page now renders the
item.total_price so that these
totals match up in the end.
Additionally, the wording surrounding item pricing has been altered to coincide with the change in the price. Since items no longer reflect the original unit price, but rather the total price, the wording has been changed to "Qty 2: $20.00", rather than "2 @ $10.00 each".
Prevent Double Application of Order-Level Discounts When Determining Packages
Workarea::Packaging class, the subtotal of all shippable items
already includes the order-level discounts after pricing is performed,
Order::Item#total_value is not the total prior to discounts,
only tax and shipping. However, order-level discounts were being
summed and deducted from the
Packaging#total_value, resulting in a
miscalculation of the total price of the Order. This problem doesn't
manifest itself until there are a sufficient number of shipping tiers
(at the very least, 3), because either the top or bottom tier will be
used anyway. Remove the code for subtracting order-level discounts from
the total value of the package, so that the proper shipping price will
be displayed to the user in checkout.
Fix New Release Form Creating Duplicates
The "with a new release" selection on the release selector pops up a
mini form which prompts the user for the name of their new release. This
form is dismissed if the user clicks the button, but still allows
potential user input (including multiple submits), causing duplicate
releases to be accidentally created if one hits enter and clicks the
"Add" button before the page refreshes. Prevent this by adding
data-disable-with to the button so that it can't be submitted twice in
the same request cycle.
Fix Duplication in Search Suggestions Indexing
This is caused by not using the query ID as the ID for the suggestion in
its index after the new metrics engine in v3.4. Additionally, the
BulkIndexSearches job was no longer in the scheduler, it has been