Replace it with this one, attached.

Make sure the project is closed when you delete the old one, and add the new one.

If you start anew project by copying and older project, such as by:
JAlbum>Menus>File>Duplicate Project
JAlbum>Explore>Projects pane>Contextual Menu >Duplicate project
Or outside of jAlbum duplicating a folder and renaming it.

Then copy or duplicate project 68, the one just fixed, don’t use any other project.

This is leftover from a problem that the core fixed over a year ago. When adding a page template, the core was keeping that information as an absolute path. But that path might have been pointing to the bundled skin, or to a later-installed skin version in the config directory. So, this could get broken. In this case, e.g., the path was pointing to the config directory copy of the skin. But after an update, the user deleted that config directory copy of the skin (which is OK), so the path was no longer valid.

This got fixed in jAlbum 20.2, I believe. The path to a page template now points to the most recent copy of the skin, no matter where it is. So, for a newly-created project, it's not an issue. But in this user's case, he's apparently starting a new project by copying an old one. That's a reasonable thing to do, since things like his contact and about pages aren't changing. He's just swapping out the photos for new ones, from the latest "event" that he's covering.

But since he's copying an old project, in which the old absolute paths are still present in albumfiles.txt, they're never getting fixed. The old error just keeps getting copied into the newest project.

This is not something a skin should be trying to fix. This is a jAlbum core thing. It's kind of a fringe case, however, so a core-based fix might be more trouble than it's worth.

Thanks, Jeff!