#61 — namespace with 2 or 3 levels must became an option, not a template itself
by
Luca Fabbri
—
last modified
Jul 25, 2011 08:45 AM
| State | Unconfirmed |
|---|---|
| Version: | 2.19 |
| Area | General |
| Issue type | Feature |
| Severity | Medium |
| Submitted by | Luca Fabbri |
| Submitted on | Jul 25, 2011 |
| Responsible |
—
|
| Target release: |
—
|
Very often we need to put a theme, or an archetype product, inside a huge project, were we need a company.project.xxx namespace.
The only way right now is tu use the "plone.app" template and write down all information manually, or use the right template then fix all manually.
Other companies (quintagroup) developed additional template, for example a 3 level theme template (quintagroup.themetemplate).
Al this can be avoided if the namespace deep level will became an option for every template, not related to the kind of template.
The only way right now is tu use the "plone.app" template and write down all information manually, or use the right template then fix all manually.
Other companies (quintagroup) developed additional template, for example a 3 level theme template (quintagroup.themetemplate).
Al this can be avoided if the namespace deep level will became an option for every template, not related to the kind of template.
No responses can be added.
If you can, please log in before submitting a reaction.
