ScriptMerge makes use of the general Joomla! cache. If you want to clean the ScriptMerge cache you can navigate to Tools > Clean Cache in the Joomla! backend.
Through the Joomla! Plugin Manager, you can manage the settings of the ScriptMerge plugin. The following parameters are available:
When testing out these settings, make sure to check the browsers Error Console for any errors. If errors occur, you probably configured something that does not work on your site. Make sure to test things site-wide as well.
The ScriptMerge component is not accessible from the Joomla! backend and contains no parameters.
The Closure Compiler API works over HTTP and requires your firewall to allow outgoing connections. Do not use this with the Merge Type set to Filelist. Also try to set the Skip compressed option to Yes, because the service gives bad results when both MooTools as jQuery compressed versions are included.
Before testing our plugin, make sure CSS is working as well. Use the W3C CSS validator to make sure there are no CSS lines that will break the rest.
You might have installed ScriptMerge and started playing with it. Sure this is possible, but with a valid backup, right? And on a testing environment, right? If no, something really is wrong with the procedure to safeguard your site. Anyway, if you have played with some settings: For instance, enabling ScriptMerge for the backend sounds really cool. But there are tons of experimental options that might or might not work, and if they do not work, they might cause your backend to stop working. Nothing unexpected.
Solution: Restore your backup. If you don't have a backup, that's your real problem. As a last resort, try removing the ScriptMerge plugin-files from the Joomla! folder system/plugins. After you have gained access to your Joomla! backend, remove the ScriptMerge extension. Optionally reinstall it. Create a backup first.
To use ScriptMerge together with full page caching, you need to set the option Merge Type to Filelist instead of Checksum. Note that this causes all CSS-files and JS-files to be passed as an argument to the ScriptMerge component. Some webservers limit the URL-length, causing problems here.
When the ScriptMerge option Merge Type is set to Filelist, the ScriptMerge component is activated and called through a Joomla! URL. When using third party SEF extensions, the original System URL is modified by that extension. Most likely that third party SEF extension has bad support for the ScriptMerge component. Therefor, modify the SEF extension to exclude the ScriptMerge component. If such an option is not available in the SEF extension, switch the Merge Type option to Checksum or choose a different SEF extension.
If a CSS-file is choosen to be included in the merging process, but that CSS-file is not ending with the css file-extension (example.css), that file will not be outputted by ScriptMerge when setting the Merge Type to Filelist. If this is the case, change this option to Checklist instead.
When using some of the online tools of Google, Google will report that some of the resources that Google needs to interpret the page are excluded from the robots.txt file. The caching files of ScriptMerge are stored in /cache and if this folder is defined in the robots.txt of your site, this error is given. If you want the checks to behave properly, open up the robots.txt and temporarily remove the /cache folder. We recommend you re-add the entry once you're done.