Conditional Build Tags - Default Options Missing

Greetings,
In RHX6 when I right-click in a topic to apply a conditional
build tag the default options Online and Print do not appear in the
menu; the only option is New/Multiple.
How do I get the default options back?
Regards,

This sounds like that at some time in the past the default
ones have been deleted. Just add them again from the New/Multiple
menu item.

Similar Messages

I need help with the conditional build tag option RoboHelp 10

I need help with the conditional build tag option. I want to apply CBT to content in a topic. I looked at the Help topics and believed that I applied the feature correctly. Howver, it is not working as desired. In the 2nd sentence below I want the text highlighted in blue to only appear for the printed output and the text printed in purple to only appear for the .htm /online output. Please help.
There are common tasks used to manage the folders in the Navigator and the folders
in the BBS Folders Viewer Grid. For more information on these common tasks see Help
and Support in Success Enterprise. click the links below.

Hi there
Using tagging is a two part process.
Part One
You create and apply the tags to the information you wish to control.
Part Two
You create a Build Expression that is used when you generate your output. The Build Expression typically reads something like: NOT Tag1 (or whatever your tag name is)
Then when you generate and use the Build Expression, the information tagged is not included in the build.
Cheers... Rick

The extra space created due to Conditional Build Tags

Hello,
I am authoring a online help file, for a web application. As different content is needed for the 4 different roles of the user, I have used Single Sourcing option and made use of conditional build tags for the content that is not common among the different roles. I even have images which are difffernt for the differnt roles. I have used conditional build tags for these too. The problem is that, extra space appears in place of the images which are not applicable to build I am publishing. Is there any workaround other than modifying the HTML files to remove the extra space added?
Regards,
Deepti Korwar

hi Deepti,
I have seen this issue on multi-level lists (in RH9) when using soft returns (Shift-Enter) within the lists.
An extra space is added before images marked with CBTs. But this only caused problems in print.
Are you seeing this space on all outputs or just print?
Can you paste a code snippet from one of the offending list?
Perhaps you can get round this by opening up the HTML tab and carefully examining and perhaps moving the CBTs.
e.g. <?rh-cbt_start condition="xyz" ?><img src="xyz" > <?rh-cbt_end ?></p><?rh-list_end ?>
Will be helpful to see the code.
thanks
Craig

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

Text coded with conditional build tags still showing up in TOC even if tag is "excluded"

I am using TCS2, Windows XP.
After creating a book in FM and coding with conditional build tags, I imported into RH. When I generate, I have the output tag set:
NOT NoOUtput AND NOT Internal AND NOT Print - I want to generate my External, Online Help webhelp. And it works like a charm. Except that:
In the TOC, I can still see headings for things that are "internal" - when I click on it, they don't go anywhere... but I don't want them to appear in the TOC!!
It seems to be excluded from the index and the search. I am sure I am just missing a step or something...
In looking through the forums I found this... http://forums.adobe.com/message/751847#751847 -- I don't know if it is still applicable since it seems to be referring to RH6 (which is a bit away from RH 8 that I am using)...
Any help is appreciated!
TIA,
Adriana

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

Can I use conditional build tags in CSS files?

I am using RoboHelp X5.0.2 and building CHM files.
I use conditional build tags to output different Help files
for the different products we have that all have similarities.
In the past I have setup the CSS file to show headers, links
etc in the color scheme we use to keep the look and feel of our
branding. One of the new products uses a different branding color
scheme.
I was wondering if there is a way I can use conditional build
tags in the CSS file so that when I build one type of help it uses
header in one color and when I build another help it uses a
different header color. Does anyone know how to do this? If it is
not possible in my current version, is it possible in the latest
version of Robohelp?

[WORKAROUND ALERT IN X502]
For .chm output, you could:
1. In the Topics pane, select all the topics (click on one
topic and press Ctrl+A).
2. Right click in the highlighted area and select Properties.
3. In the Appearance tab, select the different style sheet.
4. Click Save.
5. Generate the .chm file.
6. (optional) Repeat steps 1-4 to revert to previous style
sheet setting.
Good luck,
Leon

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

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 on tables

When I add conditional build tags to rows in tables, the text
becomes hidded (as expected), but the rows still appear. This way I
get the table too big, but with
gaps. Am I missing something?

Hi karlroth. When you assign a build tag to a row RH very
helpfully only applies it to the rows content not the row itself.
If you go into the truecode and move the x-condition statement to
the TR tag you'll be OK.

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

Conditional build tags disappeared

Hi All,
For info, we are using Tech Comms Suite 3.5 with RoboHelp 9.
We have an interesting problem in that some of our conditional build tags have somehow gone missing! We are unable to select them to apply to content/topics for selection, however where the tags have been applied the tooltip showing the condition is displayed when you hover the cursor over the 'conditioned' content. When we look at the tags applied in the topic properties dialog box, the tag does not appear.
I'm hoping that someone might have experienced this and can point us in the right direction please? Does anyone know which RoboHelp file holds all the conditional build tag information? Does anyone know an ideal solution that does not entail us creating replacement tags then reapplying them to the relevant information?
Thanks all for your help.
Lillibet

From my recent experiments with modifying .apj files and what not behind the back of RH9 I can say that this also happened to me, especially in situations where I deleted the .cdb and the .xpj file to start over from opening the .hhp file. Anyway, you might look into the file rhbuildtag.apj and examine whether your build tags are in there.
If not, just create them either in an editor if you know the syntax
<?xml version="1.0" encoding="utf-8"?>
<rhpml majorversion="4" minorversion="0">
    <buildtags>
        <buildtag>
            <name>BUILDTAG_1</name>
            <colorref>12632256</colorref>
            <comments/>
        </buildtag>
        <buildtag>
            <name>BUILDTAG_2</name>
            <colorref>16711680</colorref>
            <comments/>
        </buildtag>
        <buildtag>
            <name>Online</name>
            <colorref>65280</colorref>
            <comments/>
        </buildtag>
        <buildtag>
            <name>Print</name>
            <colorref>255</colorref>
            <comments/>
        </buildtag>
    </buildtags>
</rhpml>
Or you may just recreate them from the GUI.
Christoph

Apply Conditional Build tag to Browse Sequence

Hi Everyone-
I'm trying to control 6 conditional builds in one project. I
have 6 working indexes and TOCs using build tags. I was wondering
if there was a way to apply tags or somehow conditionalize the
browse sequences. I'm running RH7.
Thanks in advance!
Wendy

Hi Wendy:
It seems you are having the same problem that I did. I have
different User Guides however some of the Guides may have the same
procedure. I was trying to setup the search so only one of the
topics would return on the search and not 3 of them. I found
something that actually had to do with RoboHelp x3 but I applied it
to RoboHelp x5, where you need to do the following.
Create build TAG1 - this is for the ones you do not want
search to return.
Create build TAG2 - this is for the ones you do want the
search to return.
Apply the tags accordingly to each procedure accordingly.
Make copies of the following files in the WebHelp directorys
just incase:
Folder WHDATA:
whftdata0.htm
whwdata0.htm
Folder WHXDATA:
whftdata0.xml
whfwdata0.xml
Folder WHGDATA
whlstf0.htm
GENERATE PRIMARY LAYOUT (This should be set to Webhelp)
1. Define the Conditional Build Expressioin to exclude topics
that are not wanted in the search:
A. Click the Define button.
This wil bring up the Define Conditional Build Tag
Expression dialog.
B. Click the Advance button.
C. Click the Not button.
D. Select TAG1 from the drop-down list of Available
Conditional Build Tags.
E. Click the Add Tag button.
F. Click OK
G. Select your WebHelp Options, and then click Finish.
When you pull up your test or Dev site and perform a search
you should only come up with one topic. I just finished this and it
worked. Also, as a reminder I am working in x5 and not x7.
Good Luck,
Amy

Easily remove in-line Conditional Build Tags?

I'm wondering if there's an easy way to remove all Conditional Build Tags (CBT) inside a topic. Has anyone come up with a quick way to do this?
The problem I'm running into is I want to remove some CBTs on some list items. But it's not easy to remove the CBTs because the right-click menu item to deselect the CBT is grayed out unless I select a certain sub-set of the list just right. Sometimes this even happens on a single sentence. I have to select a part of the sentence and remove that part first and then the other part. It seems due to in-line formatting that's affecting this. I'm hoping there's an easier way. Any scripts out there that do this?
I can probably figure out how to do it in Notepad++ with regular expression pattern matching, but that's a hassle if there's an easier solution.
I'm using RH 9.02.271.

If you right click in a paragraph you should see either Remove Attribute or Remove Attributes.
If Remove Attribute and the attribute is a CBT, then Rh will remove it cleanly.
If Remove Attributes, when you click the option you will get a dialog and can select the span tags you want removed.
Not quite what you want but it does work cleanly.
Back up first though just in case you remove too much.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Conditional Build Tags - Default Options Missing

Similar Messages

Maybe you are looking for