Martin Aspeli wrote:
Hi guys,
After a lot of is-this-a-bug type discussions with Rob and Wichert,
I've come to feel pretty strongly about the following:
When you load an extension profile for the first time in GS, it looks to
see if it has any import steps (in import_steps.xml) that are
Hi David,
David Chelimsky wrote:
I've used http://www.reportlab.org with sucess.
Do you know of a Zope Product that already wraps report lab, or do you
recommend just accessing directly with a script?
I've been using a product called RMLPageTemplate: -
Hanno Schlichting wrote:
One example where the current behavior makes sense is when you write an
add-on product which wants to install itself into a standard Plone site
and change the settings of the Archetypes tool. The import handler for
the Archetypes tool is only specified in the extension
yuppie-3 wrote:
Hi!
The proposed solution doesn't work:
The ImportStepRegistry is not only used for imports - it is also used
for creating new 'import_steps.xml' files for exports.
Exported profiles are always base profiles, they have to specify *all*
import handlers used for
Previously Martin Aspeli wrote:
yuppie-3 wrote:
Hi!
The proposed solution doesn't work:
The ImportStepRegistry is not only used for imports - it is also used
for creating new 'import_steps.xml' files for exports.
Exported profiles are always base profiles, they
Hi!
Martin Aspeli wrote:
yuppie-3 wrote:
The proposed solution doesn't work:
The ImportStepRegistry is not only used for imports - it is also used
for creating new 'import_steps.xml' files for exports.
Exported profiles are always base profiles, they have to specify *all*
import handlers
Previously yuppie wrote:
Base profiles have per definition no dependencies. No?
It would be useful if they had. Or rather it would be useful if there
was an include-option for them so you don't have to duplicate the
configuration for products that you want to install directly from a base
profile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Hi guys,
After a lot of is-this-a-bug type discussions with Rob and Wichert,
I've come to feel pretty strongly about the following:
When you load an extension profile for the first time in GS, it looks to
see if it has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
Previously Martin Aspeli wrote:
yuppie-3 wrote:
Hi!
The proposed solution doesn't work:
The ImportStepRegistry is not only used for imports - it is also used
for creating new 'import_steps.xml' files for exports.
Tres Seaver wrote:
I think it's wrong :) The export functionality suffers from the same
problen as the import functionality: the export steps defined in
extension profiles are only used if they have been selected once.
In other words: it is just as unpredictable.
What is
yuppie-3 wrote:
For an import operation, you run:
- All steps that came from the current base profile
- All steps that came from explicit, transitive dependencies of the
current
base profile (provided we get support for declaring profile dependencies)
???
Base profiles have
Hi!
Jens Vagelpohl wrote:
On 20 Jul 2007, at 11:00, Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Next step: What needs fixing for the final?
There has been a surprising lack of response to this question. Since I
need a CMF 2.1-final for Plone in a few weeks that could be very
Tres Seaver wrote:
'importVarious' is a brutal hack: better to focus efforts on making it
disappear. The entire point of the tool is to externalize configuration
as declarative data in the profile; accomodating imperative
configuration is not something I care to support.
I think
Hi!
Tres Seaver wrote:
Wichert Akkerman wrote:
I like Yvo's idea of make import and export registration global instead
of per-profile.
They are global to the site, if I understand you. I would *not* want
them global across the whole instance, because they aren't relevant
for all users of
yuppie wrote:
Jens Vagelpohl wrote:
On 20 Jul 2007, at 11:00, Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Next step: What needs fixing for the final?
There has been a surprising lack of response to this question. Since I
need a CMF 2.1-final for Plone in a few weeks that could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Tres Seaver wrote:
'importVarious' is a brutal hack: better to focus efforts on making it
disappear. The entire point of the tool is to externalize configuration
as declarative data in the profile; accomodating imperative
Am 31.07.2007 um 15:51 schrieb yuppie:
AFAICS the premature GenericSetup 1.3 release has the biggest issues:
I'm behind the loop on GenericSetup having only encountered it when
writing a content type for a single site. I would appreciate an
explanation of the difference between
Tres Seaver wrote:
Martin Aspeli wrote:
Tres Seaver wrote:
'importVarious' is a brutal hack: better to focus efforts on making it
disappear. The entire point of the tool is to externalize configuration
as declarative data in the profile; accomodating imperative
configuration is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charlie Clark wrote:
Am 31.07.2007 um 15:51 schrieb yuppie:
AFAICS the premature GenericSetup 1.3 release has the biggest issues:
I'm behind the loop on GenericSetup having only encountered it when
writing a content type for a single site. I
Tres Seaver wrote:
[..]
Note that the extension author's convenience was not highest in priority
in the design, which tries to make the integrators job easier.
Extension authors have to be extremely cautious, and may need to clone
steps (in the absence of dependencies).
[sorry if this
Raphael Ritz wrote:
---SNIP---
And now? What are those add-on authors (e.g. David Convent for
ATBiblioStyles or Mike Gabriel for ATBiblioTopic) supposed to do?
Include the ATExtensions and CMFBib profiles in their products
as well? Leave them out and explain in their README (which those
who
Previously yuppie wrote:
Hi!
Jens Vagelpohl wrote:
On 20 Jul 2007, at 11:00, Wichert Akkerman wrote:
Previously Jens Vagelpohl wrote:
Next step: What needs fixing for the final?
There has been a surprising lack of response to this question. Since I
need a CMF 2.1-final for Plone
Wichert Akkerman wrote:
Previously yuppie wrote:
- The exports created by the new components handler are still flawed,
ISiteRoot and placeless components are not exported correctly.
I'm quite sure I fixed that: I was able to export the components and
import them again. Has that been broken
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Hi guys,
After a lot of is-this-a-bug type discussions with Rob and Wichert,
I've come to feel pretty strongly about the following:
When you load an extension profile for the first time in GS, it looks to
Tres Seaver, on 2007-07-31:
That is by design. Once an import step is grafted into the baseline, it
is part of the site's configuration for ever. Resetting the baseline
profile (a drastic step) is the only way to wipe it out.
Which is unfortunate as it means that any Product that defines its
Martin Aspeli, on 2007-07-31:
Of course, there may be a good reason to have cache.xml not be processed if
CacheFu isn't installed, but it's still unpredictable. The only way I can
make it predictable would be if I explicitly declared a dependency on this
profile and/or I explicitly declared a
Hi!
Rob Miller wrote:
i'm pretty much in support of the proposal as it's evolved so far.
I'm not.
here's my understanding of it at this point:
- the import step registry will record the profile from which a given
import step is included. if multiple profiles include the same step in
Maurits van Rees wrote:
2007-07-31 19:43:34 ERROR Zope.SiteErrorLog
http://localhost:8080/kantoor/portal_setup/manage_importSelectedSteps
Traceback (innermost last):
Module ZPublisher.Publish, line 115, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish,
On 8/1/07, Martin Aspeli [EMAIL PROTECTED] wrote:
yuppie-3 wrote:
For an import operation, you run:
- All steps that came from the current base profile
- All steps that came from explicit, transitive dependencies of the
current
base profile (provided we get support for
29 matches
Mail list logo
