nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Ignoring related items while publishing parent content instance

Venkat_Ramamurthy

Hi,

We have a requirement like when user publishes the main content instance we doesnt want the related items to get published, we configured relator cce widget and in that we have a content select cce widget with allowed type as main CTD

Ex: If main CI is of type 'xyz'(ctd name) then in main ci we have relator, in relator we have content select cce whose allowed type is 'xyz'(CTD name) (cyclic dependency).

If allowed types of content select cce inside the relator point to different CTD other than 'xyz' then while publishing if we use validation policy as lenient then we are getting option to publish the main ci excluding related items (publish,execlude warning) which is working fine if main ctd type is different from the allowed type in content select cce, but if allow type of content select cce is 'xyz' which is same as main ci type then it is not showing the option (publish,excluding warnings).

So Please suggest us with an approach where we can publish only the main ci ignoring the related items even if we have cyclic dependency.

Thanks,

Diwakar

Find more posts tagged with

Comments

Mario_DAnna

If you are on 8.1 you may proceed as follows:

- have your content select not implementing references (you will need to make the references checkbox visible by setting the suitable art in the VgnExtContributor resource)

- implement a listener which defines an ad-hoc reference when the linked content is of the desired type

Ciao

Mario

Sent from my iPhone

On 19/giu/2012, at 10:35, "eLink Entry: Discussion Group - Web Experience Management" <v7webcontentmanagement@elinkkc.opentext.com> wrote:

eLink : Ignoring related items while publishing parent content instance
Ignoring related items while publishing parent content instance Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 06-19-2012 04:30

Hi,

We have a requirement like when user publishes the main content instance we doesnt want the related items to get published, we configured relator cce widget and in that we have a content select cce widget with allowed type as main CTD

Ex: If main CI is of type 'xyz'(ctd name) then in main ci we have relator, in relator we have content select cce whose allowed type is 'xyz'(CTD name) (cyclic dependency).

If allowed types of content select cce inside the relator point to different CTD other than 'xyz' then while publishing if we use validation policy as lenient then we are getting option to publish the main ci excluding related items (publish,execlude warning) which is working fine if main ctd type is different from the allowed type in content select cce, but if allow type of content select cce is 'xyz' which is same as main ci type then it is not s! howing the option (publish,excluding warnings).

So Please suggest us with an approach where we can publish only the main ci ignoring the related items even if we have cyclic dependency.

Thanks,
Diwakar
[To post a comment, use the normal reply function]
Forum: Discussion Group - Web Experience Management
Content Server: Knowledge Center

Diwakara_Rao_Matha

Thanks for reply.

We are using WEM 7.6

Mario_DAnna

In this case the previous solution cannot be applied because in 7.6 adhoc references do not exist yet.

The only thing that you can do is the following

You need to make changes to your content type. The trick here is to make the content select to not store references and add a hidden widget containing the reference itself. You will therefore implement a listener that will copy the content management id stored in the content select into the attribute where you have defined this hidden content select when you want to create the reference to the linked content.

What you have to do is the following:

1. Enable the property in the CCE resource so that you can disable the references in the content select

2. Add an attribute to your content type and define on it a "hidden content select". That's easy. You set a content select CCE and you define as its xsl the xsl of the hidden widget !

3. Implement your listener on post-persistence create and update. The listener must retrieve the value of the visible (and not referencing) content select, recognize the type of the linked asset and copy in the hidden content select if it's of the right type.

Ciao

Mario

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, June 19, 2012 2:11 PM
To: eLink Recipient
Subject: Re Ignoring related items while publishing parent content instance

Posted bydiwakararaom@virtusa.com (Rao Matha, Diwakara) On 06-19-2012 08:04

Thanks for reply.

We are using WEM 7.6

[To post a comment, use the normal reply function]
Topic:	Ignoring related items while publishing parent content instance
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Venkat_Ramamurthy

Hi Mario,

Thanks for reply.

1. Enable the property in the CCE resource so that you can disable the references in the content select
VENKAT: current in config console we have "wcmup.widget.enableUnmanagedReferences as false", are you saying to change that to true? Setting such will not store any references? correct me if my understanding is wrong.

I changed the value to true in the config console but still I can see the reference items when I try to publish the base CI.

2. Add an attribute to your content type and define on it a "hidden content select". That's easy. You set a content select CCE and you define as its xsl the xsl of the hidden widget !

VENKAT: I don't find any widget like hidden content select cce and can you please explain me clearly on how to define the content select cce widget with xsl of hidden widget.

3. Implement your listener on post-persistence create and update. The listener must retrieve the value of the visible (and not referencing) content select, recognize the type of the linked asset and copy in the hidden content select if it's of the right type.

VENKAT: Cant I use a pre-persistent for this functionality? Hope that will reduce my code logic for skipping of commit method to avoid infinite loop.

Thanks and Regards,
TRV

On Tue, Jun 19, 2012 at 10:26 PM, eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

RE Re Ignoring related items while publishing parent content instance Posted bymdanna@opentext.com (D'Anna, Mario)On 06-19-2012 10:24

In this case the previous solution cannot be applied because in 7.6 adhoc references do not exist yet.The only thing that you can do is the following You need to make changes to your content type. The trick here is to make the content select to not store references and add a hidden widget containing the reference itself. You will therefore implement a listener that will copy the content management id stored in the content select into the attribute where you have defined this hidden content select when you want to create the reference to the linked content. What you have to do is the following: 1. Enable the property in the CCE resource so that you can disable the references in the content select2. Add an attribute to your content type and define on it a "hidden content select". That's easy. You set a content select CCE and you define as its xsl the xsl of the hidden widget !3. Implement your listener on post-persistence create and update. The listener must retrieve the value of the visible (and not referencing) content select, recognize the type of the linked asset and copy in the hidden content select if it's of the right type. CiaoMario From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, June 19, 2012 2:11 PM
To: eLink Recipient
Subject: Re Ignoring related items while publishing parent content instance

Posted bydiwakararaom@virtusa.com (Rao Matha, Diwakara) On 06-19-2012 08:04

Thanks for reply.

We are using WEM 7.6

[To post a comment, use the normal reply function]
Topic:	Ignoring related items while publishing parent content instance
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

[To post a comment, use the normal reply function]
Topic:	Ignoring related items while publishing parent content instance
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Venkat_Ramamurthy

Hi Mario,

Thanks for reply.

1. Enable the property in the CCE resource so that you can disable the references in the content select
VENKAT: current in config console we have "wcmup.widget.enableUnmanagedReferences as false", are you saying to change that to true? Setting such will not store any references? correct me if my understanding is wrong.

I changed the value to true in the config console but still I can see the reference items when I try to publish the base CI.

2. Add an attribute to your content type and define on it a "hidden content select". That's easy. You set a content select CCE and you define as its xsl the xsl of the hidden widget !

VENKAT: I don't find any widget like hidden content select cce and can you please explain me clearly on how to define the content select cce widget with xsl of hidden widget.

3. Implement your listener on post-persistence create and update. The listener must retrieve the value of the visible (and not referencing) content select, recognize the type of the linked asset and copy in the hidden content select if it's of the right type.

VENKAT: Cant I use a pre-persistent for this functionality? Hope that will reduce my code logic for skipping of commit method to avoid infinite loop.

Thanks and Regards,
TRV

On Tue, Jun 19, 2012 at 10:26 PM, eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

RE Re Ignoring related items while publishing parent content instance Posted bymdanna@opentext.com (D'Anna, Mario)On 06-19-2012 10:24

In this case the previous solution cannot be applied because in 7.6 adhoc references do not exist yet.The only thing that you can do is the following You need to make changes to your content type. The trick here is to make the content select to not store references and add a hidden widget containing the reference itself. You will therefore implement a listener that will copy the content management id stored in the content select into the attribute where you have defined this hidden content select when you want to create the reference to the linked content. What you have to do is the following: 1. Enable the property in the CCE resource so that you can disable the references in the content select2. Add an attribute to your content type and define on it a "hidden content select". That's easy. You set a content select CCE and you define as its xsl the xsl of the hidden widget !3. Implement your listener on post-persistence create and update. The listener must retrieve the value of the visible (and not referencing) content select, recognize the type of the linked asset and copy in the hidden content select if it's of the right type. CiaoMario From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, June 19, 2012 2:11 PM
To: eLink Recipient
Subject: Re Ignoring related items while publishing parent content instance

Posted bydiwakararaom@virtusa.com (Rao Matha, Diwakara) On 06-19-2012 08:04

Thanks for reply.

We are using WEM 7.6

[To post a comment, use the normal reply function]
Topic:	Ignoring related items while publishing parent content instance
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

[To post a comment, use the normal reply function]
Topic:	Ignoring related items while publishing parent content instance
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Mario_DAnna

Sorry, that's a typo: I meant *pre* Persistence, not post Persistence.

When you change to true the "wcmup.widget.enableUnmanagedReference" the system will display a checkbox in the widget config. You need to set the reference as "unmanaged" in the widget config itself.

To make a widget hidden, you can:

1. Try setting the VgnAllUsers in the Hidden field of the Authorized Group panel

2. If this doesn't work (I have fixed it in 8.0sp1 and I don't know if the fix has ever been backported to 7.6), change the widget xsl to use the xsl of the hidden widget. To do this you need to copy and paste the hidden widget XSLT field value from the config console into a text file and deploy it into your custom webapp to vcm. Let's say you have deployed /mywebapp/xsl/hidden.xsl, then you need to set

ciao

Mario

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, June 20, 2012 4:09 AM
To: eLink Recipient
Subject: Re RE Re Ignoring related items while publishing parent content instance 2

Re RE Re Ignoring related items while publishing parent content instance 2

Posted byvenkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 06-19-2012 22:07

Hi Mario,

Thanks for reply.

1. Enable the property in the CCE resource so that you can disable the references in the content select
VENKAT: current in config console we have "wcmup.widget.enableUnmanagedReferences as false", are you saying to change that to true? Setting such will not store any references? correct me if my understanding is wrong.

I changed the value to true in the config console but still I can see the reference items when I try to publish the base CI.

2. Add an attribute to your content type and define on it a "hidden content select". That's easy. You set a content select CCE and you define as its xsl the xsl of the hidden widget !

VENKAT: I don't find any widget like hidden content select cce and can you please explain me clearly on how to define the content select cce widget with xsl of hidden widget.

3. Implement your listener on post-persistence create and update. The listener must retrieve the value of the visible (and not referencing) content select, recognize the type of the linked asset and copy in the hidden content select if it's of the right type.

VENKAT: Cant I use a pre-persistent for this functionality? Hope that will reduce my code logic for skipping of commit method to avoid infinite loop.

Thanks and Regards,
TRV

On Tue, Jun 19, 2012 at 10:26 PM, eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com> wrote:

RE Re Ignoring related items while publishing parent content instance

Posted by mdanna@opentext.com (D'Anna, Mario) On 06-19-2012 10:24

In this case the previous solution cannot be applied because in 7.6 adhoc references do not exist yet.

The only thing that you can do is the following

What you have to do is the following:

1. Enable the property in the CCE resource so that you can disable the references in the content select

2. Add an attribute to your content type and define on it a "hidden content select". That's easy. You set a content select CCE and you define as its xsl the xsl of the hidden widget !

Ciao

Mario

Posted by diwakararaom@virtusa.com (Rao Matha, Diwakara) On 06-19-2012 08:04

Thanks for reply.

We are using WEM 7.6

[To post a comment, use the normal reply function]
Topic:	Ignoring related items while publishing parent content instance
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

[To post a comment, use the normal reply function]
Topic:	Ignoring related items while publishing parent content instance
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

[To post a comment, use the normal reply function]
Topic:	Ignoring related items while publishing parent content instance
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

image001.png

image002.png

Venkat_Ramamurthy

Thanks for the reply..the solution worked for us...but do we have any other solution without using hiddent content select ?

Mario_DAnna

No, not in 7.6. This solution mimics the approach used by the Furl ct.

Mario

Sent from my iPhone

On 20/giu/2012, at 11:32, "eLink Entry: Discussion Group - Web Experience Management" <v7webcontentmanagement@elinkkc.opentext.com> wrote:

eLink : RE Re RE Re Ignoring related items while publishing parent content instance 2
RE Re RE Re Ignoring related items while publishing parent content instance 2 Posted by venkat.ramamurthy@seagate.com (Ramamurthy, Venkat) On 06-20-2012 05:27

Thanks for the reply..the solution worked for us...but do we have any other solution without using hiddent content select ?
[To post a comment, use the normal reply function]
Topic: Ignoring related items while publishing parent content instance
Forum: Discussion Group - Web Experience Management
Content Server: Knowledge Center