Hi Tres!
Tres Seaver wrote:
Raphael Ritz wrote:
In the old days this would have been something like this (pseudo code):
typesTool['File'].manage_changeProperties(global_allow=False)
in the custom product's install.
The question is: how would you do that from an extension profile
without
Hi!
Raphael Ritz wrote:
That's not the point. The question is, say, you want (some of) the
default types *only* be addable to your custom type, so you want to
replicate what you do in ZMI by ticking one check box: the 'implicitly
addable' flag on a default type.
In the old days this would
Tres Seaver schrieb:
[..]
The question is: how would you do that from an extension profile
without replicating the entire 'File' fti for just this little change?
Then you aren't making an extension: it is really a base profile in
disguise, as you want to control types outside your profile's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Katja Süss wrote:
Hi *
How can I dofor type in types:if type in
NOT_IMPLICITLY_ADDABLE:
t = pttool.getTypeInfo(type)
t.global_allow = 0
for standard ATContentTypes
when using GenericSetup for a product?
Thanks
..
How can I dofor type in types:if type in
NOT_IMPLICITLY_ADDABLE:
t = pttool.getTypeInfo(type)
t.global_allow = 0
for standard ATContentTypes
when using GenericSetup for a product?
Thanks for any hints,
You shouldn't need to post-process the type information
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Katja Süss wrote:
..
How can I dofor type in types:if type in
NOT_IMPLICITLY_ADDABLE:
t = pttool.getTypeInfo(type)
t.global_allow = 0
for standard ATContentTypes
when using GenericSetup for a product?
Thanks
