Introduction
This Plone product allows some cache tuning for your site. Currently it only allows username replacment, but we might add some more features in the future.
Username replacement
If you enable this option, you can cache the whole pages and an Ajax request will replace the username in the page in order to reduce the load.
If you use a custom theme, you can specify the query used to select the HTML node containing the username. This query is written in the classic CSS format.
Extra libraries
The Javascript cookie setting is done using jquery.cookie.js, written by Klaus Hartl. The project is hosted at https://github.com/carhartl/jquery-cookie.
Changelog
0.4 (2012-08-24)
Return userid when full name is empty. [vincent]
Cleaned sources - added buildout for tests. [maurits]
0.3 (2012-08-24)
Splitted the zestcachetuning.js file so we have one version for authenticated users and one for anonymous. [vincent]
0.2 (2012-08-23)
Store a cookie with the username so we don’t have to make an Ajax call everytime. [vincent]
Fixed an error happening with anonymous users. [vincent]
0.1 (2012-01-12)
Initial release [vincent]
4 maintainers
Metadata
4 maintainers
Release files for zest.cachetuning 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zest.cachetuning-0.4.zip | 31.4 kB | Without provenance | Details for zest.cachetuning-0.4.zip |
Release files / zest.cachetuning-0.4.zip
| Download URL | zest.cachetuning-0.4.zip |
|---|---|
| Size | 31.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9690cf1b230d6599f934e6524e6f81d0abbf092216f09d8f3839e39f79ed710
|
|
BLAKE2b-256 checksum How to use checksums |
13144efc40e06cf17c34f480c127e12851fbe2dc8929706fc0fe044783c09abf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zest.cachetuning 0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
