Styler bogus warning message

[ptc-953926]

Adepters:



We're using Styler for the authoring view (Epic 5.2 patch M080).
Sporadically, when I open a document I get this warning message:



[A28138] Stylesheet has references to missing definitions.
These references will be ignored. Use Styler's Validate Stylesheet menu
item to locate these errors.



Of course, when I do that Styler reports that there are no stylesheet
errors. Also, when I ask it to add new elements from the schema, none
are found. Every element in the schema is styled. What do I have to do
to get rid of this warning message? Is there some way to determine
where it's coming from or what triggers the message?



It wouldn't be so bad if I was the only one receiving this message, but
my users are reporting its occasional appearance.



Thanks,

Dave

[naglists]

Try exporting a FOSI and using it as a screen stylesheet. Editor should
successfully ID the missing definitions.

[ptc-953926]

We're still haunted by this very frustrating problem. I tried exporting
the .style as .fos and removing the stylesheet. That works nice and the
error message goes away. Is that the only solution? It would sure be
nice if I could keep the .style file and simply get Epic to quit issuing
a meaningless error message. I guess I'll have to open a PTC case, but
that's hard to do when the problem can't always be reproduced. I was
hoping someone from Arbortext would have a suggestion.



Dave

[naglists]

Sorry, Dave, I must have been out the door or off to sleep when I replied
earlier. A more complete suggestion would have included that you:

A) Use the exported screen FOSI to identify the missing definition.
B) Return to Styler and armed with that information, find and remove the
reference to that definition OR create the definition.
C) Remove the FOSI.

It is still annoying that Styler isn't finding these. I couldn't say for
sure nor certainly cite call numbers or SPRs, but I believe Arbortext is
aware of this and is working on it (or has already).


On Fri, Apr 18, 2008 at 11:51 AM, Hintz, David L <->
wrote:

> *We're still haunted by this very frustrating problem. I tried exporting
> the .style as .fos and removing the stylesheet. That works nice and the
> error message goes away. Is that the only solution? It would sure be nice
> if I could keep the .style file and simply get Epic to quit issuing a
> meaningless error message. I guess I'll have to open a PTC case, but that's
> hard to do when the problem can't always be reproduced. I was hoping
> someone from Arbortext would have a suggestion.*
>
> * *
>
> *Dave*
>
> * *
>
> *From:* Paul Nagai [