hi all! and great document, florent... thanks!
yuppie wrote:
Tres Seaver wrote:
The use case was that, over time, an import step might be updated. If
you
had installed your site before the update, then your configuration might
also need to be updated.
I first was confused by these sentence
Doyon, Jean-Francois wrote at 2006-1-25 15:51 -0500:
> ... FSDTMLMethods ...
>But, for some reason, now it seems bobobase_modification_time comes out
>wrong :(
>
>It's stuck at some date in October, even though the files are far more
>recent.
Note that the "methods" (like "bobobase_modification_ti
hi!
Am Tue, 24 Jan 2006 22:32:36 -0600 schrieb whit:
> howdy philip! just getting back to this. thanks for your input ;)
>
> Philipp von Weitershausen wrote:
>> whit wrote:
>>
>>>sorry for the cross post, but I know there are a number of other
>>>reference engines out there and I would like to
Hi Tres!
Tres Seaver wrote:
Tres Seaver wrote:
- The "upgrade" feature you talk about for CPS sounds a bit like what
the "version" attribute was originally for on import steps: in the
original implementation, the tool knew what versions of import steps
had been run in the past,
Hi Chris!
Chris Withers wrote:
yuppie wrote:
2.) Switch completely to unicode in CMF 2.0:
Sounds like a too big change, don't think we should try that.
I think we all know this is where we need to be eventually, 2.0 seems
the right time to do that, I'd actually prefer this, even though it
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
jens
- "A workflow without managed permission can't be exported",
[Accepted] http://www.zope.org/Collectors/CMF/397
mhammond
- "Windows Devel