MarkVerlander

Built a blank master template to use for this project and future projects. Works well, and am getting used to fluid engine. Asset library functioning well with smaller library of assets.

Thanks for the quick response Paul and the helpful advice. Makes sense, and unfortunately a very time consuming lesson for me. I tried duplicating the new website I just made, hoping that only the images used in the new site would be transferred in to new Asset Library. However, the *thousands* of images from the original site still transferred, even though they are not in use. This seems like something that Squarespace could program a fix for. As well as the Asset Library function lag, error messages and crashes. Not a fan of the new Asset Library feature in it's current state.

This week I used the "Duplicate Website" option on an existing website build to create a quick new website for a client on a budget. The duplicate website function worked great, the new build was easy, and the client loves it. I was just about to hand over the new website to the new client, and happened to check the "Asset Library NEW" section. I'm so glad I did, because the Asset Library contained not only the images from the new build, but *thousands* of images from the original client website that was duplicated. Obviously I can't deliver a new website to a client that has *thousands* of another client's images. I tried to delete the images, however the Asset Library interface is has terrible lag, and freezes up with error messages every time I try delete an image, and completely crashes if I try to delete several images at the same time. This problem occurs regardless of which browser I am using, Chrome, Firefox or Safari. I now have *thousands* of images to delete manually. My only option is to rebuild a new site from scratch for the new client. In this case, the new Asset Library section has been a terrible waste of time for me. Asset Library should be an *option* for users to turn off or delete when needed.