=change log=
fixed the background image on the edit mode (looked weird!)
fixed the flickering menu bug
removed some unnecessary menu items
=Installing=
Just add plonetheme.ReOrg to your buildout.cfg in the eggs section and also in
the zcml slug section. Run the buildout and it will download the package
automatically. After this it will apear on your "add-on produtcs" on your site
setup.
=Uninstalling=
Go to your "add-on products" under site setup, select the theme and press
uninstall. after this, to clean up the remaining bits, go to your ZMI and go to
portal_skins, and under the properties tab delete the ReOrg skin and get the
default skin back to Plone Default and hit save. (I will fix this soon.)
enjoy!!
Metadata
Release files for plonetheme.ReOrg 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 |
|---|---|---|---|---|
| plonetheme.ReOrg-1.0.tar.gz | 65.0 kB | Without provenance | Details for plonetheme.ReOrg-1.0.tar.gz |
Release files / plonetheme.ReOrg-1.0.tar.gz
| Download URL | plonetheme.ReOrg-1.0.tar.gz |
|---|---|
| Size | 65.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d052cdc041a5bde5ab66407a768f58f13624fcebaaf62444cf1b66dab507c677
|
|
BLAKE2b-256 checksum How to use checksums |
3bc1c3b45cfd2d13ac371b4ea3b36b182f4c36c432ba924d3bdd4daccdbb9c6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plonetheme.ReOrg 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.