Image Busy

[Dylan Raethel]

We reported this same problem on list about 2 years ago but got no response.
It appears to be a conflict between Frontier and the webserver - until this
report we thought that it was related to our particular environment
(Frontier 7/8/9.x and IIS 4/5 on WinNT).  Your report tends to point the
finger more at Frontier itself.  Infact, we have recently found that a
similar problem with writing binary files is 'cured' with a restart of
Frontier.

As you point out, the symptoms are multiple re-rendering of the same page
(twice or more).  The first time the image will render okay but on some, but
not always all, subsequent renders the macro error occurs.  The error is
thrown by file.writeWholeFile 

One thing we did to alleviate the problem was reduce the imageRef calls by
eliminating them from our template (i.e. imageRef calls were only in the
'bodytext') but this was not ideal - and we are rendering a static site, so
this may not be applicable for you.

Another work around is to put the file.writeWholeFile statement into a try
statement.  Failure here will only mean that the image is not rewritten to
disk (which doesn't matter as you've only recently had it successfully
written - hence the macro error) and the resulting <img src... html will
come through intact.  Of course, as imageRef is a builtin verb you need to
either manage your own custom version of it or be very aware of what's
happening with any .root updates that Frontier issues.

Paul Kennett


**********************************************************************
This email is not an official statement of the Waikato
Regional Council unless otherwise stated.
Visit our website http://www.ew.govt.nz
**********************************************************************