The reasonable man adapts himself to the world,
the unreasonable man persists in trying to adapt the world to himself.
Therefore all progress depends on the unreasonable man.
- George Bernard Shaw
re. 2) Which version of Flare are you using? I had a problem with background images that were not showing. A bug was filed and fixed in Flare 11. Corresponding info from support: issue 93249 "An image set as a background image with xpos and ypos in background-position does not display in PDF output". I did verify it was fixed for my case.
re. 1) Did this work before? If not, are you sure that the heading levels are set correctly? E.g. h1 having mc-heading-level=1?
I've got the same problem in Flare 11. I've never bothered with PDFs before but am doing it for the first time. I've been following the instructions in the help and have a contents topic that contains the outline toc proxy. In the TOC, I have a Contents entry after the main title page and that links to my Contents topic. In the target, I have the generate toc option enabled, but when the output is built, the contents chapter is not there. It just goes from Title page straight into the main content.
@ Straygoatwriting: so you have defined your custom topic with a toc proxy AND you have enabeld Generate TOC proxy (automatic TOC generation) in the target? I would disable the automatic generation of a TOC and try the output again. Maybe Flare should be smart enough to only put an automatic TOC if no user-defined TOC is there. But maybe it doesn't work like this (always).
Yeah, I tried that, but it didn't work...and the reason was quite obvious! I didn't have a body proxy on my title page. I don't use any content from topics on my title page, so assumed that the default body frame was hiding beneath my image frame, but that wasn't the case. I must have deleted it by accident.
That sounds like what I was doing wrong on my pagelayout, I also didn't have the ToC proxy topic linked into the ToC file (embarrassingly easy fixes).
As for the background images not showing up, I discovered this was because my callout divs were set as display: inline-block; but switching them to block for print output fixed the issue.
The reasonable man adapts himself to the world,
the unreasonable man persists in trying to adapt the world to himself.
Therefore all progress depends on the unreasonable man.
- George Bernard Shaw