Assets are CSS/JS files that are used on almost all pages to make them look/work as expected. To ease development process developers can create multiple CSS/JS files and In-Portal would combine them together to make page load faster (less network traffic). It works like this:
- upon page load the missing assets are generated and existing assets are reused
- during new website version deployment all assets are deleted
This approach works fine, when In-Portal is used to both "show the page" and to "prepare page html".
Unfortunately when In-Portal page referencing assets is transformed into static HTML and later used outside of In-Portal (e.g. on the WordPress) the referenced assets won't exist anymore. The assets won't exist because next deployment removed them in hope, that next website visit would happen and rebuild them.
- create "MinifyHelper::dump" method, that will CURL website homepage to trigger generation of assets
- create "adm:OnDumpAssets" event, that will call "MinifyHelper::delete" and "MinifyHelper::dump" methods
- no longer call "MinifyHelper::delete" method from "kThemesHelper::refreshThemes" method
- create "DeploymentHelper::dumpAssets" method, that will:
- be declared after and be similar to "DeploymentHelper::refreshThemes" method
- call "adm:adm:OnDumpAssets" event
- call "DeploymentHelper::dumpAssets" method right after "DeploymentHelper::refreshThemes" method
- on "Tools > System Tools" page:
- update documentation for "Deploy" button to explain that assets are also being dumped
- add another button for dumping assets