Skip to main content
T
Timothy386187870sd3
Known Participant
February 18, 2026
解決済み

Conditional build expressions not being applied after updating to Adobe Robohelp 2026.01.11 version

  • February 18, 2026
  • 返信数 10.
  • 347 ビュー

Upon updating to Adobe Robohelp 2026.01.11 version, the system is no longer applying my conditional build expressions. The condition tags still exist in the project. They still show up in the UI’s author view.  If I use the UI’s Output view and look at the output presets, I can still see the condition expressions. Everything looks as expected.

If I use the UI’s preview mode and select either condition tags or condition expressions and then select appropriate options for either selection, the system no longer displays the expected content.

If I generate the output (and this is where I noticed the issue), my output includes ALL content, not observing any condition tags.

Is anyone else experiencing this?

Is there a way for me to roll back this update? I need to publish updates, but I can’t if I am publishing everything when I need to be generating six different versions of the online help.

      解決に役立った回答 Peter Grainge

      In a test I ran, it appears that AND and OR have been “corrected” in 2026.01. 

      In 2022 AND really meant OR and OR really meant AND. Adobe could not change that as that is how it all worked when they bought RoboHelp from Macromedia who in turn bought it from Blue Sky.

      Unfortunately in 2026.01 they seem to have written the code behind so that it works "correctly", by which I mean if the code had been written correctly in the first place.

      I have sent an urgent email to my Adobe contacts to confirm my findings.

      Meantime my suggestion is you duplicate your expressions and in one copy swap AND and OR to their opposites.

      PLEASE REPORT IN THIS THREAD IF YOU FIND THE SAME ISSUE. JUST ADD “Me Too” PLUS DETAILS OF ANY FURTHER ISSUES RE EXPRESSIONS..

      My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

      返信数 10

      Peter Grainge
      Community Expert
      Peter GraingeCommunity Expert
      Community Expert
      March 25, 2026

      Please note that  2026.03 has been released to fix this issue.

      My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

      Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
        dvrvb
        dvrvb
        Inspiring
        March 4, 2026

        I have the same experience with the issue of the conditional expressions.

        After the update, and after I noticed the issue, I went back to the previous version, but unfortunately I had at that moment no time to report it.

        I didn’t yet tested the swap of AND and OR, but I will do.

        dvrvb
        dvrvb
        Inspiring
        March 26, 2026

        The update 2026.03 has fixed the issue of the conditional expressions, without the need to swapping of AND and OR. It seems to work again as before the update to 2026.01. 

        DebDeb
        DebDeb
        Participant
        February 27, 2026

        I have this issue as well and it caused a major release issue. I consider this issue so severe that users should have been notified and not wait for enough complaints. Anyway, we rolled back, but we need the new version for a Confluence project. 

        Peter Grainge
        Community Expert
        Peter GraingeCommunity Expert
        Community Expert
        February 27, 2026

        It is not the case that Adobe were waiting for enough complaints. That is an incorrect statement from Adobe's general support rather than the RoboHelp support team. As soon as Tim posted this problem, I personally alerted the engineering team and they started work on a fix.

        I also posted a warning that Adobe elevated to an Announcement.

        I recommend subscribing to this forum so that you are alerted to any such issue. See Issues on my site for a possible fix that may work for you.

        ________________________________________________________

        My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.  

        Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
        G
        glundeen
        Inspiring
        February 26, 2026

        I just upgraded to 2026.01.11 and have the same issue with the condition expressions. I contacted Adobe and was told they haven’t opened a bug yet because apparently not enough people have reported the issue. I don’t want to roll back to the previous version because every time I uninstall/reinstall, I loose all my publishing profiles and it takes a long time to recreate over 80 of them. Very frustrating!!

        Peter Grainge
        Community Expert
        Peter GraingeCommunity Expert
        Community Expert
        February 27, 2026

        What you have been told is wrong. I am in direct contact with the engineers and I can assure you this bug is being worked on.

        My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

        Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
        G
        glundeen
        Inspiring
        February 27, 2026

        Interesting, because he sent me a link to this site and suggested I post that I’m having the same issue to drive opening a bug. Glad they’re working on it.

        S
        SL_Amplify
        Participant
        February 26, 2026

        I have also encountered this problem. Multiple build tags in the build expression, and they’re all being ignored regardless of whether I toggle the build setting from AND to OR.

        T
        Timothy386187870sd3作成者
        Known Participant
        February 26, 2026

        When I tested, I tried using an expression with a single build tag. If you try an expression with a single build tag, does that work for you?

        When I edited the file in Notepad++, I noticed that there was an “AND” in a ‘group flag="Include" op="AND" ‘ tag above the rows containing my build expressions. When switching the ANDs to ORs, I did not switch that first AND.

        My tags also all started out as AND, and I switched to OR. Did yours start as AND going to OR, or as OR going to AND? Just curious.

        Peter Grainge, I have noticed some instances where I have overlapping build tags, multiple tags associated with the same text block, where I did not get the results I expected. I made adjustments to those text blocks to get them to work as expected.

          T
          Timothy386187870sd3作成者
          Known Participant
          February 19, 2026

          In my testing, switching “AND” to “OR” in my build expressions appears to have resolved this issue. Note: I did not test switching “OR” to “AND”.

          I did notice a secondary issue. Some of my condition expressions include 12 conditional build tags. When attempting to use the UI to switch the “AND” to “OR”, I noticed that I could see but could not switch the “AND” to “OR” for the tags near the bottom of the screen. While I am told it is not a recommended procedure, I edited the .expn file via Notepad ++.

          Peter Grainge
          Community Expert
          Peter GraingeCommunity Expert解決！
          Community Expert
          February 19, 2026

          In a test I ran, it appears that AND and OR have been “corrected” in 2026.01. 

          In 2022 AND really meant OR and OR really meant AND. Adobe could not change that as that is how it all worked when they bought RoboHelp from Macromedia who in turn bought it from Blue Sky.

          Unfortunately in 2026.01 they seem to have written the code behind so that it works "correctly", by which I mean if the code had been written correctly in the first place.

          I have sent an urgent email to my Adobe contacts to confirm my findings.

          Meantime my suggestion is you duplicate your expressions and in one copy swap AND and OR to their opposites.

          PLEASE REPORT IN THIS THREAD IF YOU FIND THE SAME ISSUE. JUST ADD “Me Too” PLUS DETAILS OF ANY FURTHER ISSUES RE EXPRESSIONS..

          My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

          Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
            T
            Timothy386187870sd3作成者
            Known Participant
            February 18, 2026

            I did some additional testing, and I can reproduce the error in a sample project. For me, the build expression works if the build expression only include one condition tag. If I add a second condition tag, the system does not correctly apply the build expression. It shows content that should be hidden, even in the sample project.

            Peter Grainge
            Community Expert
            Peter GraingeCommunity Expert
            Community Expert
            February 18, 2026

            Can you share that small project or create one where it doesn't work? If you can, see the Contact page on my site.

            ________________________________________________________

            My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.  

            Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
            Peter Grainge
            Community Expert
            Peter GraingeCommunity Expert
            Community Expert
            February 18, 2026

            No one else has reported this but it is early days. I can say they are working on my site so ordinarily I would say that means the issue is your project. However, another unrelated issue is working fine for some and not others. In short, for now let’s look at your project and see what we can do.

            1. Please don’t be offended but have you checked your preset does have the expression selected.
            2. If you create a new tag and apply it one topic and include it in a new expression, does that work.
            3. Open the About RoboHelp sample project and see if expressions work there.
            4. Please confirm both the source and generation folders are on the same drive and it is local.

            As to rolling back, I know Adobe Support have rolled back two users with the other issue. It will give a warning that the project has been opened in a later version and might not work properly. I think that is standard and there was only one feature change, the rest was bug fixing. I think you should be OK but maybe back things up first.

            You may want to raise this with Adobe Support as well. If you do, you need to go to Adobe Support. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. The email link tcssup@adobe.com is recommended as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.

            Post back and let us know what you find.

            My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

            Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
            T
            Timothy386187870sd3作成者
            Known Participant
            February 18, 2026

            The issue may just apply to my project(s), plural.

            I’m definitely not offended, and, yes, I verified a preset’s condition expression was still defined as expected, and the condition expression was not applied to the output.

            I have multiple projects that use conditional build tags. The issue occurs on multiple projects.

            I added a new tag to a smaller existing project, applied the tag to some text, excluded the tag from the output, and the tagged content still displayed in the output when it should not have.

            I opened a sample project, added a new tag, applied the tag to some text, excluded the tag from the output, and the tagged content was correctly excluded from the output.

            契約条件Accessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices