collective.volto.blocksfield
Custom z3c.form field that allows to use Volto blocks.
This field can replace RichText fields in your custom content-types.
Features
store a json object with all blocks informations (data and order)
restapi serializer/deserializer to manage internal links
registered custom indexer for collective.dexteritytextindexer (if installed)
How to use
Import it and use as a normal field:
from collective.volto.blocksfield.field import BlocksField
class IMySchema(Interface):
my_field = BlocksField(
title="A field with blocks",
)
Upgrade to 2.2.0
From 2.2.0 version, objects with BlocksField are marked with a marker interface and blocks are indexed in block_types index.
To update contents already created in the site, you need to create an updgrade-step or call “@@mark_contents_and_reindex” view.
Installation
Install collective.volto.blocksfield by adding it to your buildout:
[buildout]
...
eggs =
collective.volto.blocksfield
and then running bin/buildout
You don’t need to install it.
TODO
Tests
Contribute
License
The project is licensed under the GPLv2.
2.2.0 (2024-12-03)
Add marker interface to objects that have at least one BlockField in their schema. [cekk]
Add block_types indexer customization for contents with IBlocksFieldEnabled interface to allow index also these blocks. [cekk]
Make package installable: on install, mark already created contents as IBlocksFieldEnabled and reindex them. [cekk]
2.1.0 (2024-08-09)
Add serializers and deserializer for slate blocks. [cekk]
Add indexer for slate blocks. [cekk]
2.0.0 (2023-07-03)
Drop support for Plone 5.2 and collective.dexteritytextindexer; in Plone6 we use core functions in plone.app.dexterity.textindexer [lucabel]
1.0.3 (2022-05-31)
Fix required python version. [cekk]
1.0.2 (2022-05-25)
add check if value is a dict in SearchableText indexer. [eikichi18]
1.0.1 (2021-03-25)
Register standard blocks serializers/deserializer for IDexterityContent. Otherwise they don’t work. [cekk]
1.0.0 (2021-02-24)
Initial release. [cekk]
Metadata
Release files for collective.volto.blocksfield 2.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 |
|---|---|---|---|---|
| collective.volto.blocksfield-2.2.0.tar.gz | 25.3 kB | Without provenance | Details for collective.volto.blocksfield-2.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective.volto.blocksfield-2.2.0-py3-none-any.whl | Python 3 | none | any | Details for collective.volto.blocksfield-2.2.0-py3-none-any.whl |
Total release size: 53.5 kB
Release files / collective.volto.blocksfield-2.2.0.tar.gz
| Download URL | collective.volto.blocksfield-2.2.0.tar.gz |
|---|---|
| Size | 25.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76cc12cb31adbeaf75a2154de2f9d4439527ca88a6555780a966a01f59365b91
|
|
BLAKE2b-256 checksum How to use checksums |
26d987b051c625427883c7a40e56dc45fa17f550381e6f7cada3342a027ce9bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / collective.volto.blocksfield-2.2.0-py3-none-any.whl
| Download URL | collective.volto.blocksfield-2.2.0-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7e428bb37334bee9cc17d81a488a6a376f54b0d51faee06d95c9bc23093ebe3
|
|
BLAKE2b-256 checksum How to use checksums |
7f003303370f1b193a8aa1ec5ae582ff640d6eddc504e7fb42c22fdc046001f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for collective.volto.blocksfield 2.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.