Skip to main content
N
naglists1-Visitor
1-Visitor
September 16, 2014
Question

tag_display behavior different from ACL than from command line

  • September 16, 2014
  • 1 reply
  • 573 views
Hi,

I am issuing the following command:

tag_display -local -icon

From both the command line and from within an ACL looping over content and
choosing specific oids.

The element is collapsed and represented by the barbell icon 100% of the
time when I issue this command from the command line with my cursor in the
tag.

When issued from the ACL, the command works as expected unless the tag in
question has child elements.

For example:

<para>Blah blah blah.</para>

Is always iconized.

<para>Blah blah blah <bold>BLAH</bold>.</para>

Is only iconized from the command line. It is NOT iconized from the ACL.

Anyone seen this behavior before? Is it "as designed" or is it a bug of
some sort do ya think?


--
Paul Nagai

    1 reply

    N
    naglists1-VisitorAuthor
    1-Visitor
    September 17, 2014
    I got it. My ACL was looping using oid_forward(). Which is correct EXCEPT
    when I collapse. Immediately after a collapse, I need to oid_next(). Derp.

    On Tue, Sep 16, 2014 at 3:11 PM, Paul Nagai <->
    wrote:

    >
    > Hi,
    >
    > I am issuing the following command:
    >
    > tag_display -local -icon
    >
    > From both the command line and from within an ACL looping over content and
    > choosing specific oids.
    >
    > The element is collapsed and represented by the barbell icon 100% of the
    > time when I issue this command from the command line with my cursor in the
    > tag.
    >
    > When issued from the ACL, the command works as expected unless the tag in
    > question has child elements.
    >
    > For example:
    >
    > <para>Blah blah blah.</para>
    >
    > Is always iconized.
    >
    > <para>Blah blah blah <bold>BLAH</bold>.</para>
    >
    > Is only iconized from the command line. It is NOT iconized from the ACL.
    >
    > Anyone seen this behavior before? Is it "as designed" or is it a bug of
    > some sort do ya think?
    >
    >
    > --
    > Paul Nagai
    >
    >
    >
    >
    >
    Terms & ConditionsAccessibility statement