[Pro] One or more html files... will be overwritten

I see this problem has been occurring and it has now happened to me a second time.

Recently I had to completely rebuild a 300 page site as I could no longer get the site to publish.

Now, a different site I manage is experiencing the same problem. I can save the file, but the site will not publish. I keep getting the message “One or more files which do not belong to this site will be overwritten. Do you want to continue?” Then FW crashes.

I have tried all of the solutions on this site. I thought I finally got rid of the offending page by applying a new master then deleting the master as what I thought the offending page was could not be deleted. But I was wrong - now the next page in line is doing the same thing.

If I have to rebuild this 264 page site I will not only go crazy, but will be looking at learning a new web page design program.

Any suggestions? I’m using a MacG5, OS 10.4.11, FW 5.4.1.


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

Are you 100% sure you are publishing to a site folder that is
only for this individual site? And not sharing the site folder
with another Freeway File? Freeway knows if this is the case and will
prompt you.

If you are not sure, try creating a new site folder and publishing to
that new empty folder.

David Owen ::
Freeway Friendly Web Hosting and Domains

On 13 Sep 2009, at 8:54 am, Mickey Bee wrote:

I keep getting the message “One or more files which do not belong
to this site will be overwritten. Do you want to continue?”


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

Try creating a new Site Folder and publish to that:

Gpt to File > Documaent Setup… and click the Select button. Make a
new folder, close and publish/upload the site.

This will not affect you original files.

Colin

On 13 Sep 2009, at 08:54, Mickey Bee wrote:

I see this problem has been occurring and it has now happened to me
a second time.

Recently I had to completely rebuild a 300 page site as I could no
longer get the site to publish.

Now, a different site I manage is experiencing the same problem. I
can save the file, but the site will not publish. I keep getting the
message “One or more files which do not belong to this site will be
overwritten. Do you want to continue?” Then FW crashes.

I have tried all of the solutions on this site. I thought I finally
got rid of the offending page by applying a new master then deleting
the master as what I thought the offending page was could not be
deleted. But I was wrong - now the next page in line is doing the
same thing.

If I have to rebuild this 264 page site I will not only go crazy,
but will be looking at learning a new web page design program.

Any suggestions? I’m using a MacG5, OS 10.4.11, FW 5.4.1.


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


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

Yes, I have created the new folder, set it up in Document Setup and I still get hung up after 8 pages are published. I will try deleting what now appears to be the offending page.

I wish I knew what happened - I was so pleased yesterday with how smooth FW was working, and just as I was finishing some major redesign with some new rollover buttons I created, it did this.

I have had to take the site down from the server and am working frantically to fix this problem before the client notices the site is down. And, of course, none of this is paid time.


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

Sometime around 13/9/09 (at 13:20 -0400) Mickey Bee said:

Yes, I have created the new folder, set it up in Document Setup and
I still get hung up after 8 pages are published.

Does this happen the FIRST time you publish into a new folder? There
should be nothing at all in that folder to begin with.

And please tell me this: are you placing anything from within the
Site folder into any pages in Freeway? This is an absolute no-no. Do
NOT touch the Site folder or use anything from inside it. Freeway
will delete and remake anything in there whenever it wants, as part
of keeping your site output absolutely up to date. So if you try
placing one of those images in your layout, Freeway will try to
replace it when you next preview/publish/upload, then not be able to
find the item placed in your page because it has been replaced…

k


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

Yes, it happens the first time I am trying to publish into a new folder. And, no, nothing from the Site Folder has ever gone into any FW site I publish.

I am getting the feeling it may have something to do with fonts… I did make one change just before this all happened. I ran, under Edits, Fonts…, and the program told me I didn’t have a substitute font selected, so I chose a generic font (Helvetica). I have just gone through all my Styles and selected helvetica as the main font (it was Verdana) and have managed to save the document. Before I try to publish again I am going through each of the pages to see what won’t load and make the program crash and try to delete those offending pages.


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

Long shot - open Disk Utility (in the Utilities folder, which is in
the Applications folder) and repair permissions. It can’t hurt, and
it might possibly help. But this is a long shot.

k


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

It is fonts - and apparently a bug in the program.

I went through all the style sheets, changed all instances of fonts to helvetica, removed all graphic font styles, removed the offending page (which required making a new master, applying all instances of pages with the previous master of the offending page to the new master) and then deleting the original master which effectively deleted the offending page. FINALLY, I could publish into yet another new folder and the site is now live.

This was due to my impression a substitute font had to be selected.

Six hours total of extra (unbillable) work because there is apparently a bug/flaw in the program.

GRRRR>>>


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

Six hours total of extra (unbillable) work because there is
apparently a bug/flaw in the program.

GRRRR>>>

Grr indeed, from your description. But when you say apparently a bug,
how did you arrive at this? And what was the bug? I’m not trying to
be a software apologist, but if you don’t know the cause with
absolute certainty how can you know how to avoid it?

I should add that I’ve never had this problem, and I’ve been using it
for… well, let’s just say ‘quite a while’. :slight_smile: I think it would be
wise to keep investigating and perhaps ask for ideas from the others
here.

k


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

Well, if I recall the first time this happened to me, it also had to do with fonts. I had a few temporary styles hanging around and attempted to delete them and clean up by reassigning permanent styles. This completely screwed up the whole site and I ended up with the same problem and eventually rebuilt the site.

Something is weird somewhere. Maybe its something I’m doing, but I’ve been using Freeway for many, many years now and don’t believe it’s a coincidence it’s happened two times recently.

Anybody else have an idea as to why so I can prevent this from happening in the future? One thing I know for sure is to be more careful with fonts.


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

Sometime around 13/9/09 (at 19:11 -0400) Mickey Bee said:

Well, if I recall the first time this happened to me, it also had to
do with fonts. I had a few temporary styles hanging around and
attempted to delete them and clean up by reassigning permanent
styles. This completely screwed up

I’m a little at a loss as to how a font issue would cause an alert
such as the one you described. That is specifically because Freeway
sees a file that it wants to overwrite but believes that it isn’t
from the site document it is currently publishing. Full stop.

This alert leading to unexpected behaviour such as the crashing you
experienced seems like it then isn’t able to overwrite the file for
some reason, either because it is locked or marked as in use, because
of a permissions error in the file system, or because of an actual
disk problem.

So - one step at a time. That new folder you’re publishing into. Is
it brand new and was it definitely empty? And you definitely picked
it in the Document Setup dialog?

One thing I know for sure is to be more careful with fonts.

Oh yes - do you use a font manager? Had you changed anything to do
with oyur fonts?

And have you run the Repair Permissions process yet?

k


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

First thing I did was run Disk Utility and rebooted the computer.

Yes, I use a font manager, but that is not the problem.

I created a new folder and it was definitely empty.

I base my conclusion about fonts and a bug in the program on the solution I managed to create to solve this problem.

It was revealed when I went through the styles after adding the “substitute font”, I discovered in the Style dialog box the Font was different than the Graphic Font. Once I rectified this, the problem solved itself.

So, in conclusion, I am of the opinion there is a bug within the program as the alert box notifying me of files being overwritten has nothing to do with what the final solution was.


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

So, in conclusion, I am of the opinion there is a bug within the
program as the alert box notifying me of files being overwritten has
nothing to do with what the final solution was.

It may be a bug, but I really wouldn’t call it that on the evidence
so far. What this tells me is that we haven’t found the source of the
problem. Sorry Mickey, but I’ve been troubleshooting Mac apps since
the 1980s and I really wouldn’t care to draw a conclusion this
absolute on the evidence I’ve read.

The process you described on the 13th still confuses me slightly. Why
did you first go into the Edt > Fonts dialog? It did sound like your
problems started then. Please excuse my repeated prodding, but I
don’t feel like we’ve reached the bottom of this.

k


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

I started this process after reading the “Accessibility” report I generated under the File menu. I then accessed the Font Sets under Edit and edited the font sets in there to add an accessibility font.

This is when the problem started. It was not apparent at first, but I continued to work on the document and when I went to publish the site (after saving) is when I first got the “One or more files will be overwritten” problem. I didn’t associate the two events at first.

Nonetheless, after spending a number of hours trying different fixes (running Disk Utility, rebooting, removing what I thought were offending pages, saving to new folder, etc.), and then having a night to sleep on it, I thought I would check the Styles and sure enough, when I opened Fonts under Edit, I noted my styles dialogue boxes featured two different fonts - as described above. Once I corrected all of that, reassigned a different font to text throughout the document, redid all the pages affected by the change in text flow, saved and then published to yet again a new folder, all works.

If this isn’t a bug, then what is it??


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

Sometime around 14/9/09 (at 18:17 -0400) Mickey Bee said:

I started this process after reading the “Accessibility” report I
generated under the File menu. I then accessed the Font Sets under
Edit and edited the font sets in there to add an accessibility font.

What is an ‘accessibility font’? The font sets used there are meant
for normal use; they’re ‘web-safe’ (meaning they are found on
virtually every Internet-connected computer) and they are for the
most part exceptionally clear in normal use.

Could you describe exactly what you did, leaving nothing out? Which
menu item did you choose and what exactly did you do in whatever
dialog window that opened?

Also, could you verify where exactly the Freeway document is saved
and what it is called, exactly and completely? Also (#2), where do
you store images and other media that you use in this Freeway
document?

when I opened Fonts under Edit, I noted my styles dialogue boxes
featured two different fonts - as described above.

I apologise, please call me thick. Could you describe it in more
detail? I’m afraid I still don’t get it…
When you choose Edit > Fonts you get the Edit Fonts dialog, where you
can select a font and replace it with something else.
When you choose Edit > Font Sets you get the Edit Font Sets dialog,
where you can work with the font sets that you use to format HTML
text.
When you choose Edit > Styles you get the Edit Styles dialog, where
you can edit existing styles and create new ones.
It isn’t possible to see more than one of these dialogs at once (that
is the nature of modal dialog windows), so we need to know exactly
what you do. Otherwise confusion reigns and nobody can be sure what
anyone else is actually describing.

If this isn’t a bug, then what is it??

Unclear at this time. It may be a bug, it may be something else. To
ensure both short and long-term peace of mind it is important to
understand the behaviour absolutely.

k


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

Well, friend, you are asking for something that will be taking even more of my time to explain.

When the Accessibility Report was generated, there was a line referring to Styles stating “Font Set does not contain a generic alternative”. As a result I selected under Edit “Font Sets”. In that dialog box, one has an option to select the font and Edit. As my website body text was mainly using Verdana, I selected that font set and edited it to include what I believed was a generic alternative. I thought maybe everybody didn’t have Verdana and I should select a more common font, Helvetica. That is where I made my downfall.

By doing so, this apparently confused my Styles, as when I finally looked at the Styles (under Edit), I noted each instance of where I had selected an alternative font, that font name would appear in the pop up menu (with Graphic written to the right) under the Font pop up menu. At this point I decided to change all instances of Verdana to Helvetica and made certain both the Font and the Graphic Font were the same.

Does this help clear the confusion?


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

Sometime around 16/9/09 (at 11:09 -0400) Mickey Bee said:

Well, friend, you are asking for something that will be taking even
more of my time to explain.

I know, and I apologise. But the facts must be established…

When the Accessibility Report was generated, there was a line
referring to Styles stating “Font Set does not contain a generic
alternative”. As a result I selected under Edit “Font Sets”. In that
dialog box, one has an option to select the font and Edit. As my
website body text was mainly using Verdana, I selected that font set
and edited it to include what I believed was a generic alternative.
I thought maybe everybody didn’t have Verdana and I should select a
more common font, Helvetica. That is where I made my downfall.

Had you created a new font set at any time? That’s the only way I can
get that warning to come up in the Accessibility Report. All that
means is that the font set font list doesn’t end that particular Font
Set list with the generic sans-serif or serif names.

Actually, Verdana could be more common than Helvetica these days. But
anyway… I assume you set your web site body text as Verdana using
the Inspector palette, or perhaps from the Style > Font menu? This
actually applies a font set, so the output code will automatically
be set with a cascading list of different fonts; Verdana, then Arial,
then Helvetica, then the generic ‘sans-serif’.

It sounds like you may have created a whole new collection of font
set entries, each only containing one font, which would explain why
you had a load of new items in the Inspector’s typeface menu.

By doing so, this apparently confused my Styles, as when I finally
looked at the Styles (under Edit), I noted each instance of where I
had selected an alternative font, that font name would appear in the
pop up menu (with Graphic written to the right) under the Font pop
up menu.

In the Edit Styles window, where you see a second typeface option
(containing the full font menu) and the label “Graphic” to its right,
this is the font that will be used if you apply that style to graphic
type. But it doesn’t affect HTML text at all. Try setting the View
menu in that dialog to CSS Attributes rather than CSS and Graphic
Attributes. Then you’ll only see settings that affect HTML styling.

At this point I decided to change all instances of Verdana to
Helvetica and made certain both the Font and the Graphic Font were
the same.

Understandable. Not really something that would help, I don’t think,
but quite a reasonable assumption at that point.

At this point, please check your font sets to make sure they all end
with either sans-serif or serif. Then you should never see that entry
in the Accessibility Report again.

What I don’t see is where this relates to the publishing problem.
That is specifically related to file creation and permissions - which
is why I didn’t (and still don’t) think that the problem relates to
your experimental work with fonts and styles.

k


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