- Used Zammad version: 2.9.x
- Used Zammad installation source: docker-compose
- Operating system: Debian 9
- Browser + version: Chromium
I’m curious about this option:
Admin -> Settings -> System -> Frontend
Option: Client storage
Description: Use client storage to cache data to enhance performance of application.
Allowed values: yes/no
I enabled this because it sounds like it would make Zammad faster, but I also wondered if it might have any negative effects. I searched through the code, but it doesn’t look like it’s actually used anywhere:
email@example.com ~ (develop) % ag --nopager -i 'ui_client_storage' . db/migrate/20170123000002_fixed_translation.rb 39: 'name' => 'ui_client_storage', db/seeds/settings.rb 590: name: 'ui_client_storage', 598: name: 'ui_client_storage',
If I’m grepping correctly, the usage of this option was removed with this commit:
commit 4a9c2c55b2ef46b3e0d49a158fb79ebb4306c256 Author: Martin Edenhofer <firstname.lastname@example.org> Date: Tue Nov 3 19:36:24 2015 +0100 Removed storage options from collection helper.
Looks like it’s superfluous and should be removed