silva.core.xml
silva.core.xml provides the basic components required for the Silva XML import and export feature.
You can find more documentation on how to use those components in the Developer documentation.
Code repository
You can find the code of this extension in Git: https://github.com/silvacms/silva.core.xml
Changes
3.0.1 (2013/05/23)
Refactor import code defining methods on the correct classes. This removes lot of workflow managing methods they were handled on the wrong class, adding those methods on classes for content who didn’t even had a workflow.
Support for missing workflow and metadata information during import.
Support for skipping content during import.
Fix various bugs regarding workflow and metadata import.
3.0 (2013/03/06)
Initial release.
Metadata
Release files for silva.core.xml 3.0.1
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 |
|---|---|---|---|---|
| silva.core.xml-3.0.1.tar.gz | 12.4 kB | Without provenance | Details for silva.core.xml-3.0.1.tar.gz |
Release files / silva.core.xml-3.0.1.tar.gz
| Download URL | silva.core.xml-3.0.1.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34e1f5f8914e63600ee9af164d5b5dbdffc5641e3006a6ce5c2f07e6bb10ccf7
|
|
BLAKE2b-256 checksum How to use checksums |
a24b6d2456d8001cd9ac5e140dc520cbb81114248db82c480dd4ed63ba3cb531
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for silva.core.xml 3.0.1
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.