Timeline for Magento2: Config value cached
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 26, 2017 at 14:28 | comment | added | thaddeusmt | You shouldn't have to clear the cache every time - that will be very slow. If you are changing the configuration value so often that you have to clear the cache every time, you should probably be using another form of storage. After updating the configuration (which should be infrequently), running $ bin/magento cache:clean should update the configuration cache. Or you can do it in the Admin Cache Management area as well. | |
| Jun 24, 2017 at 19:44 | vote | accept | Miguel | ||
| Jun 24, 2017 at 9:11 | answer | added | Nikolas | timeline score: 7 | |
| Jun 23, 2017 at 20:51 | comment | added | Miguel | Because i change the value but i obtain the old | |
| Jun 23, 2017 at 19:24 | comment | added | thaddeusmt | Why do you not want to use the default caching mechanism? Does it work after you refresh the cache? | |
| Jun 23, 2017 at 16:09 | history | asked | Miguel | CC BY-SA 3.0 |