This release is a pre-release and may not be stable for production use.
Introduction
This package is developed by Wildcard Corp. to help remove nasty local persistent utilities that won’t go away and can destroy your instance when you try to remove a product that registered one.
Features
remove adapters
remove subscribers
remove provided interfaces
remove provided interfaces across the entire site - useful for removing collective.flowplayer
Just append ‘/@@fix-persistent-utilities’ onto your plone site root or the root of zope(for gsm) and browse through all your registered utilities on your site and remove things at will.
By default, the tools prevents you from removing certain registrations; however, you can enter “expert mode” and remove whatever you want.
WARNING!!!
You can really screw up things if you do this wrong so use with extreme care and backup your instance before you use it.
I will not take responsibility if you misuse this tool…
Advice
Do not include this product as part of your normal set of products. Only install this product on debug zope clients.
This product should allow you to remove things from products that are no longer installed on the system; although, if you experience problems removing things, make sure to add those eggs to the system again.
Automatically generate missing classes
If you no longer have a product installed that you’re trying to remove, FPU can dynamically create the fake class for you.
this is dangerous if you don’t delete fake class
To enable, specify this environment variable:
FPU_GENERATE_MISSING_CLASSES true
Changelog
1.1b7 (2013-02-06)
need to specify environment variable to use the auto class generator. [vangheem]
1.1b5 (2012-05-29)
Also remove utilities from the site root if five has added them there. This will allow you to fully remove LinguaPlone. [do3cc]
1.1b4 ~ 2011-11-24
add a log (INFO) on each module missing. [toutpt]
support Plone3 using transation.abort instead of doom [toutpt]
1.1b3 ~ 2011-11-06
attempt to prevent saving generated objects to database unless you’re actually removing it.
1.1b2 ~ 2011-07-11
dynamically create missing classes so you can potentially remove classes from products that are no longer installed on the instance.
1.1b1 2011-06-02
provide ability to remove provided interfaces now also.
clean up
1.0a3 2010-10-22
works on root of zope now also
1.0a2 2010-10-22
fix case where object may not have a _p_oid
1.0a1 2010-08-25
Initial release
6 maintainers
Metadata
6 maintainers
Release files for wildcard.fixpersistentutilities 1.1b7
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 | |
|---|---|---|---|---|
| wildcard.fixpersistentutilities-1.1b7.zip | 26.4 kB | Without provenance | Details |
Release files / wildcard.fixpersistentutilities-1.1b7.zip
| Download URL | wildcard.fixpersistentutilities-1.1b7.zip |
|---|---|
| Size | 26.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
758289ecf67730612fcee82cc0e5323071305d3e5257c75a9291053113283de9
|
|
BLAKE2b-256 checksum How to use checksums |
335b3f83a2206495af65dcef508322c460ce321ddb3cb0063c66b29ceaa58f0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wildcard.fixpersistentutilities 1.1b7
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.
