Introduction
This package helps to create custom portal logo in Plone, using new configlet, custom css and images. It allows user to construct logo from multiple items such as text or images.
Installing
This package requires Plone 3.0 or later.
Installing without buildout
Install this package in either your system path packages or in the lib/python directory of your Zope instance. You can do this using either easy_install or via the setup.py script.
After installing the package it needs to be registered in your Zope instance. This can be done by putting a collective.multilogo-configure.zcml file in the etc/package-includes directory with this content:
<include package="collective.multilogo" />
or, alternatively, you can add that line to the configure.zcml in a package or Product that is already registered.
Installing with buildout
If you are using buildout to manage your instance installing collective.multilogo is even simpler. You can install collective.multilogo by adding it to the eggs line for your instance:
[instance] eggs = collective.multilogo zcml = collective.multilogo
The last line tells buildout to generate a zcml snippet that tells Zope to configure collective.multilogo.
If another package depends on the collective.multilogo 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.
Usage
For example we want to create custom logo for portal DMS4U from server family: “DMS4U | CMS4U | ERP4U | CHAT4U” pointing to particular sites http://dms4u.cz, http://cms4u.cz, http://erp4u.cz, http://chat4u.cz etc.
Go to “Site Setup” and open “Multi Logo Settings” configlet listed under “Add-on Product Configuration” control panel section.
There you can specify a several options like display order (inline or block), logo items separator and define individual parts/items of the logo. Additional promo text placed under logo items can be defined also.
In our case set “display inline” to True, as separator we enter “|” and define the following logo items:
title=DMS4U image= link=http://dms4u.cz css_class='activeLogo' # to make logo item visually activated new_window=False # we want the logo item to act like standard portal logo separator='+' ... title=CMS4U image= link=http://cms4u.cz css_class='inactiveLogo' # to make logo item visually deactivated new_window=True separator= ... etc
Copyright and credits
collective.multilogo is licensed under the GPL. See LICENSE.txt for details.
It was written by Lukas Zdych anc contributed by Matous Hora.
Changelog
0.2.1 - 2008/08/19
synced readme.txt files [lzdych]
0.2 - 2008/08/19 =——————
fixed: lost multilogo settings after product reinstallation [mhora]
enabled logo item separator per logo item and added configuragle promo text under the logo items [mhora]
added fallback for empty logo link to portal navigation root [mhora]
0.1 - 2008/12/01
Initial release [lzdych]
1 maintainer
Metadata
1 maintainer
Release files for collective.multilogo 0.2.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 | |
|---|---|---|---|---|
| collective.multilogo-0.2.1.zip | 31.1 kB | Without provenance | Details |
Release files / collective.multilogo-0.2.1.zip
| Download URL | collective.multilogo-0.2.1.zip |
|---|---|
| Size | 31.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7236104327ea61e1ad1f158cf8af2883974127bd404ff4705cca93112b81dacc
|
|
BLAKE2b-256 checksum How to use checksums |
bf683ddfea619971a4c35fe1e4672020b17e99f0891f983fe4044db94863c806
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.multilogo 0.2.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.
