We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://www.monasterium.net/mom/IlluminierteUrkundenIllUrkOe/collection is a collection consisting only of charters which are "hooked-in" from https://www.monasterium.net/mom/IlluminierteUrkundenIllUrk/collection. When opening this "hooked-in"-collection in the image-preview (https://www.monasterium.net/mom/IlluminierteUrkundenIllUrkOe/images?block=1) it returns an The query exceeded the predefined timeout and has been killed. [at line 161, column 26] In function: img:years(item()*) eXist-error. The image preview of the master collection (https://www.monasterium.net/mom/IlluminierteUrkunden/images?block=1) is working fine. It is my assumption that this is due to the hooked-in mechanism, but that would have to be investigated.
The query exceeded the predefined timeout and has been killed. [at line 161, column 26] In function: img:years(item()*)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://www.monasterium.net/mom/IlluminierteUrkundenIllUrkOe/collection is a collection consisting only of charters which are "hooked-in" from https://www.monasterium.net/mom/IlluminierteUrkundenIllUrk/collection. When opening this "hooked-in"-collection in the image-preview (https://www.monasterium.net/mom/IlluminierteUrkundenIllUrkOe/images?block=1) it returns an
The query exceeded the predefined timeout and has been killed. [at line 161, column 26] In function: img:years(item()*)
eXist-error. The image preview of the master collection (https://www.monasterium.net/mom/IlluminierteUrkunden/images?block=1) is working fine. It is my assumption that this is due to the hooked-in mechanism, but that would have to be investigated.The text was updated successfully, but these errors were encountered: