Alex,

When the install program "backs up" the templates directory, it doesn't move/reinstall it.

But, when the program backs up the associated /build_root/images directory, the "images" directory itself is moved -- given a .bak extension, then a new images directory is created.

The problem is, the new images directory doesn't have the same permissions as the old one (most likely), _and_ bigger issue, is that it doesn't have all the other subdirectories that might have been added to run other plugins, or to handle special graphics.

For this reason, Links should put all it's images in subdirectories, then just rename the subdirectories it's replacing -- in this case -- default/av/snap/yahoo, in the next release, simple as well.

This may cause a problem, with multiple upgrades, and maybe the version number should be appened ... .204.bak would be the back ups made by the 204 install. Intermediate releases would be 204a.bak, or 205.bak

I had a bit of time trying to figure out why the plug-in installs suddenly quit working, and while my error message wasn't completely accurate, the real problem was that I assumed my local image directory paths were still there, but they had been removed when the "images" folder was renamed.

Also... you might want to check the <%build_images_url%> parameter during the install, and check to see if the template directories are installed at that location, rather than assuming "<%build_root_url%>/images" which is what it seems to be doing. It would prevent having the images installed into the wrong area on some (most?) sites.

It might be working this way now, but I'm pretty sure one of the sites I just upgraded had the images moved to the same level as build_root_url (so that image links resolve as build_root_url/../images) and the graphics directories were still installed to build_root_url/images.



PUGDOG® Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum