Ok I've just noticed that I have a different album with a deep-data.json file bigger than 4bm that works fine!
The page does not load the
deep-data.json file if no tag cloud is used for the "Whole album". (Normally, tree.json and data1.json is enough.) Try starting a Search in that album, and it will show whether deep-data can be loaded successfully in that album.
It's easy to find out if the server is the culprit by testing the local album. Does the local album work? Also, your server guy could have looked into the server log to determine the actual error. I bet it's some kind of file size restriction.
OK I (well I say I) have fixed it
I suddenly recalled an issue from three years ago, which surprised me as I usually can't recall what I did yesterday, where search wasn't working.
It was the same issue I'm having now except the album was working as it was split into folders so the data1.json was smaller than 4MB but the deep-data.json was bigger than 4MB.
Thread here
https://jalbum.net/forum/thread.jspa?threadID=58082&start=15&tstart=0
Even though we didn't pin it down to a size issue in that thread it was fixed.
The fix (as per my server guy from 3 years ago) was to add a web.config file (see bottom) with the below in it to the folder.
His note in bold below
The MIME type was set as recommended (and probably could also be configured as text/json), however the isapi handler was registered to handle the request (which is normal if you are dynamically serving json from the server side application) rather that the generic static file handler.
I just removed the isapi handler registration for .json files from that folder.
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<handlers>
<remove name="JSON" />
</handlers>
</system.webServer>
</configuration>
Edited by: ming666 on 31 Mar 2025, 15:33
