Hi,
I've been googling a way to add a workflow to some specific objects, not the
whole content type and I ended up to placeful workflows, but, correct me if
I'm wrong, it is intended for doing certain already existing workflow
transitions (or other things) to some objects, but not adding/enabling
For a site with historical references, we're going to store a date on content
types. However, Zope's 'DateTime' only supports dates from 1900 [1] whereas the
site may refer to a long time before that. It might even be that we have dates
where the year is a negative number. (Not billions, but maybe
Plone 4.0.3
I have a custom content-types AuthoringPublishedContent (derived from
ATDocument).
Instances of this type should be created as content of some folder generated
by some backend
logic (and only there). That's why the content-types is not implictly
addable.
On the destination folder I
On 2/28/11 12:25 PM, Gil Forcada wrote:
Hi,
I've been googling a way to add a workflow to some specific objects, not
the whole content type and I ended up to placeful workflows,
correct
but,
correct me if I'm wrong, it is intended for doing certain already
existing workflow transitions (or
On 2/28/11 12:41 PM, Kees Hink wrote:
For a site with historical references, we're going to store a date on content
types. However, Zope's 'DateTime' only supports dates from 1900 [1] whereas the
site may refer to a long time before that. It might even be that we have dates
where the year is a
On 2/28/11 1:35 PM, Andreas Jung wrote:
Plone 4.0.3
I have a custom content-types AuthoringPublishedContent (derived from
ATDocument).
Instances of this type should be created as content of some folder
generated by some backend
logic (and only there). That's why the content-types is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Ritz wrote:
Not sure I get the full picture but you can only blacklist locally,
not white list. Meaning, you can't Allow this type here if it is
not allowed in the FTI for the container type. Only the other way
around works.
You got it
Il 28/02/2011 15:23, Andreas Jung ha scritto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Ritz wrote:
Not sure I get the full picture but you can only blacklist locally,
not white list. Meaning, you can't Allow this type here if it is
not allowed in the FTI for the container
On 2/28/11 3:23 PM, Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Ritz wrote:
Not sure I get the full picture but you can only blacklist locally,
not white list. Meaning, you can't Allow this type here if it is
not allowed in the FTI for the container type. Only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Two possible workaround:
- - hiding the entry from the dropdown menu through CSS (I failed
overriding an !important statement)
- - monkey-patching _allowedTypes() in
plone.app.content.browser.folderfactories which actually did the job for me
10 matches
Mail list logo