moving content from one channel to another does not update the channelassociation correctly

Hi, we have editors moved content item from a subchannel (say AA) to a higher level Channel (say A). The content has other related items which may relate back to the content. When we republish the content, the content-channel association is correctly updated in the live database's vgnaschannelfileassociation table. But when republish the related items the obsolete content-channel association gets inserted into the vgnaschannelfileassociation also that end up the same content shows in two places. I've looked at appconsole and mgmt schema's vign tables, the content does not have association with the subchannel anymore. So where else I can find the obsolete association and remove it? Thanks for your help!

Find more posts tagged with

Comments

David_Stiles

What version VCM are you running?

From: eLink Entry:Vignette V7 and V8 Web Content Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, July 13, 2010 2:40PM
To: eLink Recipient
Subject: moving content from onechannel to another does not update the channelassociation correctly

moving content from one channel to another does not update the channelassociation correctly

Posted by jni@collegeboard.org (Ni, June) On 2010/07/13 15:37

[To post a comment, use the normal reply function]
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

June_Ni

V7.6.

June_Ni

Sorry, this is on v7.3.

David_Stiles

Well, 7.3 certainly makes more sense than7.6. In 7.6 there were changes made that should avoid any scenarios like theone you’ve described.

I’m not sure I actually follow thespecific details of your situation, but the problem is most likely stemmingfrom the way in which content/channel association data is managed prior toversion 7.6. Prior to 7.6 this data is managed by both the associated contentitems and the channels, which allows for the possibility of one of those twocopies to become stale. But the stale data wont be in the database. Instead thestale data will be contained in internal constructs called snapshots. Whatneeds to happen to avoid deployment/publishing of the stale data is to causethe snapshots to be regenerated. This can be accomplished by modifying thecontent items that you still see obsolete data for. Once those items have beenupdated, republishing them should clear things up.

From: eLink Entry:Vignette V7 and V8 Web Content Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, July 13, 2010 7:03PM
To: eLink Recipient
Subject: RE moving content fromone channel to another does not update the channelassociation correctly

RE moving content from one channel to another does not update the channelassociation correctly

Posted by jni@collegeboard.org (Ni, June) On 2010/07/13 19:58

Sorry, this is on v7.3.

[To post a comment, use the normal reply function]
Topic:	moving content from one channel to another does not update the channelassociation correctly
Forum:	Vignette V7 and V8 Web Content Management
Livelink Server:	knowledge-wlweb01

June_Ni

We've tried unpuliblish/republish the content item, touch and then unpublish/republish, etc. except recreat it. the old association still gets published somehow. Is there anyway to clean up the obsolete snapshot?