Cascading object creation

Friday 21 July 2006 7:56:16 am

Hi all,

this may be in the forums somewhere already, but I honestly don't know
how to search for it. My apologies if I'm duplicating a query.

What I'd like to be able to accomplish is the following:
When creating and publishing an object, I would like to use
the value of specific attribute in that object to create an additional
object at the same time.

Is this in any way possible?

Andy

Tuesday 25 July 2006 2:22:27 am

Hi Kristof,
thanks for your reply.

You can create a workflow event to accomplish this. I've made something similar, but it copies an existing object under the newly published object ( http://ez.no/community/contribs/workflow/sck_cen_create_copy ).

Your extension does look like it's really in the ball park, although it's not
exactly what I'm looking for. I think it can be tweaked, though, have to experiment a bit...

You can probably use a content/edit extension handler instead ( see http://pubsvn.ez.no/nextgen/trunk...8/content_edit_extension_handler.txt, settings/content.ini and kernel/classes/ezcontentobjectedithandler.php ).

Here I didn't have much luck, sorry. content_edit_extension_handler.txt says almost
nothing, and suggests reading setting/content.ini for more detail. But I found nothing
in settings/content.ini. And for whatever reason my installation doesn't even have
a settings/content.ini and kernel/classes/ezcontentobjectedithandler.php
(running 3.7.6 by the way).

Andy

Wednesday 26 July 2006 1:04:23 am

Figures.

I tried to upgrade to 3.8 several weeks ago and gave it up as impossible.
No matter how I approached it, the upgrade scripts chucked wobbly after wobbly.
And to be bloody honest, the new translation treatment is NOT a step forward.

Reckon I'll never have a choice in the matter, though. Upgrade or die...

Thursday 03 August 2006 1:44:12 am

To be honest, Kristof, I find it drastic as well, but in the opposite direction.

3.8 has some interesting bits that I'd love to have access to, but they come
at much too high a cost. Moving from 3.7 to 3.8 is most definately not a step
forward in my installations, but I'm forced to go that route to be able to enjoy
some bug fixes and feature additions.
At the risk of being insulting to the developers, it tastes like Microsoft and I'm
losing some trust in the whole package.
I'm beginning to re-think some upcoming projects.