When I create a new album with Tiger I import the Settings from an existing album. All settings are import except one.

Settings > Tiger > Site > Top Bar > Logo > My_Logo.jpg

The Settings shows that My_Logo.jpg populates the logo box.

But the file doesn't exist. If I compile the album, the top bar, where the logo should appear displays ?.

If I go back to Settings and manually import My-Logo.jpg, and re-Make album, everything is OK.

My_Logo.jpg should reside in the res folder.

Am I missing a setting.

Thanks,

PeterB

This is a poor implementation. Unfortunately, jAlbum does not know which files to import from the other album, besides the skin settings. I'm not sure if we can come up with something better. The only way to resolve this issue is to copy the contents of the old album's "res" folder (Ctrl-Shift-I / res) to the new one.

It gets much more byzantine than this.

In my skins, I don't use the res directory to store things like logos. I use David's DiskCache() method. This has several advantages.

First, it's invisible to the user, so he doesn't say, "Hey, what's this res thing in my project," and then deletes it.

Second, it cleans up after itself. If the user decides to use a different logo file, the old one isn't then hanging around, getting copied into each album along with the new one. I've seen res folders in the output of Tiger albums that contain the entire history of the user's choices of things like logo and background images!

ETA: Third, cached files survive the deletion of the original. On a subsequent album build, it looks for the original, and if it finds it, it uses it, and replaces the cache copy. If it doesn't find the original, it just uses the cache copy. Handy, if the original is modified or replaced - you don't need to remove it and re-add it to the project.

The disk cache does not, however, get copied to the lifeboat.zip file. I'm thinking it probably should.

What's stored in the project file are the name of the logo file, and the full path to it.

So, when importing, what should be brought in? Of course, that's different if the import is being done from the project file, or from a published album. The project file is more likely to be the user's own project (though he might have grabbed the lifeboat.zip file from the web, and gotten the project file from that - might be his, or someone else's). Importing from a published album might also involve the user's own project, or someone else's. So, the full path to the original logo file might or might not be valid. What gets imported is also modified by what's in the preventCopy entry in skin.properties.

Because of all of this, whichever technique is being used to stash things like logo files, a user is often better off using Duplicate project instead of importing settings. Copy the entire project, delete the album objects in it, and add new ones.

Related, for site aware skins, I allow for users to save/load default settings for templates like About.htt and Contact.htt. Either or both of those could be common to every project by a specific user. It saves a lot of copy and paste or manual entry.

Yes, I will remove the import of these settings.