toutpt wrote
> Make your upgrade step just apply the profile it will install thé new
> dependencies.
What exactly do you mean "apply the profile"?
* Is it a zcml genericsetup:upgradeStep with a migration profile?
* Is it a zcml genericsetup:upgradeStep with a handler-function?
--
View this m
Hi
I am no wizard on this, but I think this should work if you are not upgrading
the other product, just installing it.
1) Make an upgrade step in your product (xcml)
2) Make a new profile in your product (in other words a folder "upgrade_1_to_2"
with metadata.xml in it
If the other product al
espen wrote
> Hi
>
> I am no wizard on this, but I think this should work if you are not
> upgrading the other product, just installing it.
>
> 1) Make an upgrade step in your product (xcml)
> 2) Make a new profile in your product (in other words a folder
> "upgrade_1_to_2" with metadata.xml in i
Make your upgrade step just apply the profile it will install thé new
dependencies.
Le 23 avr. 2013 13:24, "Jochen Dekeyser" a
écrit :
> I want to clearify my question, I don't think my previous question is
> completly clear:
> Suppose I have an add-on with metadata.xml
>
>
>
> 1
>
>
> Now I
I want to clearify my question, I don't think my previous question is
completly clear:
Suppose I have an add-on with metadata.xml
1
Now I want to upgrade my add-on and metadata.xml to:
2
profile-mydependency:default
And I want to create an upgrade step which automatically in
23. apr. 2013 kl. 10:35 skrev Jochen Dekeyser [via Plone]
:
> Hi,
>
> I want to install an additional profile of another add-on (a dependency like
> in metadata.xml) in an upgrade step. Now, I do this with some custom code.
> Although it works, it looks like overkill... Is there some Generic
On Tue, Apr 23, 2013 at 10:35 AM, Jochen Dekeyser
wrote:
> Hi,
>
> I want to install an additional profile of another add-on (a dependency like
> in metadata.xml) in an upgrade step. Now, I do this with some custom code.
> Although it works, it looks like overkill... Is there some
> GenericSetup-s
Hi,
I want to install an additional profile of another add-on (a dependency like
in metadata.xml) in an upgrade step. Now, I do this with some custom code.
Although it works, it looks like overkill... Is there some
GenericSetup-stuff that can handle this kind of situation (like metadata.xml
but fo
