|
@Terisa: I was able to replicate it.
@chaley: I think Terisa's bug is caused by caching in the template formatter subsystem. Basically, when the server is asked for metadata for a book, the user functions from the currently loaded db in the GUI are used. Since the metadata is coming from a library without the function, the error result is cached. In the future queries from a library with the function return the error result. Since I'm not too familiar with the innards of the template system, I'm not sure what the best approach here is. Thoughts?
|