collective.bbcodesnippets provides pervasive, generic and extensible BBCode Markup integration for Plone.
Functionality
collective.bbcodesnippets replaces BBCode in the whole generated HTML output. BBCode snippets can be placed everywhere in the site.
At transform time at the end of the chain, before or after Diazo (configurable), the output is parsed and all BBCode will be replaced.
The BBCode parser only replaces configured BBCode snippets. At the control panel all registered BBCodes are listed to be activated. By default all codes are inactive.
This package utilizes the excellent bbcode package from Dan Watson to parse and replace. We register all default formatters as named utilities which are used as factories for the formatter using the Zope Component Architecture (ZCA). Custom parsers can be provided by registering an own named utility. Before parsing at transform time new Parser is created using the configured adapters only.
Further features:
The Plone toolbar got a new menu to copy BBCode templates for the active BBCodes.
TinyMCE got a new menu to insert BBCode templates.
There is a demo page with all activated BBCodes at the portal root under @@bbcodesnippets-demo.
A boolean index has_bbcodes got added to the portal_catalog. Content with active or inactive BBCcodes in any of their text or richtext Dexterity schema fields are indexed True.
Installation
Install collective.bbcodesnippets by adding it to your buildout:
[buildout]
...
eggs =
collective.bbcodesnippets
and then running buildout.
Afterwards (re)start Plone, go to the controlpanel and install the addon.
Then there is a conrol-panel to control the allowed BBcodes.
Source Code
The sources are in a GIT DVCS with its main branches at github.
We’d be happy to see many forks and pull-requests to make collective.bbcodesnippets even better.
Contributors
Michael Graf, FH St.Pölten - Idea and Use Case
Thanks to St. Pölten University of Applied Sciences for initial funding.
3 maintainers
Metadata
3 maintainers
Release files for collective.bbcodesnippets 2.0.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_bbcodesnippets-2.0.0.tar.gz | 37.1 kB | With provenance | Details for collective_bbcodesnippets-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective_bbcodesnippets-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for collective_bbcodesnippets-2.0.0-py3-none-any.whl |
Total release size: 68.3 kB
Release files / collective_bbcodesnippets-2.0.0.tar.gz
| Download URL | collective_bbcodesnippets-2.0.0.tar.gz |
|---|---|
| Size | 37.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a83cb73451455ef2d34ba17b38ca1e190463d16309ada1a77df7f9366f721559
|
|
BLAKE2b-256 checksum How to use checksums |
c3b6f978a1a956ee4444a68212bd905c9675792cc565e14700724f602bca654e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 7, 2026.
Transparency logRelease files / collective_bbcodesnippets-2.0.0-py3-none-any.whl
| Download URL | collective_bbcodesnippets-2.0.0-py3-none-any.whl |
|---|---|
| Size | 31.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f104a8d958973e608d3765eadf4e06f34f38533444a13803c135bba3ab01d99
|
|
BLAKE2b-256 checksum How to use checksums |
78f36eeb40f159d9b493c73163a44f52c49ab1859d2ad22f4dc8668fcc700c8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 7, 2026.
Transparency logSecurity for collective.bbcodesnippets 2.0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for collective_bbcodesnippets-2.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 7, 2026.
Transparency logA 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.
