Introduction
A facade storage for Archetypes which delegates to a Plone site’s Memberdata Tool for storing content item field values as memberdata properties.
This heavily relies on name magic. It is assumed that the correponding member and content instances have corresponding ids. Correspondence is established with the help of Products.PlonePAS.utils.[de]cleanId - the same way Plone 4 uses to keep track of member folders.
The use case driving its development has been to support custom Archetypes-based content types which can be used as home folders for members and mirroring some of the member properties. That way, people can change member properties by editing their home folder settings.
archetypes.memberdata is used in production on http://www.incf.org.
Usage
In your Archetypes schema definition you can use the MemberPropertyField instead of a regular StringField to get and set the field’s value in a corresponding member property. Per default, a property with the same name as the field is used unless the member_property_id is set to point to a different property.
For other field types one can use MemberdataStorage as well as long as the data type can be handled by the member data tool.
Changelog
1.1 (2011-03-29)
Don’t break if email login is enabled [raphael]
Extend test coverage to also check for member property changes being picked up in “content space” [robin].
1.0 - 2009-04-03
Adding test suite [raphael].
Adding MemberpropertyField for convenience [raphael].
Breaking this out of ResearchCommunitySite to make it more accessible (from r15354 - yes, no changes in three years) [raphael].
1 maintainer
Metadata
1 maintainer
Release files for archetypes.memberdatastorage 1.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 |
|---|---|---|---|---|
| archetypes.memberdatastorage-1.1.tar.gz | 5.9 kB | Without provenance | Details for archetypes.memberdatastorage-1.1.tar.gz |
Release files / archetypes.memberdatastorage-1.1.tar.gz
| Download URL | archetypes.memberdatastorage-1.1.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ba5afb6125c4b2fc7a44b9f6972548491db96099bee756812eaa4ab3bc75eb2
|
|
BLAKE2b-256 checksum How to use checksums |
f251c3507dbda6b644f60094bd467a809adea106bda8127b4cc3005625203fb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for archetypes.memberdatastorage 1.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.
