The flexibility offered by Opus means it is possible to build a publication which does not quite work the way you were expecting. Sometimes these bugs might look like technical problems but many are related to the publication design and so are easily fixed. This topic provides a range of things you can do to identify and solve problems yourself.
If you have been editing the same complex publication for a long time or doing a lot of cut and paste from other programs you may find it worthwhile to...
All of these things help Windows and Opus makes sure all tasks have been completed, clears the memory being used and generally refreshes things.
There is an option in the Publish Settings to show details of any errors. Although this does not always tell you exactly what the problem is, it will show at what point in the process the problem occurred, which can give vital clues. For example, it may stop at a particular page or identify a particular image or sound file. Note that if all the pages have been prepared but then the process stops then there may be an issue with a master page in the publication.
Most bugs are easily fixed once you have established where the problem actually is or what it involves. Here are some things to work through:
In both of these cases try rebuilding your publication by copying and pasting each page from the existing publication into a fresh version to see where the problem occurs or if it disappears completely.
Once you've located the problem here are some common solutions which may help fix it: