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

671SP1+1: onReplicantAdded - OR container

Adam Stoller

Environment:[indent]TS 671SP1+Patch1 on W2K - using Firefox[/indent]
Problem:[indent]Unable to get onReplicantAdded handler to fire on root of OR container[/indent]
[indent]I searched for "onReplicantAdded" in the forums, only turned up one hit - with respect to trying to implement the functionality in 6.1
I then tried just "onReplicantAdd" which turned up four hits (and not the one previously shown): one for DD, one for someone using 6.1, one for dealing with post-deletions, and the last was somewhat general in nature[/indent]

).Ideas anyone?

Find more posts tagged with

Comments

nipper

Adam, I have this working in a 6.7.1 mode, there were some funky quirks I found but was able to get it to work.

I will dig up my code & see if I can post it.

nipper

Change the JS you have highlighted to this:

IWEventRegistry.addItemHandler("/root/content" ,
"onReplicantAdded", remove_empty_level);

Your OR container is /root/content

/root/content/bulleted is a container with 1 and only 1item

Adam Stoller

Change the JS you have highlighted to this:

IWEventRegistry.addItemHandler("/root/content" ,
"onReplicantAdded", remove_empty_level);

Your OR container is /root/content

/root/content/bulleted is a container with 1 and only 1item

I believe I tried that - but it didn't seem to give me what I wanted.
I did an alert("ITEM: " + item.getName()); and it tells me something like "/root/content[0]" or "/root/content[1]" - okay, so that I try alert("TYPE: " + item.getType()); and it would only tell me it was a replicant - but I need to know the type of replciant instance it is...

I seem to recall this coming up - Unfortunately I can't think of a decent wording to use for searching in the forums - "OR" is too generic and probably would be stripped as noise - "type" is also too generic a phrase and likely to turn up thousands of hits that have nothing to do with what I want - "replicant" or "container" will probably turn up fewer hits, but still too many to easily wade through to find relevant one....

Ahh - yes, I found ISCBorisB's reference to his own post which I think gives me the logic code I was looking for - I'll try to put it to work and close the thread if it works - thanks.

(I probably should have pursued it further when I tried it - alas)

nipper

Well if you put half the time into solving this problem as you did formatting your first post, you would have figured it out.

:-)

All you need to do is a getChildren in your function and you are good to go.

Adam Stoller

Well if you put half the time into solving this problem as you did formatting your first post, you would have figured it out.

:-)

All you need to do is a getChildren in your function and you are good to go.

Heh - you don't know the half of it - I had to compose the entire post on my laptop, dump it onto a thumb-drive, and upload it on a desktop computer so I could post it ;-)

But again - I started with what I posted - I then thought about and tried taking it down to just the /root/container level - but it didn't seem to give me what I wanted and that was where I made the mistake of going back to my original non-working code instead of pursuing the code that actually got the alert to show up.

In terms of the code - it now looks something like this:

function remove_empty_level(item) {
  var name = item.getChildren()[0].getName();
  if (! name.match(/bulleted$/)) {
    return true;
  }
  ..
}

The sad part of all this is that apparently it's a built-in "feature" of FormsPublisher how the select list is rendered - because in fact there is no "blank" option for me to remove -- I only want values 1, 2, and 3 - I checked getOptions() on the item, there are only three options in there (I was expecting four, so I could delete one of them).

So all of this ended up being throw-away (for me) - because I have to just set a default value, make the select list required, and then make it not-required before I make it hidden (based on another field item) - sigh (trivial to code, but annoying to have to do so).

Thanks anway.