In Jan 2007 I posted a question about preview files asking if I could split the files into seperate folders, one for each website to make it easier to find files The thread for that question is here Pjay gave me the answer and I have been using seperate folders for each project since, however it is a problem if you forget to change the local publishing address to the right project and end up with the files mixed up again. I don't know if it would be possible to make this a feature in SS by automatically changing the preview files to the correct project folder. What do you think VM Guru's

Tony,

I leave my preview directory alone and use publish to local disk. By using separate publishing profiles for each project (with each project publishing to its own local folder), it provides better control than changing the preview folder.

This also allows me to have separate local folders with associated web sites so when I am satisfied with the project, all I need to do is click the publish to web site button.

OK, thanks for that tip Larry I'll give that a try and see how I get on.

Keep in mind that preview files are different from published files. That may not affect what your are trying to do but you should be aware of it. Preview files let quickly let you see how the pages will work but are not intended to be used as your final files. Published files are internet ready

Preview files group any rendered images in a single sub-directory. Existing images or external files are not moved into the preview folder. Instead, the page links to them with absolute links to their current location on your PC. That speeds things up a bit since there is no file copying. Preview may also add some command to the html page to simulate internet access.

For published files, external images and other files are gathered (if the default gather option is used) and copied to a number of user definable sub-directories based on their file type. The html page links to them in their new location with relative inks (unless absolute links are requested).

Larry,
I have just been testing your way of seperating the files and images in each project and come up against a problem.

I have opened new seperate folders for each project then from the Profile Tab set the Export Destination to Files on Disk, from the Pages Tab changed the Local Publish Directory to "C:\Documents and Settings\T Clayton\My Documents\My IMS Projects\Mysite\ProjectName, then in Path Options selected Gather all Files. My Problem is with the slideshows not working as the "slidshow.js" files are not being published along with the rest of the project, also the images for the Bookflip from DynamicDrive have not been transfered. Am I doing something wrong?

No, this is standard publishing action with SiteSpinner. When you publish to disk (like site publishing), SS does not about external script, CSS, or media/image files. Much like you would need have to upload these files to your site, your would also need to copy them into your local disk folder.

OK. I understand, I was expecting it to do that for me . Thanks for your prompt reply. Tony

Don't forget, if you want you can have SiteSpinner publish an external file by adding it to a page as a Foreign Object with a Format of 'Publish File'. That will copy over the file as long as you have the Publisher's 'Gather' mode turned on.

The file will be placed in the same folder as the html page by default unless you give the Publisher's 'External Files' sub-folder category a folder name.

quote:

Originally posted by Harpo:
Don't forget, if you want you can have SiteSpinner publish an external file by adding it to a page as a Foreign Object with a Format of 'Publish File'. That will copy over the file as long as you have the Publisher's 'Gather' mode turned on.

The file will be placed in the same folder as the html page by default unless you give the Publisher's 'External Files' sub-folder category a folder name.

Huh? Got confused right after the phrase 'Don't forget....'

Harpo,
Don't understand what you mean, come to think of it I didn't understand the relevence of your last post either, can you explain further for us dumbells. Thanks Tony

If you have a file (slidshow.js for example) that you want SiteSpinner include along with the normal SiteSpinner files when you publish, you just need to add it as a Foreign Object.

To have SiteSpinner send the file:

Open the Foreign Object Editor
Open the Format drop-down list and select ‘Publish File’
Browse for the file using the ‘Filepath’ button
Click OK

Make sure you have 'Gather set in the Publisher (pages tab)

There is more on this in the tutorial’s ‘Foreign’ page under ‘Publish File’

TonyC:
My main point on the preview files is that you should not use them as your final online files because they are not quite the same as the pubished files.

Aah, now I understand what you were saying about SS publishing an external file into the project. That's very useful to know. Thanks a lot Harpo.

quote:

TonyC:
My main point on the preview files is that you should not use them as your final online files because they are not quite the same as the pubished files.

Is ther any other difference except that the geometry, images & media are put into seperate files?
Tony

quote:

Originally posted by Harpo:
If you have a file (slidshow.js for example) that you want SiteSpinner include along with the normal SiteSpinner files when you publish, you just need to add it as a Foreign Object.

To have SiteSpinner send the file:

Open the Foreign Object Editor
Open the Format drop-down list and select ‘Publish File’
Browse for the file using the ‘Filepath’ button
Click OK

Make sure you have 'Gather set in the Publisher (pages tab)

There is more on this in the tutorial’s ‘Foreign’ page under ‘Publish File’

TonyC:
My main point on the preview files is that you should not use them as your final online files because they are not quite the same as the pubished files.

By Golly! Here's another secret which was just revealed to me. Or, perhaps, I was the only one who didn't know this, which doesn't really surprise me.

I have several drop down menus which were saved as javascripts. Before the above secret, I would always log into the web server via an ftp program and upload the javascript menu. Now, I can use the Foriegn Object editor and the 'publish file' to upload the javascript file.

I'll bet there are more secrets which will reveal themselves.

The Foreign Object Publish File type can be used to upload your files to your site, but in my experience the files end up in your root directory instead of the indicated sub-folder. So if you like to keep your files sorted into different folders, you will end up logging onto your site anyway and moving the files.

For example, I add a single javascript file to a page using the Publish File object, then publish the page. Even though my settings show that code and scripts are supposed to go into a "code" folder, the script ends up in my root.

The same thing happens with WMV and SWF media files - they end up in the root files instead of the /media folder.

I thought it was too good to be true, I'll give it a try and see if it happens the same to me. I'll let you know. Is this then a bug Harpo? Tony

SiteSpinner doesn't try to categorize the external files. A 'Publish File' will be placed in the Publisher's 'External Files' sub-folder category if you have a folder name there. Otherwise, in will be placed in the same folder as the html page.

So I don't think there is a bug there but don't hestitate to post to the bug forum if you see one.

The only disadvantage to using Publish Files that I can see is that, for now, they don't check if they already exist in the destination folder. So the file will be copied over every time whether you need it or not. That might be a problem for large files. A workaround would be to put all the publish files on one page and only publish that page when you have changed one of the files.

quote:

Is ther any other difference except that the geometry, images & media are put into seperate files?

Yes. Existing images or external files are not moved into the preview folder. Instead, the page links to them with absolute links to their current location on your PC. That speeds things up a bit since there is no file copying.

Preview may also add some command to the html page to simulate internet access

I just deleted the slideshows.js file from a site and then put it back in with the Foreign Object Editor, it did put it with the other html files so that is fine.

Thanks for that Harpo it will be useful for the future.

Larry, are you setting your "External Files" in the Publisher > Pages > Sub Folders to point at some other folder other than the default blank (which means the root folder)?

All files of format "Publish File" will go to this folder, regardless of extension.

Following are the relationships between the Foreign Object Format type and the Publisher Pages > Sub Folder. This sets the folder for the published Foreign Object:

Foreign Object ->  Publisher Pages > Sub Folder
==============================================
Publish File    -> External Files
General Plug-in -> Plugins, Java Files
HTML (IFrame)   -> Embedded HTML Files
SVG             -> Embedded SVG
Java Applet     -> Plugins, Java Files
Shockwave       -> Embedded Flash Files
Flash           -> Embedded Flash Files
Quicktime       -> Video Files
Realaudio       -> Sound Files
Video           -> Video Files
Sound/Music     -> Sound Files
Other File Type -> Other Foreign Objects

The publisher pays no attention to file extension. The Foreign Object "Format" sets the publish placement. Note the "Other File Type" -- this offers an independent file placement to "Publish File".

So if you want your Foreign Objects to go to particular folders:

Set the Foreign Object "Format"

In the Publisher > Pages > Sub Folders (don't overlook the "Use More Categories" checkbox) set the matching Sub Folder name.

Harpo, some suggestions for improvement:

Could the Foreign Object Format names exactly match the Publisher Sub Folder names -- this avoids doubts about where particular files go.

Is there any need for the two Flash categories (Shockwave and Flash) and the two Java Categories (General Plug-in and Java Applet)? They generate the same code and seem equal in all respects.

In the Foreign Object > Format list could you add "Code" (for Javascript and PHP etc).

I do not see any real difference between a Publish file going to an "External Files" directory vs the root if you have more than one file type to upload. I often have .css, .js and .php files that need to be uploaded to their respective folders, and occasionally a .swf file. But most likely I am the odd duck so this doesn't effect anyone else.

This is one area I feel VM needs to improve. The programs (SS & WE) are great for creating web pages, but not so great at building web sites. There is often a lot more than just HTML that makes a web site. But you really need to use an external FTP program to add all the other files required for your site.

I would like to see the Publish File type removed from the Foreign Object select list and expanded in the Publisher. Something like a table which would allow me to include external files from my computer, specify where they should be uploaded and a check box to allow me to select if they should be published.