The site folder will be empty until you publish or preview the page.
Open the FW doc and see if it works on preview and publish for you.
If it does then you can examine the structure and duplicate it on your page(s)
Alternatively you can copy the whole page and paste it into your FW doc. You can do this by selecting the page in the LH sidebar when you are viewing in Site View - Edit>Copy then with your existing doc open select the Site Folder (in the LH Sidebar) and Edit>Paste
I knew very little FW when I first made this site. I’m wondering if I have some inherently fatal flaws in there, though it did work before the upgrade.
One thing to try – no matter what else you try – is to create a new page (and document) entirely within Freeway 6. Don’t copy anything at all from your original FW5 document, just draw each new element one at a time. There may be an issue with the upgrade code that runs when a FW < 6 document is opened for the first time in 6. The only way to figure this out is to see what happens when you don’t engage that upgrade method at all.
I knew very little FW when I first made this site. I’m wondering if I have some inherently fatal flaws in there, though it did work before the upgrade.
No matter which HTML level you choose, Freeway will write valid code for that level. Individual Actions may vary in their ability to stick to the standards, but the code that Freeway writes by itself will be correct. As long as you write valid code, no matter what level, the browser has no excuse to screw it up. All modern browsers support XHTML 1 and HTML 4 and 5. This choice doesn’t matter at all.
Walter
On Dec 18, 2013, at 11:23 AM, Joe wrote:
Would it be better/safer if the new doc is HTML5 or 4 or whatever these days?
Well there is nothing on that page to link the javascript code.
Did you copy the whole page as I suggested? (not just select the items on the page)
You can do this by selecting the page in the LH sidebar when you are viewing in Site View - Edit>Copy then with your existing doc open select the Site Folder (in the LH Sidebar) and Edit>Paste
Did you try the standalone FW document I sent you?
And please make your page output code More Readable
I did follow your instructions to add the page to my existing file. Upon uploading I got an error message about missing resources. Please see the screen grab at http://bringyourface.com/untitledpage.html for a look at the error and my other settings.
Not sure if it changes anything. I also got a similar error message (just the bottom one on untitled page) when I opened your file as standalone and tried to preview it.
I didn’t want to tamper without running it by you, Dave. Don’t want to make things worse, but i’m not sure if this explains the problem or not.
Don’t want to make things worse, but i’m not sure if this explains the problem or not.
The Missing Resources Error is a common message and one you will come across regularly if you move files around between drives etc.
It is also easy to fix.
Go to (in the main FW Menu) Edit>Resources where the dialogue box will show you a list of all the resources used in your FW document and their status.
Pay particular attention to the ones marked as Missing in the Status column.
Select the first of these and then choose Edit from the Button in the bottom right corner.
In the subsequent window there are 3 main options Resample Update and Locate.
Choose Locate and then a Finder like window will open to let you choose the Missing file from its location on your Drive.
Finding one file may be enough for FW to then locate any other missing files (especially if they are in the same place)
But repeat the process for any other missing files.
NB - it is good practice to keep all external files that you are going to use in your FW doc in the FW created Media Folder whether they are images or movies or whatever. If you dont want to put your original files in there then copy the originals and place them in there and then reference them from within the FW doc.
Now that you have updated the Resources the file should Preview/Publish without error.
If you haven’t already done so also download and install the External Javascript Action from the Forge External JavaScript - ActionsForge
I’m not sure why Ext JS didn’t work the first time, but it’s all working now. What a relief. Thanks and Happy Hols.
Last question (which is part of my confusion and why I didn’t want to tamper): What does the # in the Edit Hyperlink panel do that replaces entering a longer hyperlink?
Is the Graphic Link to File action able to link to my online folder of enlargements already on the web (Resources/enlarges/whatever.jpg) or does it only use files from my computer? Is it then putting them in a web file somewhere? I’m trying to get a handle on that.
If you just want to link to a file that is already up there then you shouldn’t need GLTF - just try using the External Link section of Edit>Hyperlinks.
I know it didn’t work for you before but I would like to see if it does now.
Maybe duplicate the original page, remove all the old stuff and try again with new links and the external js action.
Any map areas are not my creation. I double checked to see that Ext JS had added jquery and main js files to my Resources web folder with Fetch FTP. Then I selected the images, applied Graphic Link to File to files on my computer (after failing with direct links to web folder images on a previous document) and used Cmd + K, #, class/preview in Extended.
Let me know if you find Gremlins doing their dirt. That’s what I suspect.
After much head scratching I think I have found the cause of the Map Area creation that upsets the links and stops the preview javascript from running.
On the NewPixPage change the border colour on Stasia and Taylors pic to none (2nd pic on 1st row)
Now preview in your Browser.
In my tests the border style/colour forces FW to create a Map Area and shifts the link to the Map Area. Top code block is without a border colour.