So on review the core module now has commerce_stock_enforcement which resolves this issue.
his patch adds a safety check that re-validates stock immediately before an order transitions to the Placed state. It prevents orders from completing when stock has changed since the item was added to the cart (e.g., manual stock updates or concurrent purchases), which can otherwise result in negative stock.
Feels like this should be closed: https://www.drupal.org/project/commerce_shipstation/issues/3485865 📌 Drupal 10 compatibility fixes Active
Thanks for this, I've created the follow up tickets and will add this to the next release
As there has been not feedback on this for over a year I'll mark as closed.
Any progress on this?
Latest changes want apply
Could not apply patch! Skipping. The error was: Cannot apply patch https://git.drupalcode.org/project/change_pwd_page/-/merge_requests/12.diff
In Patches.php line 331:
Cannot apply patch password (https://git.drupalcode.org/project/change_pwd_page/-/merge_requests/12.diff)!
c_archer → created an issue.
c_archer → created an issue.
c_archer → created an issue.
Can confirm patch in #21 works.
This is a great suggestion and would make it much easier to add new subscriptions.
c_archer → created an issue.
c_archer → created an issue.
Here is a patch to correctly render the pager
c_archer → created an issue.
Ran into this issue, have created a patch implementing mglaman's idea
c_archer → made their first commit to this issue’s fork.
Thanks mlncn, thats it working!
Tried this path, but it does not appear to be working, do I need to do anything?
Works as expected
Patch from #8 works as expected
To replicate use the form type: Use Opayo Drop-In form - easier PCI compliance (SAQ-A) but less customer friendly checkout experience.
c_archer → created an issue.
Latest patch works as expected, am able to suspend a queue
Patch #23 works well with no issues.
Latest patch works well.
It would be great if we could set how many revisions are kept, sites with a large product database could end up with very large revision tables. Allowing to set a cap would be a good solution for this.
Latest patch seems to work well
I think this was a env variable missing, closing ticket.
I had an issue with this today on a large dataset, applied the patch and it resolved the issue for me in the short term till I can resolve the data issue.
c_archer → created an issue.
Patch #29 and #27 does not apply against version 4.0.0-alpha6
c_archer → created an issue.
I added a date range facet and a commerce price field with a range facet.
c_archer → created an issue.
c_archer → created an issue.
Added a patch on the other module
Created a MR to resolve the issue.
Have created a MR to resolve this.