WP Manifestindependent plugin directory
manifest / performance / simple-custom-css-cache

Simple Custom CSS Cache WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA

Add a file cache on Simple Custom CSS plugin(https://wordpress.org/plugins/simple-custom-css/)

★ 2stars
1.0.1latest · 10 years ago

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/beapi/simple-custom-css-cache/archive/refs/heads/master.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.
Simple Custom CSS Cache # Description ## Instead of loading WordPress on every page to get Simple Custom CSS values, create a real file and load it instead of Simple Custom CSS style. Important to know ## Put Simple Custom CSS option to a real file PHP5 Required. 1. Download, unzip and upload to your WordPress plugins directory 2. Activate the plugin within you WordPress Administration Backend 3. That's It ! More help installing Plugins Frequently Asked Questions ## By default the css file is written in your WordPress Content dir in the folder cache/scss/ . The files names are like 10-scss.css where 10 is the blog id. You can use the filter 'SCSSCache/foldername' and change the folder name. Check if the folder wp-content/cache/scss is here and writable. If not so, then create it. Changelog ## 1.0.0 9 April 2016 Ini

Releases

2 releases.

Tag
Published
1.0.1 latest
Oct 5, 2016 10 years ago
Apr 9, 2016 10 years ago

These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.

A grade

Security

Simple Custom CSS Cache 1.0.1 · audited by WP Registry

No security issues found.

Audited release
1.0.1
Findings
none
Worst severity
—
Content hash
2f1c4c7fc9ca2602193a167e…

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.