🚀 go-pugleaf

Seems to me there might be a bug here.

1) Consider if you tag some destination content with a condition, yet you leave unconditional the xref that points to it.

2) Then, you hide the condition in question and generate the book.

3) The result is an error that shows in the error log.

4) So, then you go tag the xref with the appropriate condition.

5) You set the conditions to hide, book-wide.

6) In subsequent generations, the error still pops up in the log, even though you fixed it.

The solution is to save the file with the originally faulty xref as MIF and then save it back as FM.

Has anyone else run into this bug? FM 7p576. Anyone else care to test that?

Cheers,

Sean

P.S. This was posted in FM+SGML but I thought it might see more play here. One person on the framers list contacted me to say they were running into this same thing. Looks like a total of four or five users so far. Does that mean some of you are not running into this at all or are not using conditional text and FM7? I wonder.