imslp wrote:The 300+ items probably did it in. Basically, the server will kill any page that loads for longer than 30 (or maybe it was 60) seconds as a hung page. I may try raising the limit, though the fundamental problem would unfortunately still be there.
If it is not hard to combine the files, I'd suggest doing so.
For test I performed a concatenation of the full score and the separate parts for Prelude no. 1 arr. for brass quartet
- Open the ''Ariadne'' work page in edit mode
- Comment out the 6 item entry for Prelude no. 1
- Replace the 6 item entry for Prelude no. 1 with a 3 item entry
- Save the work page - this actually restores a readable work page
- Mount WIMA's ''public_html'' directory tree as a local file system on my home pc (using sshfs)
- Copy the full score pdf file to a fall-back file
- Concatenate the full score pdf file with the separate part pdf files (using pdftk)
- Upload the the concatenated full score and parts file - having the same name as the full score file in order to preserve the WIMA/IMSLP rdirection
a cumbersome procedure. And when I returned to the Ariadne work page after the replacement action the work page was blank again
imslp wrote:Otherwise, we could wait for the limit raise. In the long term we might want to think of other ways to deal with such pages.
I have my hands full with transferring WIMA files and keeping track of the transfers performed by other transfer project participants. So I can't possibly go into a file combination task like that.
Just a thought: you say that there is a max page load time and then the load process terminates. If load time is the crucial issue couldn't we suspend the call of the external service for mp3 files (there are plenty of them in ''Ariadne'') for huge pages. It is my impression that the repeated call of the external service is by far the most time consuming part of the page load process.