sc.base.hotsites
Overview
Allows, via p4a.subtyper, the user tranforms a folder in a hot site.
What is a Hot Site here ?
When you set a folder as a hot site :
Removes viewlets around the content: footer, header and top
Block all portlets (from parents, from group and from content type), you can re-enable manually, if you want
Enable a new skin, via access rule, so you can customize the look’n’feel of your Hot Site
Enable a local workflow, defaults to one-state workflow, to simplify the management of Hot Site
Limits the addable content types in the Hot Site folder, you can configure the content types
Use a content as a template to Hot Site index
Optionally, create a page (document) as accessibility content, useful when the hot sites is a Flash content
Options you can setup
In Site Setup, access the menu Hot Sites
Addable content type on Hot Sites folder
Skin name used in the Hot Sites folder
Default view id, that will be setted in the Hot Sites folder
Default view path, a content template that will be copied and used as the default view of Hot Sites folder
Workflow id, workflow used in the Hot Site, will be setted using the Placeful Workflow, defaults to one-state workflow
Use accessibility content, if selected will be created a page (document) as a alternate (accessibility) view, you will must provide the link to this content. It’s useful when the default view is a Flash content.
Requirements
Plone 3.2.x (http://plone.org/products/plone)
Installation
To enable this product,on a buildout based installation:
Edit your buildout.cfg and add sc.base.hotsites to the list of eggs to install
[buildout] ... eggs = sc.base.hotsitesTell the plone.recipe.zope2instance recipe to install a ZCML slug:
[instance] ... zcml = ... sc.base.hotsites
If another package depends on the sc.base.hotsites 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 and save your resource registries in order to see the effects of the product installation.
Sponsoring
Development of this product was sponsored by Simples Consultoria.
Credits
Simples Consultoria (products at simplesconsultoria dot com dot br) - Implementation
Changelog
1.0 - 2009/12/29
Initial release [lucmult]
Metadata
Release files for sc.base.hotsites 1.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 |
|---|---|---|---|---|
| sc.base.hotsites-1.0.tar.gz | 20.4 kB | Without provenance | Details for sc.base.hotsites-1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sc.base.hotsites-1.0-py2.4.egg | Legacy Egg format | - | - | Details for sc.base.hotsites-1.0-py2.4.egg |
Total release size: 52.9 kB
Release files / sc.base.hotsites-1.0.tar.gz
| Download URL | sc.base.hotsites-1.0.tar.gz |
|---|---|
| Size | 20.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71be03472cf8221c437cfa79a601a3c7ac5835617a2de285b4490003a6879057
|
|
BLAKE2b-256 checksum How to use checksums |
731f1334ece56aa8cf2ecb091b27fcbe6fbdf47b666678cd2b17df0af2e05054
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / sc.base.hotsites-1.0-py2.4.egg
| Download URL | sc.base.hotsites-1.0-py2.4.egg |
|---|---|
| Size | 32.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
abbc344399ad4d3f66ba225bb91e0b04ae85db64aaa9b70e52678c2d6e4b4d0b
|
|
BLAKE2b-256 checksum How to use checksums |
6b4ece4e7a963d52e2899c60d77c987e9e0d8ffb5819f9a7dbb47d6b54f505fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sc.base.hotsites 1.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.