Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
litespeed_wiki:cache:litemage:troubleshooting:multi-site-cache-not-updating [2017/05/09 15:51] Jackson Zhang [Cache Not Updating On One Store In A Multi-site Setup] |
litespeed_wiki:cache:litemage:troubleshooting:multi-site-cache-not-updating [2017/05/09 15:54] Jackson Zhang [Solution] |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| ==== Solution ==== | ==== Solution ==== | ||
| - | Usually, the virtual host cache root should be located under ''/home/$USER/lscache'' and cannot be in a centralized location,such as RAM disk, for multi-site setups. Even in /home/$USER/lscache location, It can not be like /home/$USER/lscache/domain1.com, /home/$USER/lscache/domain2.com for multi-site. All multi-site domains should have only one cache root location, such as /home/$USER/lscache. "lscache" folder can be renamed to other folder, such as /home/$USER/turbocache. | + | Usually, the virtual host cache root should be located under ''/home/$USER/lscache'' and cannot be in a centralized location,such as RAM disk, for multi-site setups. Even in /home/$USER/lscache location, It can not be like /home/$USER/lscache/domain1.com/, /home/$USER/lscache/domain2.com and /home/$USER/lscache/domain3.com for multi-site. All multi-site domains should have only one cache root location, such as /home/$USER/lscache. "lscache" folder can be named differently, such as /home/$USER/turbocache. |
| If cache root is not located under ''/home/$USER/'', it is likely that the other site cannot see these cached files. Please refer to our **[[litespeed_wiki:cache:common_installation:cpanel-shared| cPanel guide]]** for cPanel environment cache root setup. | If cache root is not located under ''/home/$USER/'', it is likely that the other site cannot see these cached files. Please refer to our **[[litespeed_wiki:cache:common_installation:cpanel-shared| cPanel guide]]** for cPanel environment cache root setup. | ||
| Once the correct cache root is set and the cache has been purged the problem should be resolved. | Once the correct cache root is set and the cache has been purged the problem should be resolved. | ||