Introduction
Resource Registries creates a unique URL each time a CSS or JS file is modified providing a way create unique files without having to rename the original ones.
It also has a feature to concatenate several CSS or JS files to less files to the user. But with the way this concatenation is done sometimes the files that can be safely concatenated are not, because the tool just tries to concatenate one file with the previous file. For example:
We have 4 files registered in this order: a.css, b.css, c.css and d.css. If a.css, b.css and d.css are compatible to be concatenated but c.css is not, Resource Registries will create 3 files: ab.css, c.css and d.css.
This product, patches the way those concatenated files are created to check all previously concatenated files and concatenate the file there. This way, in the previous example, the patch will create 2 files: abd.css and d.css
Installing
Add this product to your buildout, re-run buildout and restart your instance, the patch will be applied automatically.
To remove this feature, just remove the product from your buildout, re-run it and restart the instance.
The product doesn’t create an install profile entry in the Products Control Panel and doesn’t save anything on the database.
Changelog
1.0 (2015-03-02)
Initial implementation [erral]
Metadata
Release files for cs.plonepatches.resourceregistries 1.0
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 |
|---|---|---|---|---|
| cs.plonepatches.resourceregistries-1.0.zip | 27.4 kB | Without provenance | Details for cs.plonepatches.resourceregistries-1.0.zip |
Release files / cs.plonepatches.resourceregistries-1.0.zip
| Download URL | cs.plonepatches.resourceregistries-1.0.zip |
|---|---|
| Size | 27.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0054f9e598d63f1560282b66fdc08254d2bc48e29fce2db6f373c2f00e3f6b93
|
|
BLAKE2b-256 checksum How to use checksums |
302eaa071a6cb5e932dd99e9cb40355c55ff57148cc023c7fdfe5af618fdb60d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cs.plonepatches.resourceregistries 1.0
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.