Closed (fixed)
Project:
Entity cache for Drupal Commerce
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Jan 2016 at 21:19 UTC
Updated:
4 Apr 2016 at 15:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mglamanComment #3
mglamanUpdate hook to disable order entity cache, and keep settings in case someone feels adventurous. And opens door to have it fixed.
Comment #4
mglaman3:28 PM mglaman: we should probably update the readme to match and we'd have to be clear on the module page we were disabling something on people, but otherwise yah
3:28 PM mglaman: oh and you spelled commerce wrong :)
3:29 PM mglaman: also, maybe link to this, https://www.drupal.org/node/2240427#comment-10709112 in the comment, which explains why in a bit more detail
Update project page, readme.
Comment #5
vulfox commentedI'm currently looking at using this at our site. Would it be better to wait for this update? Is the current behaviour very unsafe?
Comment #6
mglamanvulfox, you can use the module. I'd just recommend running "variable_set('commerce_entitycache_cache_orders', FALSE);" in an update hook, or apply this patch. It's not necessarily unsafe, but could be problematic in a large Drupal Commerce site. The module removes the locking features for orders provided by Drupal Commerce, which is technically a regression.
Thanks for commenting, forgot I need to button this up.
Comment #7
liamanderson commentedConfirm patch from #3 is working.
Comment #9
mglaman