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

OnReplicantBeforeAdd index value discrepancy

michaelangel0

TeamSite 6.5 SP2 on Windows Server 2003

This is the scenario:

I have two containers for which I am registering onReplicantBeforeAdd event handlers. One container is of type 'orreplicantcontainer' and the other is an 'andreplicantcontainer'.

The index value that is passed to the event handler function for the 'orreplicantcontainer' is zero-based, whereas the index value that is passed to the 'andreplicantcontainer' starts with a 1.

Why would Interwoven do this?

This looks like a bug to me - it certainly requires a code workaround to ensure functions work in a standard way.

Find more posts tagged with

Comments

moonkhanna

TeamSite 6.5 SP2 on Windows Server 2003

This is the scenario:

I have two containers for which I am registering onReplicantBeforeAdd event handlers. One container is of type 'orreplicantcontainer' and the other is an 'andreplicantcontainer'.

The index value that is passed to the event handler function for the 'orreplicantcontainer' is zero-based, whereas the index value that is passed to the 'andreplicantcontainer' starts with a 1.

Why would Interwoven do this?

This looks like a bug to me - it certainly requires a code workaround to ensure functions work in a standard way.

Before anyone can comment on what you are saying, can you post the code you are using to get the index values and what are the output of your code..Also, how is it affecting things at your end?

ISCBorisB

This looks like a bug to me - it certainly requires a code workaround to ensure functions work in a standard way.

You are correct, there is an inconsistency in 6.5 (I never checked in 6.7).

As you've indicated, 'onReplicantBeforeAdd' Event Handler Index Parameter starts from 1 for the "And" Container(default) and
from 0 for the "Or" Container. Just deal with it, even if it's a bug IWOV will not bother with 6.5 any longer

michaelangel0

To ISCBorisB : I certainly am dealing with it - the workaround is in place and my code works now.

I was merely trying to document my frustration at having wasted time troubleshooting and debugging my code when it didn't work as expected, and to try and save others the same.

To moonkhanna: I don't think it was necessary to upload my code - the functions are Interwoven-supplied functions and could be checked by anyone without any of my code.

Thanks all the same.