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; } } }

Broken associations

susheel

We have inherited an implementation where a complete master site was deleted but it existed on one of the editions. When we try to localize it gives the following error:


ERROR com.interwoven.livesite.iw.servlet.CreateLocalizedPagesCommand () - Failed to execute
com.interwoven.livesite.common.business.BusinessException: failed to check page Localization
When we check for its depependencies we receive a different error:
ERROR com.interwoven.ui.teamsite.dependency.InspectUsageCommand () - Error while retrieving associated files.
com.interwoven.cssdk.filesys.CSInvalidVPathException: Unknown Hopi error(Bad version path)

It seems to be because of broken associations
How can we reset dependencies of these files?

Find more posts tagged with

Comments

Rick Poulin

What version and OS?

Your best bet is probably to resurrect the old files, rather than trying to localize anew. There's no ootb tool to manage dependencies directly, and the effort to build one and then figure out how to fix them is non-trivial, if even possible (since editions are read-only).

susheel

We are using 7.4.1 version on Windows OS. Can we know where the dependencies are mapped ?

Rick Poulin

There's no physical file where this information is stored, if that's what you mean. You can only modify the information via the cssdk -- there isn't even a CLT for this.

Have you tried resurrecting the original content? Is there a reason why this wouldn't work for you?

susheel

We are not sure what all dependencies it had. When we check for file associations it gives unknown hopi errors.

Rick Poulin

We are not sure what all dependencies it had. When we check for file associations it give unknown hopi errors.

It shouldn't matter though. Fix the root cause instead of the symptoms.

susheel

yeah we tried getting back all the associated files. still we get some errors. if we rename the site other than US then everything works fine along with localization. when we rename to US all the issues start(previous mappings causing the issue). can throw some light how to remove the associations using cssdk. small example if possible.

Rick Poulin

Look at CSAssociatable in the javadoc. Every CSFile implements that interface.

Not sure what you tried exactly, but I'd try restoring the edition as a whole rather than individual files. Also, downgrading a master site to a localized version of a (new?) master is not a supported operation, if that's what you're getting at. You might be better off creating a new branch and migrating the relevant content into it.

susheel

support responded back with these instructions:

add "On Delete Cascade" in the tables iwcont_site and iw_asset .

1) disabled foreign key in iw_content referencing to iw_asset
2) disabled foreign key in iw_site referencing iw_asset
3) delete from iwcont_site where site_name='****'
4) delete from iw_asset where ast_relative_path='sites/****/default.site'
5) delete from iw_asset where ast_relative_path='....'
7) enable foreign keys that were disabled above.

I am note sure what they are talking about.

susheel

We found the tables now. But they seem to empty. can someone tell what might be the issue.

Rick Poulin

I think there was a miscommunication when you described the issue to support. It looks like they're talking about the LSCS database, which would only make sense if the dependencies were preventing you from publishing/ingesting content into LSCS...

I think you need to reset the conversation and start with the initial problem, i.e. "When attempting to localize certain files, we get error X. Here's how to reproduce."

susheel

We received a patch from support and everything is fine now...