MadCap Software Forums

* The front/back covers do not have headers and footers; all other pages do have them.
* TOC entries point to correct layouts; for the entries with Break Type=None, the page layout is (default).
* We do have multiple layouts.
* We do not use blank pages. Do not have a blank page layout. It does not ...

The footers are large enough for the content.
There does not appear to be any body or decoration frames in the way.

What might be some other reasons why the footer text (manual title and page number) is included in some but not all of the PDFs?

Thanks in advance for the help!
Lisa

SVN works much the same as Perforce. Whatever is in SVN is what gets built. If it's not there, it's not included in the builds. The doc builds are processing again, and one project built as expected. Might have been something as simple as the files not reaching the repo. That's all been checked, and ...

haha...good thing I'm not particularly stressed and can go with the humor. All files are checked in for all projects; that is the logical first place to look, IMO. No missing linked topics, images, etc., messages are received when I build in MadCap. All looks as it should.

In answer to the Fosters ...

Problem
We recently updated the cover pages to include an image in the background and updated content. The PDFs generate with the appropriate cover art and content when produced directly from MadCap. No problem there. Once changes are made to the doc, we commit our files to SVN. Fosters then ...

Our resolution: reactivate the license key.

Just in case anyone else has this problem,

Two days ago, our builds stopped working. Instead, we have Invalid Activation Code result 2002 showing for all of our doc builds. What would generate this type of error? I think it's our SVN and Jenkins builds rather than Flare; however, I wanted to ask just in case it is a Flare issue.

Thanks!
Lisa

That was it. Thank you!

The doc I'm working with was imported into Flare about a year or so ago. We have a total of four projects: Global, Doc1, Doc2, and Doc3. Docs 1 & 2 are linked to the Global and I can reimport the ImportFromGlobal whenever I need. Doc3, however, is perplexing.

There are several topic files, page ...

Absolutely, 100% relevant. Added the body frame back in and voila! Extra page left the building! Thank you so very much. :D

This may not be relevant, but it may help. I had hours and hours of fun with an extra page that I just could NOT get rid of a few months ago.

In the end, I discovered that ...

The only difference we "had" was left-end disabled. In out PDF output, we do not include blank pages. Otherwise, everything you do, we did. The only issue I have is the extra page, which we never had before. Ever. Once I applied the new page layout, that's when the extra page was added to the output ...

We're on V8 but will upgrading to 9 soon.

I used one decoration frame and made adjustments to the position of the variables. Looks great in the PDF output. There is no background color or image or anything set in the body tag; all say (not set).

The cover_page.htm is now associated with the ...

#1 & #2: There was a body frame getting in the way. The variables in one decoration frame were in the output and work great after a few adjustments.

The variables in the second decoration frame are not coming through yet. Did the same thing here that I did to the first decoration frame. No body ...

I see that I can add variables and text to a Decoration frame on a page layout. The expected outcome is that the variable text included in the this frame would show in the output (PDF and help).

1. What might be preventing it from showing in the output?
2. Do variables not work with page layouts ...

I got it to work at the project level, but never in the Global project. There were many, many issues adding a page layout in this one. I'll just work it at the individual project level.

The previous writer imported much of the documentation from Framemaker; thus, these files are associated with FrameMakerConversion.css. Newer topic files, when associated with this same .css, have access to all of the available styles.

The specific file I'm trying to work with is a common file in ...

I created a cover page layout, but when apply that layout to the cover_page.htm, the cover page layout appears twice in the output. Then, the text doesn't show up.

What I really want to do is just add the cover art to the background of the topic file cover_page.htm. Seems simple enough, right? No ...

Why is it that I can view/select styles for some topics but not others?

We have new front/back cover art for our user manuals. The Global project has the following items that are shared among our projects:
1. cover_page.htm with ProductName, ProductVersion, DocTitle, & DocTitle2 variables.
2. masterpage layout
3. page layouts for each guide (I know we don't need all of ...

From what I've gleaned from the Flare Help, and this is from a few weeks ago, by default, a build includes all files and is based on WebHelp. If you don't want a file to be included in WebHelp, you have to tag it. The files I inherited are tagged with condition tags, which works fine. I also use ...

If I added two spaces after the colon in the Auto-number Format - Enter format box, numbers rather than alphas are displayed in the output. The Reset and Format are ignored.

Output shows Appendix A:Title rather than Appendix A: Title.

I've tried several settings on the h1.Appendix style, but can't yet find the magic one.

Help appreciated!
Lisa

Edited: It did work...except that I want it only in the TOC entry, not as the main topic heading and in the header. It inserts "Appendix" as the main topic heading and in the header, which I do not want to happen.

I would still like answers to my questions so that I can plan for future appendixes.

It's working well for the interim, but I still need two spaces after the colon. Anybody know what setting I need to update for that? I've tried several things in the h1.Appendix style, but still have 0 for ...

There are times when I want to group topic files in a TOC book, which is really a section. Some of these "books" are the actual title of the section; however, from time-to-time, I may want a book/section title to show in the output without having to link it. If I don't link it, the book/section ...