Hello, I've just read your documentation about how to enable lscache on cPanle servers and there's something I'm perplexed about. There are some parts that seem complexe for end users 1) the lscache folder needs to be created With tools like Installatron or Softaculous, we have more and more users that don't use FTP and something as simple as creating a folder could be complexe for some users 2) end users must manually enable public cache in their htaccess folder Shouldn't this be managed by the WordPress plugin ? 3) lsws needs to be restarted ? Your documentation implies that lsws has to be restarted once a user has enabled public cache in their htaccess file. If the documention is correct then this completly prevents the WordPress cache plugin from being self service. I would like to suggest either adding all 3 steps to the lswp cache plugin itself, so when you click on enable it detects that cache path, creates the folder if it's required, adds the correct lines to the .htaccess file and then make it so lsws don't need to be restarted. If the plugin is not able to do all of these things then there needs to be an end user cPanel plugin so he can enable WordPress cache on his websites without requiring help from the sysadmin.