How to use
The BLOB support in Plone is amazing for a lot of reasons.
However Plone will raise errors when you visit a file content that use BLOB support without also having the BLOB file.
For developers this can be a little bit boring. It’s quite common to copy a production Data.fs for developing using production data, but you don’t always want to copy all blobs.
This product monkey-patches parts of Plone, so that visiting objects that store content in the blob storage without having the BLOB available will not lead to errors. Instead a file only containing the string “File created by experimental.gracefulblobmissing.” is created in the place where the blob-file should be.
Requirements
This product has been tested on:
Plone 5.1
Plone 5.2
For Plone 4 / Archetypes compatibility stay below version 2.0. For Plone 3 compatiblity stay on version 0.3.0 or lower.
Warning
This is designed only for development/staging environment. Do not use in production if you are not 100% sure of what you are doing!
Credits
Developed with the support of S. Anna Hospital, Ferrara; S. Anna Hospital supports the PloneGov initiative.
Changelog
2.0 (2023-08-03)
Remove Archetypes compatibility code. [thet]
1.0 (2022-03-11)
Add support for relstorage. [pbauer]
Create dummy image blobs on the fly. [ale-rt, mauritsvanrees]
0.5.0 (2018-12-14)
Only patch plone.app.blob and Products.ATContentTypes if they are installed. This makes this package compatible with a Archetypes-free Plone. [gforcada]
0.4.0 (2015-04-29)
modify patch to not touch every file but only create file with a string in it when it is missing [pbauer]
patch ZEO to create missing blob-files [pbauer]
add logging-message when creating a missing blog-file [pbauer]
fixed errors when reindexing SearchbleText index [keul]
Added a patch for ZODB egg that Create the blob folder path and create (touch) an empty file for each blob file if it’s missing. [sneridagh]
0.3.0 (2011-09-30)
fixed dependency on collective.monkeypatcher >= 1.0 [keul]
pached also getScale method, used by some atct views [keul]
0.2.0 (2011-06-06)
fixed dependencies [keul]
direct access to files with missing blobs now redirect to the view with a warning [keul]
0.1.0 (2010-11-19)
initial release
Metadata
Release files for experimental.gracefulblobmissing 2.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 |
|---|---|---|---|---|
| experimental.gracefulblobmissing-2.0.tar.gz | 16.5 kB | Without provenance | Details for experimental.gracefulblobmissing-2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| experimental.gracefulblobmissing-2.0-py3-none-any.whl | Python 3 | none | any | Details for experimental.gracefulblobmissing-2.0-py3-none-any.whl |
Total release size: 25.1 kB
Release files / experimental.gracefulblobmissing-2.0.tar.gz
| Download URL | experimental.gracefulblobmissing-2.0.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
736af972ebc86f7075d6e6019c9e022bf44d94e19a047a75f676e6ff3a66c33b
|
|
BLAKE2b-256 checksum How to use checksums |
5512a1447529efb54f74bb84bf430551fa2a41ca92588215938c975248fa31be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / experimental.gracefulblobmissing-2.0-py3-none-any.whl
| Download URL | experimental.gracefulblobmissing-2.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fdc5dae0211c3747382bbb8f99a4597ef0ee8f8f75910d0816d2582134c59ace
|
|
BLAKE2b-256 checksum How to use checksums |
aed7e84d1f6af29486a27ce8b7cdc36e8c9fa1ddbdbd008a9c9c378565f1dd22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for experimental.gracefulblobmissing 2.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.