|
Revision 503
(checked in by mylan, 2 years ago)
|
Add possibility of exporting objects to Skin Product for following importing on its installation. Add full css and javascripts registries dumping. Change interface.
|
| Line | |
|---|
| 1 |
%(SKIN_PRODUCT_NAME)s |
|---|
| 2 |
|
|---|
| 3 |
Installation |
|---|
| 4 |
|
|---|
| 5 |
You can install this skin in the same way as any other Plone product: |
|---|
| 6 |
|
|---|
| 7 |
1. Install as Zope product: extract Plone skin from archive to directory of products and restart Zope (Plone). |
|---|
| 8 |
|
|---|
| 9 |
2. If you have access to file system - Set/Check in product's config.py constants. |
|---|
| 10 |
|
|---|
| 11 |
3. Install in your Plone instance with QuickInstaller 'Plone Control Panel' -> 'Add/remove Products' |
|---|
| 12 |
|
|---|
| 13 |
4. Now your Plone site should have the corresponding skin look. |
|---|
| 14 |
|
|---|
| 15 |
Note: |
|---|
| 16 |
|
|---|
| 17 |
1. SkinName was created with "Plone skin dump product":http://quintagroup.com/services/plone-development/products/skin-dump |
|---|
| 18 |
2. When you install this skin in Plone Control Panel |
|---|
| 19 |
3. all other skins created with "Plone skin dump":http://quintagroup.com/services/plone-development/products/skin-dump will be automatically uninstalled. |
|---|
| 20 |
4. Chosed in config.py import polisy (by constant IMPORT_POLICY from list ["only_new","backup","overwrite"]) |
|---|
| 21 |
define the import procedure behavior when the same id meeted in portal root. On uninstall back_[date] directory |
|---|
| 22 |
and added during installation objects not removed - this behavior choosed for more safety. |
|---|
| 23 |
|
|---|
| 24 |
Other skins created with "Plone skin dump":http://quintagroup.com/services/plone-development/products/skin-dump can be found at |
|---|
| 25 |
"Quintagroup Alternative Plone Skins project":http://skins.quintagroup.com/ |
|---|
