This release is a pre-release and may not be stable for production use.
Right now this package provides 2 widgets, FileField and ImageField. These widgets support file uploading with server side caching. That means that if some other field in the form fails validation, the user wont have to upload the file again. Instead they get the information of the file they included or a thumbnail of the image if it’s an ImageField. An option to remove the file from the form is given too.
The ImageField has a thumbnail preview and allows size validation and automatic resizing when dimensions get past certain values (this isn’t enabled by default).
If Lightbox is installed (optional), the full size images will be displayed with it (non popup image viewer). Also an animation removing the file attached to the form will be shown if Scriptculous is installed (optional). The server side caching is done using the TemporaryFile class from the official Python tempfile module. It’s a secure way to store files on a platform independent way. The files are cleared when they are not used anymore.
The widgets need a controller that will be the file server for the download links and images previews. You can import the controllers from file_fields.controllers (PicServer and FileServer) and specify the url on the widget constructors (file_server_url, image_server_url)
The easiest and recommended way is enabling the extension your dev.cfg, prod.cfg or app.cfg adding:
file_field_server.on = True
1 maintainer
Metadata
1 maintainer
Release files for FileFields 0.1a0.dev-r301
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| FileFields-0.1a0.dev_r301-py2.4.egg | Legacy Egg format | - | - | Details |
Release files / FileFields-0.1a0.dev_r301-py2.4.egg
| Download URL | FileFields-0.1a0.dev_r301-py2.4.egg |
|---|---|
| Size | 21.9 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
ff485e36db4278f56487a6e8f7cfd8c3aa26a80646cfc3f4b92e5f587019b9f7
|
|
BLAKE2b-256 checksum How to use checksums |
f7f2ef55ae4ce79b25bdf74d0d638f99c293273b6b2a6b3c2958539e64008e48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for FileFields 0.1a0.dev-r301
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.
