Background Supersizer from a shared folder

Freeway
1

I have a site that just gives information and a booking calendar to
those who jointly own a holiday apartment. Nothing complicated - just
pages with the required information with some local images as
background. Just over a year ago I added the Background Supersizer
action to most of the pages.

I work on a 27" iMac with 24" second screen and a 17" mbp and
sometime in the last year I started another site in a shared folder
using Hightail (a Dropbox-alike) so I could easily do minor changes
from the mbp in the living room without having version problems. I
also moved the then latest holiday property site entire tree to the
Hightail folder, but didn’t make the changes I had intended to make.
By ‘entire tree’ I mean a site-named folder containing: a media
folder with all the images, another containing pdf docs, the FW
document and its backups, and some Showcase documents. The site
refers to nothing outside the site-named folder.

Last week I made a change to the holiday property site and all the
backgrounds disappeared totally. I did have to re-generate a Showcase
slideshow within the Hightail area, but that worked fine. Removing,
publishing, re-adding and force re-publishing the B-S pages didn’t
bring the backgrounds back. No backgrounds at all.

I then duplicated the entire site tree from the Hightail folder back
into a new unshared folder on the mbp, published and uploaded. All
works properly.

Is there a problem with keeping FW data on such a shared folder?
Another site works fine from the shared folder, but that one doesn’t
use B-S. So far it’s only the B-S action that fails. Only one copy of
FW open at a time of course.

Ideas? No link, because it currently works fine.

David

–
David Ledger - Freelance Unix Sysadmin in the UK.
email@hidden
www.ivdcs.co.uk

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

2

I’ve no idea at all and I’m pretty sure you inspected this in the browser. Have you had an eye on the error message regarding the missing resources:

Just a guess:

naming woes such as:

missing backgroundimage-supersize1b or something like that and compare it with the name in the resource folder - which could be theoretically backgroundimage-supersize1 (for whatever reason).

Empty the resources folder and/or force publish (all).

But - dear David - this is just a shot into the dark.

Cheers

Thomas

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

3

On 10 Apr 2015, at 09:25, Thomas Kimmich wrote:

I’ve no idea at all and I’m pretty sure you inspected this in the browser. Have you had an eye on the error message regarding the missing resources:

Just a guess:

naming woes such as:

missing backgroundimage-supersize1b or something like that and compare it with the name in the resource folder - which could be theoretically backgroundimage-supersize1 (for whatever reason).

Empty the resources folder and/or force publish (all).

But - dear David - this is just a shot into the dark.

Cheers

Thomas

Thanks

When I get time I’ll revisit this and upload to a different area so it doesn’t matter. FW showed no errors at all, and all resources were found at publish time (once I’d fixed the slideshow image location).

Regards,
David

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options