I’ve posted in regard to this before, but have a question:
I had a FW site folder inexplicably corrupt an action and there is no easy fix. Right now my only option is to rebuild from an archived copy of the site folder saved prior to the corruption, which would be difficult.
Alternatively, is there any way for me to download my working files – an entire site’s worth – from my server and associate them with a new FW site folder? What is online now was not affected by the errant action.
Ideally, I’d like to be able to pull everything down into a new site folder and carry on as if nothing happened.
The Freeway document is the only thing that can be opened and edited
in Freeway itself. The contents of the site folder are an artifact of
that document, and do not have any bearing on what you see in Freeway.
Think of the Freeway document as a Word file, and the contents of the
Site Folder as the paper pages that spill out of your printer when you
press Apple - P.
Do you have the fwbackup file that Freeway creates each time you
successfully re-open the document? Or do you have a backup copy of the
freeway file?
Walter
On Jul 29, 2010, at 5:37 PM, wireguy wrote:
I’ve posted in regard to this before, but have a question:
I had a FW site folder inexplicably corrupt an action and there is
no easy fix. Right now my only option is to rebuild from an archived
copy of the site folder saved prior to the corruption, which would
be difficult.
Alternatively, is there any way for me to download my working files
– an entire site’s worth – from my server and associate them with
a new FW site folder? What is online now was not affected by the
errant action.
Ideally, I’d like to be able to pull everything down into a new site
folder and carry on as if nothing happened.
The files that are on your server are FW generated HTML files which were produced from your yoursite.freeway file.
This is a one way process.
You can try using FW’s Import HTML option but results can be very hit or miss.
Have you tried selecting a New site folder in the FW doc setup section and tried publishing into that to see if it works? ie ‘yoursite2’
Does this problem affect all your pages? If only 1 or 2 then you could delete them and rebuild them using a screenshot of the page as a background image/template.
SP towers have an article about the quickest/easiest way to rebuild a site from scratch in their Knowledgbase section.
I will have a look and see if I can find it but if you can give us a bit more detail as to what is going wrong we might be able to offer more specific advice.
For the current files that are working and online I do not have an associated fwbackup file. If I read you correctly, when my “site folder” corrupted what happened was both the fwbackup file itself (and consequently the output documents) failed.
I have an archived copy of the fwbackup file (and documents) from a good bit prior to the corruption that I’d have to rebuild from, but are unaffected.
Not to mention I manually edited a few of the online pages in the interim via Coda, so that inevitably made them rogue.
OK, Walt, thank you very much for the help. I wasn’t aware of the direct I/O relationship between the fwbackup file and the output documents.
I’ll just rebuild and be done with it. Probably will give me the opportunity to refine, anyway.
Dave, this was the site where the HTML 5 action went awry and would no longer allow itself to be activated. For whatever reason – I don’t have the time to figure it out – the action can no longer be applied to any FW document, new or old, in that particular file.
I didn’t know the extent of the one-way road with the fwbackup file, so that pretty much relegates me to a rebuild.
Thanks for the response. I’m just going to do it straightaway and stop whining.
What is foiling me is that the only intact up-to-date files I have are the ones on my server and not associated with any fwbackup file. They were published just prior to the corruption.
The only active fwbackup files I have is the one associated with the corrupted HTML 5 action (that was rendered useless) and the archived copy that’s a few revisions behind where my published site is.
Now what I will try to do is republish the corrupted file into a new site folder to see if the HTML5 issue carries over…it is about the only thing I haven’t tried yet.
Can you send this document to our support team please? support(a)softpress.com
Many thanks and apologies if you’ve done this already,
Joe
On 29 Jul 2010, at 23:10, wireguy wrote:
Dave, this was the site where the HTML 5 action went awry and would no longer allow itself to be activated. For whatever reason – I don’t have the time to figure it out – the action can no longer be applied to any FW document, new or old, in that particular file.
I didn’t know the extent of the one-way road with the fwbackup file, so that pretty much relegates me to a rebuild.
Thanks for the response. I’m just going to do it straightaway and stop whining.