collective.skinny
An example implementation of a separate, public-facing skin as discussed at:
http://danielnouri.org/blog/devel/zope/plone-3-theming-for-mortals-part2.html
http://danielnouri.org/blog/devel/zope/plone-3-theming-for-mortals.html
http://weblion.psu.edu/news/viewlets-barriers-for-plone-newbies
Look at the package’s configure.zcml file for instructions on how to activate the public skin to actually see it.
You can use this package either as a template to copy and modify, or use it as it is and extend within your own package.
If you decide to extend this with your own package, which is probably the cleaner way of doing it, You can start out by overriding the index.html view, and thus the main.Main class in your overrides.zcml file, using directives as you find them in them in this package’s configure.zcml. You can then subclass the main.Main browser view and code away.
Changelog
0.2 - 2009-01-22
Instead of displaying the login form when an Unauthorized error is raised, display a 404 page in the public skin. This will make pages like /edit invisible. [nouri]
0.1 - 2009-01-22
Initial release [nouri]
Metadata
Release files for collective.skinny 0.2
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 |
|---|---|---|---|---|
| collective.skinny-0.2.tar.gz | 6.0 kB | Without provenance | Details for collective.skinny-0.2.tar.gz |
Release files / collective.skinny-0.2.tar.gz
| Download URL | collective.skinny-0.2.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
16cb9181416498f66883f6d26ff534226b6c04b03a9195512bbdc4f12737fb0f
|
|
BLAKE2b-256 checksum How to use checksums |
dc51ac3c72ac85069c82ffa9673299f976df4c23f1cda10fc2f01ce7380cdb09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.skinny 0.2
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.