CPskin related content types
Contributors
Laurent Lasudry, laurent.lasudry@affinitic.be
Changelog
1.0.13 (2021-05-17)
Build more specific procedure interface [boulch]
Remove useless index because template si specifying in zcml file [boulch]
Add add_view Procedure expression [boulch]
1.0.12 (2021-05-04)
e_guichet field is printing like a link in template [boulch]
Add new procedure validator [boulch]
e_guichet field always available (even if imio.behavior.teleservice is installed) [boulch]
Fix / update buildout & dependencies [laulaz]
1.0.11 (2021-01-06)
Remove lead-image out of procedure template [boulch]
1.0.10 (2020-08-12)
[WEB-3405] : Don’t forget upgrade step to (re)change view on existing objects [boulch]
1.0.9 (2020-08-12)
[WEB-3405] : First step :Change procedure default view. [boulch]
1.0.8 (2020-07-08)
[WEB-3381] : Fix procedure contenttypes view when imio.behavior.teleservices isn’t install. [boulch]
1.0.7 (2020-07-06)
Override edit and add View : When ITsProcedure behavior is there, we want to hide e_guichet basic text field. [boulch]
upgradesteps : To apply new default procedure template. [boulch]
Procedure template : Change “a href” link to e-guichet by “button” to e-guichet. [boulch]
Procedure template : (Add Leadimage fancybox, add RichText) [boulch]
1.0.6 (2020-07-01)
Add custom “procedure_view” for content type “procedure”. [boulch, laulaz]
1.0.5 (2020-01-14)
Don’t try to migrate related items in NavigationRoot and don’t try to remove them. [boulch]
1.0.4 (2020-01-10)
Refactoring setuphandlers. Remove old procedure at end of the process. Better manage for demarche (old_procedure) relatedItems [boulch]
1.0.3 (2020-01-07)
Fix a bug when we get current wf state. We now use updateRoleMappingsFor to get good permissions and good roles in the current state. (products and procedure) [boulch]
Add “procedure” content type + step to migrate old “demarche” document to procedure : WEBOTT-19 [boulch]
1.0.2 (2019-03-18)
Add icon for product content type : WEBOTT-10 [laulaz]
Add Fancybox overlay on product image : WEBOTT-10 [laulaz]
1.0.1 (2019-03-18)
Minor improvements (leadimage size & more css classes) : WEBOTT-10 [laulaz]
1.0 (2019-02-05)
Initial release. [laulaz]
Metadata
Release files for cpskin.contenttypes 1.0.13
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 | |
|---|---|---|---|---|
| cpskin.contenttypes-1.0.13.tar.gz | 14.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cpskin.contenttypes-1.0.13-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 39.0 kB
Release files / cpskin.contenttypes-1.0.13.tar.gz
| Download URL | cpskin.contenttypes-1.0.13.tar.gz |
|---|---|
| Size | 14.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe27e844aa91d076f0eaee413bc0fa1ff3cc958cc5fef3f471a4257169ab46c6
|
|
BLAKE2b-256 checksum How to use checksums |
daba3a8f57ed58380ca837e0ae98f5fc0c1dd32365b2c412db863d595de3c863
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/44.1.1 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/2.7.17
|
Release files / cpskin.contenttypes-1.0.13-py2-none-any.whl
| Download URL | cpskin.contenttypes-1.0.13-py2-none-any.whl |
|---|---|
| Size | 24.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
9ce49a1328d3a492fbeccfd42b401b36a656b4ff67a9ef726b72a9aa1f8c198b
|
|
BLAKE2b-256 checksum How to use checksums |
6d48cf037496c667c12f46631291538360eec0049cebdf7914277b74c6575622
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/44.1.1 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/2.7.17
|
Security for cpskin.contenttypes 1.0.13
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.