Hi,

if I edit the info.htt and start a smart upload, than ~100MB of my image gallery are uploaded. Shouldn't the info page and media be updated only?

-Micha

"Make" is required, then "Upload", simple as that.

Not sure why so much more was uploaded .... What if you upload 2nd time, just to test ... That should certainly whizz through ....

Make Album and Upload. Doing anything "clever" will take longer, will screw up the skin's JSON database files (because those files will no longer accurately reflect what's in the album), and will screw up the jAlbum uploader (because the manifest file will no longer reflect what's on the server).

This is one of the downsides to a JSON-driven album structure. No matter how small a change is made, the JSON database files for the album need to be regenerated. That takes time. But in total, they're less than 1MB, so the upload time for those files is negligible.


I can't say that I've ever seen that happen. After making a small change and making the album, open up the output directory and look at the time stamps on the files. See if you can figure out what new files are being generated. Given the size, it would have to be slide images, I would think, but I can't remember the last time I saw jAlbum do that.

One other bit of cleanup to try: connect to your server and delete the manifest.jmf file. Then, in jAlbum, do the upload again. It will be somewhat slower than normal because it will have to compare the time stamps on every file (but it won't have to upload all of them again). But that will ensure that you have a clean, undamaged manifest file on the server.

This is not an uploading problem at all. The problem is that jAlbum is generating new image files when it shouldn't be.

Just playing a hunch, but turn off all of the image variants (all of the WebP nonsense), make the album, and upload it (it will delete a bunch of stuff on the server, which might be a bit slow). Then make a small change, like to your info.htt template, make the album again, and upload it again. I'm betting that the "needless uploading" problem goes away.

I did a test: make album -> upload -> make album -> upload. Here the messages from the console. Looks like there is a problem. Do you need more information?

Making "Apidarium-04" (Changes)
Warning. New version of page Vortraege.htt exists but can't be updated (user modified). Consider removing and re-adding page
Warning. New version of page Vortraege.htt exists but can't be updated (user modified). Consider removing and re-adding page
Making deep-data.json: 0,025s
"Apidarium-04" made in 55,846s
 
Uploading "Apidarium-04" to https://www.apidarium.de/
All workers shut down
"Apidarium-04" uploaded to https://www.apidarium.de/ in 1m 15,023s
Using cached scriptEnvironment
 
Making "Apidarium-04" (Changes)
Warning. New version of page Vortraege.htt exists but can't be updated (user modified). Consider removing and re-adding page
Warning. New version of page Vortraege.htt exists but can't be updated (user modified). Consider removing and re-adding page
Making deep-data.json: 0,024s
"Apidarium-04" made in 55,676s
 
Uploading "Apidarium-04" to https://www.apidarium.de/
All workers shut down
"Apidarium-04" uploaded to https://www.apidarium.de/ in 1m 20,827s

Strange, I didn't change my album images but nearly 100 MB of album images are regenerated always. I don't understand that it behaves like it should.

Also if I change nothing, 'make album' and start an upload, than 100 MB are uploaded again. OK, I can live with it, since I don't need it often and I can wait.

I started a complete remake per deleting the output dir. Ten minutes later I started a new make and a few images get updated, but not all - see screenshot. Looks like the large images got an update.