Introduction
plone.app.changeownership as it sounds is a plone package to change objects ownership.
Problem
There is no way in plone to transfer ownership of all objects owned by an user to a new user. To delete a plone member in such case is not an option.
Solution
plone.app.changeownership makes easy to transfer ownership from one ore more members to a new member. It also can change content metadata, like Creators field.
Install
See docs/INSTALL.txt for a buildout configuration.
You have to install the package from quickinstaller or setup_tool. You will get a configlet in the plone control panel named “Change Ownership”
Changelog
0.4 (2012-09-20)
Fix permissions for Plone 4 [fdelia]
0.3 (2011-03-07)
Added MANIFEST.in [WouterVH]
Added Dutch-translation [WouterVH]
Added z3c.autoinclude support [keul]
Added italian translation [keul]
0.2 (2010-02-02)
Added check to support instances without a membersfolder [jaroel]
0.1 (2008-02-01)
Merged matth’s branch that adds:
Filter by path
Dry run option
Sorting of usernames
Display userid as well as full name
Initial release
7 maintainers
Metadata
7 maintainers
Release files for plone.app.changeownership 0.4
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 |
|---|---|---|---|---|
| plone.app.changeownership-0.4.zip | 25.1 kB | Without provenance | Details for plone.app.changeownership-0.4.zip |
Release files / plone.app.changeownership-0.4.zip
| Download URL | plone.app.changeownership-0.4.zip |
|---|---|
| Size | 25.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b1fb7130f7912d5d0d4e2514941cde8a7ed7f8a8f7067fd6b8a32c3c20cab80
|
|
BLAKE2b-256 checksum How to use checksums |
dcde261a554cfb61a4906b579abb92f2360fb5a1e762c862a831117017bbaafd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.app.changeownership 0.4
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.
