Introduction
Changelog
1.0 - (9 June 2008)
Use /view for e.g. images/files (using view_url from plone_context_state). [maurits]
Place references without a workflow in the list of visible items. [maurits]
Do not show portlet for anonymous. [maurits]
Only report relations ‘isReferencing’ (from plone.app.linkintegrity) and ‘relatesTo’ (relatedItems) and not for example ‘translationOf’ from LinguaPlone. [maurits]
Added French and Spanish locales. [maurits]
Removed the edit/add forms. [maurits]
Split the references into (in)visible links in the text and related items. [maurits]
Show review state title and use state coloring. [maurits]
Only display when there are references. [maurits]
Initial release
5 maintainers
Metadata
5 maintainers
Release files for collective.portlet.references 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 |
|---|---|---|---|---|
| collective.portlet.references-1.0.tar.gz | 13.8 kB | Without provenance | Details for collective.portlet.references-1.0.tar.gz |
Release files / collective.portlet.references-1.0.tar.gz
| Download URL | collective.portlet.references-1.0.tar.gz |
|---|---|
| Size | 13.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d4351d11068356b9a86d6221131ad1df3b6008da3263e4e39871644172e50a4
|
|
BLAKE2b-256 checksum How to use checksums |
4ea027aa1393ec788931680c4af38346b0b1917973470e1da57006513a197e7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.portlet.references 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.
