Three separate problems, here.

First, the easy one. You should not be telling jAlbum to process only updated subdirectories. With a skin like Tiger, this will produce an album in which things like the search function are broken. And if you've switched to a newer version of jAlbum or Tiger, the breakage in the album could be much worse. It's a long story, but please just trust me on this one.

Having that set correctly will, of course, generate a new index.html file for each folder, but those are small files, quickly uploaded. Just not a big deal. You will also get new JSON files (used for searching and other things), but those won't be massive, either. Not tiny - in your existing album, the deep-data.json file, for example, is just shy of 6MB. But we're talking megabytes here, not gigabytes.

The second problem, more mysterious, is why the core is generating newly-scaled images. Is that really what's happening? When you build the album, is it taking an ungodly long time? If you open the output directory and look at the file information in any of the slide folders, are you seeing new file timestamps? You're not doing a Force Remake, are you?

The third problem is the failure of the upload. David may be in touch - he might need access to your server to experiment. It's one of those areas in which there's not much useful error information in the app itself.

As I've said before: I am naturally 100% motivated to fix a bug, if this is indeed a bug. Try to reproduce it!

And as it always does, for me at least.


That's been my experience.


I think I know what's happening here. You've got a bad internet connection. jAlbum can compensate for that, but only up to a point. If it loses the connection entirely, it can no longer rely on the manifest file to tell it what needs to be uploaded. Then it has to drop back to doing a more traditional upload routine - compare each file on the server to the file on the PC. If the PC version is newer, upload it. Otherwise, skip it. So when it's telling you that it's uploading 15GB, that's a "worst case" scenario - it won't really know until it actually does the uploading.

I recently started having horrendous uploading problems. Long story short - the Ethernet port on my PC was bad. Downloads were fine, but uploads were a disaster.

Try doing some speed tests - install this app: https://www.speedtest.net/apps/desktop


Those timestamps tell me that jAlbum is not producing all new slide images. It's not actually uploading all of them. So the smart "make album" is working as intended.


No. The only thing that would trigger the production of all new scaled images would be a Force remake. Please just uncheck Process only updated subdirectories. That is creating album errors that you may not even find initially. But they're there. As I said above, that will create only new index.html files for each directory/folder - not a big deal.


At some stage of the game, you must have told Tiger to offer zip files of the images for downloading. It appears that you've turned that off, but the files are still out there. Open up the output directory of the project, and find and delete any zip files you find. Finder should be able to locate them quickly. The skin doesn't need them for anything.

Pardon the four day delay. I've been busy. (aren't we ALL!)

Followup: I added a handful of items into my gallery, then UNCHECKED the box 'Process only updated subdirectories' As mentioned above.

I rebuilt the gallery; it took a bit longer this time, like 2.5 minutes, but that's a drop in the bucket.

Time to UPLOAD.... fingers crossed.

Success! It only processed the new files, reviewed the rest and it was done in a couple of minutes. As it should be.

Of course that's the way it USED to be too, until I began this thread. I was flummoxed.

Thanks for being responsive to my needs. My site: 12,500 images ,15.8 GB of searchable uploads and it's back to behaving. Jalbum FTW.

Jim Cooper

David, at this point, I can't recall. I THINK it built it OK, and then in uploading it hit a stopping point. (Hung up on a file, if I recall. )

So then I X-out of the upload and try again. And THEN instead of going only through the new images, it begins the ENTIRE rebuild (?) Process. 5 hours. It didn't like to do this a second time.

And as was pointed out it is not even remaking every file? My HOME jalbum output directory had files made months ago. Huh?

So, maybe it was an internet glitch. I will pay closer attention if/when it happens again. This is NOT infrequent. But, I will note exactly what the sequence is.

I appreciate your program, the Turtle skin, and this forum for help. Believe it.

Jim

Oops! Yes, I USED to have Turtle, and something even before that.

Tiger it IS. Really a great interface for me. Nicely structured.

Thank you Jeff and David.

Well... Not so fast. It's BAAAACK.

I had to change ONE FILE (a misspelled one for a client.)

I removed one file, replaced one file. Hit build and it did so in just over 2 mins.

Then I uploaded it. It has a small progress bar, and it went all the way across as normal in about one or two mins....

Then it said "Writing manifest" and THEN began the whole upload process again, progress bar at the beginninng. 15.85gb of uploads. I ABORTED.

The website had loaded with my channges. Hmmmmm.

So this morning I simply repositioned ONE file in my opening gallery (Featured). I rebuilt it 2+ mins., then UPLOAD:

It began the LENGTHY rebuild all. No short progress bar. I aborted.

Now the 'Featured Gallery' is broken thumb.

Sigh. So it is back to the 5 hour rebuild just to reposition one file. (See screenshot)

Internet is fast. I dunno.

Edited by: SharpByCoop on 25 Apr 2023, 14:30
http://www.knifegallery.com/index.html