I just wanted to see if any redirects on my albums are broken now that I'm fully on TIGER skin, however, each page comes up with the same 2 non-issues making it hard to find any real issues! (if there are any broken links)

Please confirm my thoughts on this.

Attached - See the screen capture of a typical page.

• Favicon.ico missing from the res folder.

I know it is not missing so I assume the res folder blocks external read access?

• The link to a Facebook Group is "Forbidden by robots.txt"

The link works so I assume that it is blocked by Facebook?

I guess there is not much I can do about the above and the only way to check for broken links is to trawl through every page on my websites?

Edited by: John-Simpson on 23 Aug 2024, 21:25

On Safari the favicon is shown by

<link rel="icon" type="image/png" sizes="32x32" href="res/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="res/favicon-16x16.png">

The favicon.ico is missing

Just did a quick, simple test, and if an album is hosted on jalbum.net, and it includes its own favicon.ico file, the hosting wipes it out. No problem with the other "species" of favicon - the PNG's, the big Apple/Android ones, and so on.

That's something that Anders will need to address.

It's confounded by the redirect of your mgbreunited domain to your jAlbum account. That's not really behaving itself, either. If I try to go to the home page of that domain, I get redirected to my own profile page on jAlbum. Probably not what you had in mind.

Again, something for Anders.

No. To cover the waterfront, you need only 5 files - 4 favicon variants, and one manifest file.

• A favicon.png, 32x32 px
• An apple-touch-icon.png, 180x180 px
• An Android icon-192.png, 192x192 px
• An Android icon-512.png, 512x512 px
• A manifest.webmanifest file that contains:

{
  "icons": [
    { "src": "icon-192.png", "type": "image/png", "sizes": "192x192" },
    { "src": "icon-512.png", "type": "image/png", "sizes": "512x512" }
  ]
}

The rest are anachronisms, aimed at obsolete browsers (like IE11) or obsolete OS's (like Win8).

No, the jAlbum hosting is actively blocking the favicon. We need to hear from Anders about this.

Here's a little test album. The skin doesn't have to know where the album is going to be uploaded. The favicon, a capital T, is sitting in the project's res folder, so the link is relative.

(demo album removed)

Here's exactly the same album, hosted on my own host:

(demo album removed)

On the jalbum.net site, the favicon is clearly present, but if you try to access it, the server coughs up a 404. See this screenshot from jalbum.net hosting:

(demo album removed)

But now try:

(demo album removed)

It will happily cough up other files from that folder, but not favicon.ico.

What you're seeing on those pages is one of the included PNG icons.

The only one that fails on jalbum.net hosting, consistently, is the one named favicon.ico.

Look at the page code on one of those albums, and try to access res/favicon.ico directly.

I'll wager that Anders can explain it instantly. It's probably an attempt to avoid having Dor replaced. But it's targeting that file name at all levels, not just at the root of the user's jAlbum subdomain.

So, OK to block https://jefftucker.jalbum.net/favicon.ico, but it shouldn't be blocking https://jefftucker.jalbum.net/mydog/res/favicon.ico.

Fixed now!