This project has been archived by its maintainers, and is no longer receiving any updates.
Back Reference Field and Widget for Archetypes
Usage
Use it like a field is supposed to be used. Its almost similar to ReferenceField, ReferenceWidget/ ReferenceBrowserWidget.
Archetypes Referenceable API offers already back-references, the field/widget allows to visualize them like forward references. The relationship (name) of the reference must be the same as on the forward reference field given.
Usage for ArchGenXML/ UML
in your UML tool create a relation between 2 classes and make the ‘to’ end of i the assocation navigable (such a beast is provided in the sample dir).
add the tagged value backreferences_support to your model and set it to 1.
invoke ArchGenXML,
restart your zope and try it out
BackReferenceField for Archetypes.
This is the counterpart to the ReferenceField. When you have a relation that is managed by a ReferenceField, you can define at the reference’s target object a BackReferenceField and a BackReferenceWidget, that alows you to navigate back and also add references to the same relation from the other side
Installation:
You have to install it via portal_setup because it has skin elements (the widget templates).
Comaptibility
Works with Plone 3 and 4.
Licence
copyright 2004-2009 BlueDynamics Alliance, Austria
GNU General Public License Version 2 or later
Contributors
Kai Diefenbach - make it ready for Plone 3
Jens Klein - remove old school Install, use GS profile instead, eggified.
3 maintainers
Metadata
3 maintainers
Release files for Products.ATBackRef 2.1
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 |
|---|---|---|---|---|
| Products.ATBackRef-2.1.tar.gz | 12.0 kB | Without provenance | Details for Products.ATBackRef-2.1.tar.gz |
Release files / Products.ATBackRef-2.1.tar.gz
| Download URL | Products.ATBackRef-2.1.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e25765321ecdc385764e11645cd0de06225935da0d701bfe53157b3471e0794e
|
|
BLAKE2b-256 checksum How to use checksums |
54678cab981fbc1a4f6a7204210115e95742ddda56da816cf9a0763084c1cc44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.ATBackRef 2.1
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.
