Thanks executive...I don't know what I was searching for, but I never found any of those when I tried. And I tried multiple variations of move, moving, hosting, server, gallery. Sigh.

The second one seems to be a good quick overview. I'm not sure there aren't gremlins hiding in there :)

Paul
aka PolyWogg

Okay, looking into it, I seem to have two issues...one that might kill me and one that might save me.

First, I might have fubared myself awhile ago. I have a virtual host package, and I run WordPress in my root at PolyWogg.ca

The Piwigo install is one level down at https://polywogg.ca/pandafamily/.

I have a ton of stuff in the WP site and elsewhere that directly links to that URL structure such as an image at:

https://polywogg.ca/pandafamily/_data/i … 94-la.jpg.

If I move it to another domain, call it "PolyWogg2.ca", then all my existing URLs will be off, won't they? Even if I can copy the database over, move all the files, and get everything up and running in the new site, it won't be PolyWogg.ca in the domain root, it will be PolyWogg2.ca.

Maybe I can reroute any links from polywogg.ca/pandafamily/blah blah blah over to the PolyWogg2 address. Hmm...

Did that setup just screw me up? Should I have installed in root originally?


Second, something seems off with my install, and I wonder if it is the variety of images that are included/generated/resized. The problem I'm having with my host is that it only allows me 200,000 inodes (files and folders). That seems like a lot, and nobody ever goes near it. My main WP install with over 1000 posts has about 20K inodes.

Piwigo, by contrast, is showing 103,490 Files, 1,623 Folders. But I only have 13K photos. If I ignore say 10K for overhead, the rest is about 6-7 times the number of photos I have. Something I never really thought about, but now I wonder if I have it generating sub sizes I don't need...

In my CONFIG / Photo Sizes, it has Square, Thumbnail and Large set as automatic. After that, it also has checked:

-- XXS - tiny        
-- S - small        
-- M - medium        
-- XXL - huge        

Do I need all those? If I cut some of them, would it reduce dramatically the number of files I'm creating or does it manage those other sizes on the fly? Is there also a list somewhere that says where those sizes are shown by default?

Paul

On a separate note, I have about 13K photos in the site but it tells me that Piwigo has

Thanks Executive...I figured it out.

Basically I was asking for the sizes:

- Square        
- Thumbnail        
- XXS - tiny        
- XS - extra small        
- S - small        
- M - medium        
- L - large        
- XL - extra large        
- XXL - huge

Which ones do I *have* to have without breaking my gallery (i.e. where photos wouldn't load on some page). Square, Thumbnail, and Large are required and are pre-selected. But I was wondering if I got rid of XXS, XS, S, M, XL and XXL, would that mean some page wouldn't load i.e. if the admin page needed thumbnails and thumbnails weren't there, obviously that wouldn't load. Hence, I assume, why thumbnails is always required. I'm using Bootstrap Darkroom, and my default on the page is Large, so I was wondering if the others were required. Short answer -- apparently not. I went in, deselected them, pulled up custom settings, and in the explanation of sizes, it showed a whole list of choices and the last time any of them had "hits". Almost all of them showed at least 11 months since they were last viewed for any of the sizes. I will monitor for the future too, there's a couple of weird sizes listed in there that I might be able to get rid of too, but I dumped them.

My 150,000 inodes just dropped to 75,000 overall. I'm nowhere near the limit now!

Thanks for your help...I wouldn't have figured that out without having someone to bounce my thinking off of!

Paul

Thanks Eliz82...I found a partial way around it...my pressure to do "something" was having too many files. THen I realized that waaaay back when I set up the site, I had chosen too many variations of the photo sizes so it was generating way too many versions of the same file. I reduced and that problem is solved.

Now I have a NEW problem. Apparently when I linked, and they are rather "hardcoded" links from the URL to the blog post, the URL I got was not the default LARGE size but something else. So when I deleted all those other sizes, apparently the linked image went with it. Which means I either have to find the size that disappeared (perhaps Medium) and recreate it, or relink all those photos. Stupid stupid stupid.

PolyWogg

Thanks Eliz82,

That link (derivatives) is exactly what was going on with mine.

But now that I understand that better, I'm not sure if my new problem with missing photos embedded in my site IS what I thought it was. Here's my example...I did a blog entry about my honeymoon in Hawaii, with a post about each day with photos of what we saw. Here's the link:

http://polywogg.ca/honeymoon-recap-hawaii-day-5/

It used to work fine, all the photos showed. I wrote it three years ago, it's been fine as far as I know until recently. But now when you load it, you'll see that the first picture loads fine with the link:

https://polywogg.ca/pandafamily/i.php?/ … 3c4-la.jpg

If I understood your derivative post, the "key" part of that filename is the "-la" extension telling me that it is indeed using the LARGE default setting (I keep thumbnail, square and large by default). And it loads fine, which it should.

However, the next image (and all the rest) do NOT load:

https://polywogg.ca/pandafamily/_data/i … b6e-la.jpg

I assumed at first that it was going to have a -ME extension and since I had deleted medium, that was the problem. But no, it too is looking for the large. Except it doesn't load while the first one does.

Now, I haven't fixed the page, so I can see the problem still, but I had the same problem on other pages, and I "fixed" those ones, but I'm not sure how my fix did it. Here's what I did:

a. Opened up the original album in Piwigo
b. Browsed to the single photo page
c. Paged through to the end to see each photo was there and loading
d. Closed out
e. Reloaded the WP page, and all the images loaded.

But I don't know "why" that fixed it...I have two ideas as possible explanations but not sure which is more likely.

1. Does it mean that the gallery doesn't actually have the LARGE ones generated anymore? And by going to each page in the album where LARGE is shown, it IS generating it so now the link works?

2. Or, as my host just instituted a change for something, is it likely to be a first-time caching problem? My host just instituted LiteCache across all the servers. And I likely haven't viewed those pages since caching was rolled out. But that shouldn't matter -- most caching will try to load from the cache, but if it doesn't find it, it loads the original. It doesn't look in the cache and just stop. But, equally, if I browsed through the album, page by page, it would generate it for the cache too. I don't think it can be the caching problem, as it has been installed for almost a month now, and I still had the problem on a page I just created the other day (so the photos would have been in the cache in theory).

Any guesses as to which of the two are likely? Or, I guess more pointedly since you can't guess at my hosts caching protocol, is #1 likely?

PolyWogg

Thanks Eliz82...generation under way! Only 8K more images to go :)

PolyWogg wrote:

But I still have the following sizes showing under custom:
Custom
Delete e520x360 (Last hit: today)
Delete e1008x756 (Last hit: today)
Delete e120 (Last hit: 2 days ago)
Delete e240 (Last hit: 4 days ago)

Do you think I can delete these? Not sure why they are showing a hit for today?

No idea what is with that custom sizes, they are probably made by some plugins or themes. Not think is a good idea to delete them unless you know what you are doing.
... or maybe delete them and then deactivate and reactivate all your plugins and themes, and they will be probably be regenerated.

PolyWogg wrote:

and others were links to the original files with no -ME or -LA version for some reason).

From I remember when I worked with the Api, when original file resolution is less the the one set in medium, then the Api response will show medium derivative as a link to the original image (instead of building a new image with "-me.jpg" suffix. And this is normal as the images are not upsized to build derivatives, only downsized.

PolyWogg wrote:

Very close to done. Although when I generated the LAs for all of them, it took me back up a bit in iNodes. Still less than 50% of where I was though.

I think Piwigo should not come with all derivatives enabled by default. Like I said in that post I linked, there are many hosts that put a limit on iNodes. Only Piwigo by itself will generate by default 9 derivatives for every original image, if you also install Thumb and Piwigo mobile theme you will end up with 11 derivatives. If your host have a limit of 100.000 iNodes you can upload ~8000 pictures and you hit the limit.