This release is a pre-release and may not be stable for production use.
beyondskins.ploneday.site2010
Overview
This product is a installable Plone 3.x, 4.x Theme developed by Simples Consultoria.
Requirements
Plone 4.0 (http://plone.org/products/plone)
Plone 3.2.x (http://plone.org/products/plone)
Plone 3.1.x (http://plone.org/products/plone)
Installation
To use this theme, on a buildout based installation:
1. Unpack beyondskins.ploneday.site2010 package to src/ folder of your buildout 2. Edit your buildout.cfg and add the following information:
[buildout] ... eggs = beyondskins.ploneday.site2010 [instance] zcml = ... beyondskins.ploneday.site2010The last line tells buildout to generate a zcml snippet that tells Zope to configure beyondskins.ploneday.site2010.
If another package depends on the beyondskins.ploneday.site2010 egg or includes its zcml directly you do not need to specify anything in the buildout configuration: buildout will detect this automatically.
After updating the configuration you need to run the ‘’bin/buildout’’, which will take care of updating your system.
Go to the ‘Site Setup’ page in the Plone interface and click on the ‘Add/Remove Products’ link.
Choose the product (check its checkbox) and click the ‘Install’ button.
Uninstall – This can be done from the same management screen, but only if you installed it from the quick installer.
Note: You may have to empty your browser cache to see the effects of the product installation.
Browsers and OS’s
Internet Explorer 8.0 (WinXP/Vista)
Internet Explorer 7.0 (WinXP/Vista)
Firefox 3 (WinXP/Vista/MacOSX)
Safari 4 (WinXP/Vista/MacOSX)
Safari 3 (WinXP/Vista/MacOSX)
Credits
Simples Consultoria (products at simplesconsultoria dot com dot br) - Design / Packaging
Changelog
trunk (2010-04-05)
xxx [Simples Consultoria]
1.01 - (2010-03-26)
Compativel com plone 3 e 4 [tamosauskas]
1.0 - (2010-03-26)
Release inicial [tamosauskas]
Metadata
Release files for beyondskins.ploneday.site2010 1.0.1dev-r0
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 |
|---|---|---|---|---|
| beyondskins.ploneday.site2010-1.0.1dev-r0.tar.gz | 438.5 kB | Without provenance | Details for beyondskins.ploneday.site2010-1.0.1dev-r0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| beyondskins.ploneday.site2010-1.0.1dev_r0-py2.4.egg | Legacy Egg format | - | - | Details for beyondskins.ploneday.site2010-1.0.1dev_r0-py2.4.egg |
Total release size: 892.9 kB
Release files / beyondskins.ploneday.site2010-1.0.1dev-r0.tar.gz
| Download URL | beyondskins.ploneday.site2010-1.0.1dev-r0.tar.gz |
|---|---|
| Size | 438.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d010ed54bba6945a1eb0573d8680c160f7c8d3e979c15c32a417cc9bc4461097
|
|
BLAKE2b-256 checksum How to use checksums |
fb36fc11c87351583f7ecbe419ae838e9edd19f2d6bf08d9cb4446762eaa463c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / beyondskins.ploneday.site2010-1.0.1dev_r0-py2.4.egg
| Download URL | beyondskins.ploneday.site2010-1.0.1dev_r0-py2.4.egg |
|---|---|
| Size | 454.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
2d8f98fc4746fd048e73ad889f908938997233733c00af2bb49e3d9a4bc1e6bd
|
|
BLAKE2b-256 checksum How to use checksums |
3798d75147355d0dca80bfe3052ce5eaf288d0d73ead22e5828fdb5fe565e043
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for beyondskins.ploneday.site2010 1.0.1dev-r0
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.