-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.2 #215
Closed
Closed
1.2 #215
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tal (#200) * Set amount to the subtotal when the discount amount exceeds the subtotal * Make not discounting price modifications optional * Remove deprecation
* [WIP] Initial opensearch draft * Apply php-cs-fixer changes * Indexing works with opensearch * add small cleanup * add small cleanup * Check productlisting with opensearch tenant * Apply php-cs-fixer changes * Replace elastic search everywhere * add more cleanup * add more cleanup * add more cleanup * add original sync command * remove debug * Apply php-cs-fixer changes * Add deprecations and duplicate filtertypes for opensearch * Apply php-cs-fixer changes * Add docs for OpenSearch * Apply php-cs-fixer changes * Add to ignore 404 on create-index * Apply php-cs-fixer changes * fix: ignore 404 as we handle it differently * fix: ignore 404 as we handle it differently * Prepare groups for multi select --------- Co-authored-by: mattamon <[email protected]> Co-authored-by: lukmzig <[email protected]> Co-authored-by: lukmzig <[email protected]>
…th a name that exists When you create a Pricing Rule with an name that already exists the backend interface is not loading the pricing rules anymore because it inserts a row with "null" values. The reason is because the create() call is successfully but at the update() call you get an errror because a pricing Rule with that name already exists. Solution -> wrap it into a transaction
…tal (#200) * Set amount to the subtotal when the discount amount exceeds the subtotal * Make not discounting price modifications optional * Remove deprecation
* [WIP] Initial opensearch draft * Apply php-cs-fixer changes * Indexing works with opensearch * add small cleanup * add small cleanup * Check productlisting with opensearch tenant * Apply php-cs-fixer changes * Replace elastic search everywhere * add more cleanup * add more cleanup * add more cleanup * add original sync command * remove debug * Apply php-cs-fixer changes * Add deprecations and duplicate filtertypes for opensearch * Apply php-cs-fixer changes * Add docs for OpenSearch * Apply php-cs-fixer changes * Add to ignore 404 on create-index * Apply php-cs-fixer changes * fix: ignore 404 as we handle it differently * fix: ignore 404 as we handle it differently * Prepare groups for multi select --------- Co-authored-by: mattamon <[email protected]> Co-authored-by: lukmzig <[email protected]> Co-authored-by: lukmzig <[email protected]>
…th a name that exists When you create a Pricing Rule with an name that already exists the backend interface is not loading the pricing rules anymore because it inserts a row with "null" values. The reason is because the create() call is successfully but at the update() call you get an errror because a pricing Rule with that name already exists. Solution -> wrap it into a transaction
…th a name that exists When you create a Pricing Rule with an name that already exists the backend interface is not loading the pricing rules anymore because it inserts a row with "null" values. The reason is because the create() call is successfully but at the update() call you get an errror because a pricing Rule with that name already exists. Solution -> wrap it into a transaction
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.