Conditional build tags applied to topic but it still displays in my TOC?

I have applied topic level conditional build tags to topics.
The corresponding books are still being displayed in my TOC. I
checked the 4 topics and the condition is applied at the topic
level. What am I missing here?

Hi Renee
If I recall correctly, you were also using Conditional
tagging on almost everything in the TOC too.
It's worth noting that:
1. Sometimes the tagging will conflict and you won't get the
results you were expecting
2. Any topic inside a book should disappear if you are
tagging at topic level. But the book will remain if at least one
topic linked to a page inside the book wasn't excluded and remains.
Cheers... Rick

Similar Messages

How to apply conditional build tags to the topic title that is displayed in Search tab of CHM?

I have the project in which 2 different words are used to reffer to one objects (this word/term depends on the customer). All other information related to functionality, steps, etc. are common. So:
In the help content (body of the files), I created 2 conditional build tags (CBT) for these terms.
In TOC, if topic title contains the term, I created 2 different topics reffered to the single topic file, but the title of the topic shows correct term (depends on CBT).
File names of this topics contain only term1.
The problem occurs when I generate CHM for CBT2 and search for the term1 (marked with CBT1) using the Search tab. All occurrencies where term1 presence in the file name, appear in the found results.
How can I resolve the issue?
These topics must be found by search (that's why "Exclude from search" option is not a decision).

Ahhh, you are correct. I believe it was Version 10 introduced that.
So here's what I'd suggest. Even though you are unable to use a variable in a Topic Title, it can still be used in other places such as the TOC, the Index and in the Topic content. So I'd still recommend that you declare and use a variable for those items. Just to simplify things.
As for any topics that have the term in the title, you could create two topics. One with the term one way and the other with the term the opposite way. Then use a Conditional Build Tag to exclude and remove the one that shouldn't be found.
This may cause you a bit of a maintenance issue by having the same topic content in more than one place. (one for each topic)
So to overcome that, you would be able to add the main body information to a topic and use an Inline Frame in the two topics that would then simply be shells with appropriate Topic Titles. Either that or declare a snippet and use the snippet in both topics. Put the main part in the snippet.
Cheers... Rick

In RH9, random conditional build tags appear within topic text

I have assigned conditional build tags to text within a topic. After closing the topic and re-entering at a later time, other (additional) text now has the conditional build tag assigned as well. However, I did not assign the tags to those other sections of text.
I do not have any trouble assigning a conditional build tag at the topic level. The issue only occurs when a tag has been assigned to text within a topic.

There is another thread running on this. See http://forums.adobe.com/thread/58834?tstart=0
I am locking this thread so that all replies go to the one above.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

RH 11: Conditional Build tags applied: Content still showing up in search

Hello. I am generating WebHelp using conditional build tags using RH 11.
I have marked books in the TOC with a CBT of Not in 6.1.
I generated help and excluded content marked with the CBT Not in 6.1.
When the Web Help is generated, the books marked with the CBT do not display in the TOC. However, if I do a search, topics that are under the books and therefore should not be included in the output have search results returned.
Is there a scenario in which topics that have been excluded from the generated help would still show up in search?
Your help is greatly appreciated.
Jenny

Hi Jenny
Indeed there are a few reasons this may happen.
First, simply excluding a topic or a book in the TOC simply makes sure that the TOC doesn't have a link pointing to the topic. Normally, I'll just tag the topic itself and ignore tagging the TOC. If a topic has been excluded, it won't appear in the TOC.
In the WebHelp SSL recipe, click to expand the Content Categories section and look at the settings on the right. You might try ensuring the following option is enabled. It's named Exclude Unreferenced Topics from Output. As long as nothing else is linking to the topic, ensuring it is removed from the TOC *SHOULD* cause it to no longer be included.
Cheers... Rick

Apply Conditional Build Tags to Index Keywords?

My client has a bespoke module for a specific customer in
their software. There is a common Help Topic with conditional build
tags applied to content, so that one Layout is for the standard
product, and the Help excludes all mention of the bespoke material,
and the other layout includes text on the bespoke module. This
works well, except for the Index Keywords for the bespoke stuff,
which still appear in the Index for the standard Help Guide.
Any ideas anyone? How do I tag index keywords so they are
excluded from a defined Layout?

Thanks Peter, So that's what they're for!
(I don't know if you ever used ForeHelp, but the Index tags
were inserted immediately next to their tagged text, so that they
were automatically included within the boundaries of the
Conditional Build Tags. This also had the benefit that when
exporting to Word, the Index at the back gave reference to the
actual page number, not the page number of the beginning of the
topic. Quite useful; I was thinking along those lines...)
Regards

Conditional Build Tags Bug

I have several problems with RoboHelp9. I am using Windows7 and 64bit. This is the one causing the most trouble.
Conditional build tags apply themselves unwanted and unassigned.
The deletion of conditional build tags at the topic properties tag (right side window) does not work.
I have to repeatedly go back and forth to the dialog and keep selecting and deleting.
Some of the conditional build tags go clear, most don't.
I go into the topic directly in the wysiwyg view and manually try to select and delete them, and they delete only with difficulty.
After running through a long topic and using every method available to clear conditional build tags, I saved the project, then went in to manually apply cbtags, of which I am only using two.
After applying them, and switching to the html window to adjust image sizes manually (because thru the wysiwyg interface the process takes too long), I find that the conditional build tag I applied to several tables and texts at the top of my topic have now applied themselves unasked to a number of the texts and even tables which I had cleared of all cbtags.
I have just about had it with this program.
This is only one of the many problems and bugs I have found and been trying to work around.
I suppose that the solution to my problem is to not use conditional build tags at all, but I am working with about five years' worth of legacy technical documents that have all been upgraded to RH9 and as I am looking at them to make the standard revisions, I am noticing this phenomenon of wrongly applied cbtags in other projects.
I would rate this as a bug of very high and critical importance.
Has anyone seen this under the consitions stated? (RH9, upgraded RH7 projects, Windows7, 64bit).

Sorry, I should have said see the Announcements.
http://forums.adobe.com/community/robohelp/robohelp_general_discussion
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Conditional build tags with character styles and ignored text

RoboHelp HTML v8.0.2.208
Windows XP Professional Version 2002 Service Pack 3 with 2 GB of RAM
Output: WebHelp and HTML Help
I have recently moved my projects from RH HTML X5 to RH HTML 8 and this is when the following problem appeared. I use lots of conditional build tags within the help projects. Some of these tags are for my own use for reference and I combine these with character styles containing a coloured background (highlight) so that they show up in the WebHelp or HTML Help output (e.g. text to identify the software version that the field/feature/text was added, reminders to check details, insertion of bug ID numbers, design document names, etc.). These areas of text are stripped out of the final build for customers by using a conditional build expression.
What I have noticed is that if a paragraph contains text with a conditional build tag applied AND that tagged text has a character style applied AND an unknown word within the conditional build tag is ignored (with the HTML tag <?rh-ignored text="word_to_be_ignored" ?>), saving the topic, closing it, then re-opening it shows that the conditional build text has stretched to the next conditional build tag, or to the end of the topic if there aren’t any other conditional build tags. This also happens by switching from Design View to HTML View. Note that this doesn’t happen if Ignore All is applied to the unknown word.
This doesn’t just apply to projects converted from RH X5. I created a new test project in RH8 and the same behaviour was observed. Similar behaviour occurred very occasionally in RH X5 but that seemed to be down to HTML tags being nested incorrectly.
The largest project contains around 1200 topics and with many hundreds of conditional build text areas this now causes a problem. I’ll probably have to locate every ignored word in an area of conditional text within each project, set it to Ignore All and then manually remove and re-apply the conditional build tags, unless someone can come up with something clever. Can anyone else replicate this and should it be logged as a bug?

Hi Daggins,
Thanks - that is good info to have. But as we all agree, that does take away from the point of single-sourcing.
You aren't misunderstsanding exactly... I am doing all my conditional tagging in FM and it works like a charm in terms of the PDFs that I generate from FM, and even the conditionally tagged text in RH shows/hides correctly. The issue is I am also importing my index and TOC from FM... and even if I have an entire file in FM tagged as conditional (all the text is tagged as conditional, I don't know if you can tag a file as conditional), the file name as a heading it still appears in the RH TOC. There is no text... but in my view it shouldn't appear in the TOC either (it looks like just a broken link when I generate my online help) - this is not ideal.

Conditional Build Tags Bugs

Hello,
I have problems with Conditional Build Tags since I upgraded from RH7 to RH9 .
I am using the following software:
Windows XP Professional Version 2002 Service Pack 3.
Version control software (RoboSource Control 3.1) as we share projects between 3 authors
And I mainly work in wysywyg view.
When I open a project on my PC, the conditional build tags I've defined in a topic apply themselves unwanted and randomly.
The deletion of conditional build tags from the topic Properties > Advanced tab > Content-level tags > Remove button does not work properly. The selected tag is removed only for the paragraph pointed by the mouse cursor. When I navigate down in my document, this tag is still present on other paragraphs.
Sometimes, I must switch to the html view to remove the tags manually.
I noticed that a thread has seent on May 5, 2011, for which Peter Grainge gave a link to a TechNote with a fix. I tried to access this TechNote, unsuccessfully.
I also read that Adobe RoboHelp Service Release 9.0.1 is intended to fix the following: CBT gets applied randomly in topic content on switching between the HTML view and the Design view in certain scenarios.
However, my scenario is completely different as CBT gets applied randomly when OPENING the project in WYSYWYG.
Moreover, my administrator told me he has already downloaded this release.
With single sources, our team produces online helps for various versions and products. This situation is very uncomfortable for me, and my colleagues, as the produced documentation may contain bad information for a version or a product or may miss information. My work is not reliable.
Has anyone encountered this situation and found a solution?
Thanks for your help.

Hi Peter,
Thanks for your help.
Effectively, the patch was not installed.
I ran the update and did not need any passwords to do it. The About RoboHelp HTML now shows 9.0.1.232. However, the version of the PolarisProjectFile.dll still shows 9.0.0.228. Is this normal?
The IT administrator is sure to have downloaded this release. He thinks something got wrong during the downloading process and that it failed.
This release solved some of my problems:
I opened again the projects in which I identified that tags were messed up.
- For some, tags were still messed up. I had to fix them again manually. I checked them in and re-opened them. They were clean.
- For others, they re-opened with tags properly assigned (miraculously).
I do not understand these differences in behavior.
I do not feel confident when I open a project. We manage so many topics that it is impossible to identify those in which tags are messed up. How can I be sure that tags are correctly assigned? It is so an uncomfortable situation !
Moreover, I identified another problems yesterday.
I wanted to open a project that another member of the team upgraded to RH9 last week. RH9 proposed me to upgrade it.
A member of the team wanted to open a project that I upgraded on my PC. RH9 proposed her to upgrade it.
We removed these projects from our local directories and used the Open project from Version Control again. And it was OK.
This situation should not occur. What do you think?
The other members of the team have the patch 9.01.232 (and the same version of dll as me).
The IT thinks that these problems are linked with my user account.
Historically, Windows XP was installed in French on my PC whereas my colleagues were in English.
As I had so many problems after upgrading to RH9, my Windows XP is now in English.
However, I keep having problems (those mentioned in this discussion).
The solution proposed now is to change my machine for a new one.
Could this be really the final solution?
Do you have any opinion on this matter?
Thanks for your help.

Conditional Build Tags...weird behavior?

If I apply a conditional build tag to a topic from the TOC
tab, the topic gets included in the output even if I have specified
that tag to be excluded.
However, if I apply the same conditional build tag to a topic
from the Project tab, then the topic gets excluded (as expected)
from the output because I have specified that tag to be excluded.
Is this inconsistency in behavior by design? I looked at the
RoboHelp Help, and it appears there is nothing wrong with adding
conditional build tags to topics from the TOC tab.
Can someone shed light on this? I am using Adobe RoboHelp
HTML 6, Build 099.
Thanks,
K
P.S.: It appears RoboHelp is completely ignoring the
conditional build tags that I am adding to topics from the TOC tab.
If I see these tagged topics from the Project tab or the Topics
tab, there is no color shading for these topics. The color shading
for the topics shows only if I tag the topics from the Project Tab
or the Topics tab.

Here's a copy-paste from the RH Help...It didn't explain
things the way you did. :-(
Applying conditional build tags to Table of Contents
Use conditional build tags to design and create multiple
versions of your project from a single set of source files. After
creating the conditional build tag, you can apply it to both books
and pages in the TOC for maximum control over the final results.
From the TOC view, you can apply conditional build tags to Topics
also. When you generate a project, you can define conditional build
expressions to include or exclude the book or page in the TOC, from
the output.
Show Me
Use this procedure to apply conditional build tags to books
and pages in the TOC. When you exclude such a tag from your output,
the book or page in the TOC, is not included in the output.
To apply a conditional build tag to a book or page in the
TOC:
Option 1:
Create the conditional build tag.
Click the TOC tab to view the Topic list.
Select a book or page to which you want to apply a
conditional build tag.
Right-click and select Apply Conditional Build Tag, and
choose the Tag you want to apply. The tag is applied to the
selected book or page.
When you generate the project, you can define conditional
build expressions to include or exclude the tagged books or pages
in the TOC, from the output. (A TOC to which a tag has not been
applied, will be included in the output.)
Option 2:
Create the conditional build tag.
Click the TOC tab to view the Topic list.
Select the book or page to which you want to apply a
conditional build tag.
From the Format menu, select Apply Conditional Build Tag, and
then choose a tag. The conditional build tag is applied to the
selected book or page in the TOC.
When you generate the project, you can define conditional
build expressions to include or exclude tagged books or pages in
the TOC, from the output. (A TOC to which a tag has not been
applied, will be included in the output.)
To apply multiple tags:
From the Format menu, select Apply Conditional Build Tag, and
choose New/Multiple. The Conditional Build Tag dialog box appears.
Click Check All to apply all the tags, or select specific
tags to apply to the book or page in the TOC.
Click OK.
If your project is under version control, these steps may
include more options. Click here for more information.
Tips:
You can also apply conditional build tags to topics, topic
content, folders, and Index.
To verify the tags applied to topics, topic areas, TOC, and
Index, or rename a tag, or change the color of a tag, click the
Project tab, expand the Conditional Build Tags folder, and
double-click the tag. You can make the desired changes in the
Conditional Build Tag Properties dialog box.
Ensure that you remove textual references to the excluded
book or page, such as text links, which refer to the tagged book or
page in the TOC. (Hotspots are not active for excluded topics.)
If you generate Printed Documentation, TOC with Conditional
Build tags are not excluded from printing.

Conditional Build Tags + Image Map + Popup Doesn't Work

For RH build X.5.0.2, I have images in some topics and a
conditional build tag is applied to those images. The images have
image maps drawn on them and those image maps launch popup topics.
Everything worked fine until I added the conditional build tag
--even though I'm not applying the conditional build tag when I
compile. Now when I click an image map, on an image that has a
conditional build tag applied (though not compiled) nothing
happens.
Can anyone help?

Did you apply the conditional tag before, or after you
inserted the image maps? Are there different results for the two
approaches?
Harvey

Conditional Build Tags and Baggage Files

Good afternoon
I have a project where I need to produce two outputs - one
for the internet and one for our intranet. I have applied
conditional build tags to the topics that I don't want displayed on
the internet however, the topics with baggage files attached still
show up - I can't figure out how to apply a cbt to these files. Can
someone help me please?
Thanks

HI Leapy.
OK I think I have got to the reason why your CBTs are being
included. If you have them at the topic level, they are exlcuded.
If you have them at the topic contents level they are included. Do
a right click on the CBT in the project tab and select the
"Properties" popup menu item. You will probably find that the tags
show up at content level. If you change these to be at topic level
you should be OK.
BTW if you are using merged webhelp there is a known problem
with links failing. Peter Grainge has covered this, and the
workaround, very well at his site. Click
here
for more details.

Auto-set Conditional Build Tags Based On Style?

Is there a way to auto-set conditional build tags based on style?
I want to be able to import a Word document into RoboHelp and have it recognize certain styles as requiring certain conditional tags. For example, an imported Word document might have a style called WD_Internal and any text with that style would automatically have a conditional build tag assigned to it. The idea is to allow my SMEs to indicate which text is intended for internal audiences and which text is OK for customer consumption in a single central Word document using styles. When the content is correct, I'd import it into RoboHelp, have RoboHelp assign conditional build tags, then generate multiple printed versions of the document (an internal version and a public consumption version).
Setting conditional build tags is pretty easy, but it will still be a lot of work to manually set them. Is there a way to do this automatically?
I am using RoboHelp HTML RH9.

Hi,
There's no way to do this through the interface. You can however create a script to do this for you. Cycle through the content of the topics and insert the code for the CBT.
Greet,
Willam

Conditional Build Tags for Framesets Using RH6

I am using RoboHelp 6. I have conditional build tags on some
topics within a folder and also on certain entire folders and these
are working nicely. In addition, however, I really would like to
add conditional build tags to two framesets in order to separate
this information so that each frameset is seen only by the
appropriate groups (just as it is in the regular topics/folders). I
am reluctant to even try to do so because if this is something that
RH6 doesn't allow I don't want to do something that will corrupt my
project. If adding conditional build tags is possible, then I need
to know where I add them: 1) to the frameset, or 2) to each of the
two topics that make up the frameset, or 3) a combination of the
frameset and the two topics.

Create a new project, import some topics from your existing
project and then attempt to do what you want. If it goes pear
shaped, no harm done.

Conditional Build Tags for Text Blocks Applied to Entire File

RoboHelp 8.0.0.203. This post also deals with conditional build tags, but in this case the conditional build tags have been associated with sections of text and text blocks within a topic. The design was implemented originally in RH7 and the project has since been updated with RH8.
For example, you could have three blocks: Purpose, Procedure, Tips, and a Notes block. They are disabled by applying blocks Tag A, Tag B, Tag C, and Tag D respectively. If Tag A is applied to the Purpose, it is cross-hatched in the design window and does not appear upon generation.
The problem is that tags that are seemingly unrelated to blocks, such as Tag C and Tag D, are spontaneously applied to those blocks -- by the software. In fact, they would be spontaneously applied to all of the blocks and text in a some of the files (for no apparent reason), cross-hatching every element and every block of text in the file. When we unapply the tag and store the file, when we re-open the file, the tag is mysteriously re-applied to all the blocks -- again by the software.
Has anyone seen this type of problem in RH8?
Below is further detail about the problem
An example of how tags shold be applied involves a block involving three banners
<div class="banner">
     <?rh-udv_start name="Banner A" ?>BANNER A NAME<?rh-udv_end ?>
     <?rh-udv_start name="Banner B" ?>BANNER A NAME<?rh-udv_end ?>
     <?rh-udv_start name="Banner C" ?>BANNER A NAME<?rh-udv_end ?>
</div>
Under normal conditions, an associated tag would be applied to "unselect" two classifications, thus selecting the third by default. This is done by highlighting the associated banner, right-clicking and selected the "UnselectedBanner" tag, Below, banner C is selected by unselecting Banners A and B. T
<div class="banner">
     <?rh-cbt_start condition="UnselectedBanner"?>
     <?rh-udv_start name="Banner A" ?>BANNER A NAME<?rh-udv_end ?><?rh-cbt_end ?>
     <?rh-cbt_start condition="UnselectedBanner"?>
     <?rh-udv_start name="Banner B" ?>BANNER A NAME<?rh-cbt_end ?><?rh-udv_end ?>
     <?rh-udv_start name="Banner C" ?>BANNER A NAME<?rh-udv_end ?>
</div>
The <?rh-cbt_start condition="UnselectedBanner"?> indicates that the section is de-selected.
Note, that the "<?rh-cbt_end ?><?rh-udv_end ?>" are in opposite order in the example (but that's how it appears in the file).
In the cases where this problme occurs, we the html riddled with "Tag D" and "Tag C" condition tags for all the elements.
<?rh-cbt_start condition="Tag C, Tag D"?><div .......     </div><?rh-cbt_end ?>
I cannot attach any files because these files are on a classified system.
Thank you much.

Hi Tammy
It will also be helpful if everyone that encounters the issue reports as a bug. It's like a voting system. The more reports of bugs that are seen, the more weight is given to the priority. This directly translates to the fix being posted sooner rather than later.
So even though the bug has been "reported", you and others should take a moment and report as well!
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

Topic and content level conditional build tags

What is the difference between a topic level and a content
level conditional build tag? Why would you select one over the
other? How do you select one over the other.

First let me point out that the same conditional build tag
can be applied at either the topic level or the content level. It
sounds like you may be thinking that you have to create a tag as
for either the content or topic level.
Apply a tag at the topic level when you want the entire topic
excluded from a certain output. Do this by right-clicking on a
topic in your Project Manager, going to Apply Conditional Build
Tag, and selecting the tag.
Apply a tag at the content level (text, images) when you want
the topic to be included but want specific content to be excluded
from a certain output. Apply a tag at this level by selecting the
text and/or images that you want to apply the tag to,
right-clicking, going to Apply Conditional Build Tag, and picking
the tag.
Note that you wouldn't use a tag at the topic level on a
topic where you have used that same tag at the content level, and
vice versa.
Generally, the idea of build tags is to set an output to
exclude certain tags, but you can also set outputs to include tags
instead, which then excludes all other tags.
--Ben

Conditional build tags applied to topic but it still displays in my TOC?

Similar Messages

Maybe you are looking for