This is sort of odd to me. I have a folder of images on my desktop and I want to use them for both background images and also as regular images where if someone clicks the link, the image opens another window and opens the full size image.
No problem using the images in the folder as background images, but when I use the hyperlink to link to one of these images, it does not put the image where it needs to go so that it uploads. It works fine on the preview in the browsers, but does not upload, those the same images when used as a background image on the web show up fine and I get a 404 for all this image file links I have made.
Do I have to bring the images in somehow internally? And as far as internal options, it only seems that I can choose another page. The weird thing to me is why the background images from the same folder can be found by Freeway and uploaded properly, but not otherwise?
Are you specifying an URL for the image?
That’s the only way I can understand what you are saying.
Linking to an absolute address will work if the file at that address (in
this case on your HD) is accessible from the internet.
I normally make a graphic box on a page and import an image (or drag and
drop into image box from Media folder). And I often use Spawn new window
action for a sized uncluttered window for images.
hope this helps
regards
Brian
Rgator said recently:
This is sort of odd to me. I have a folder of images on my desktop and I want
to use them for both background images and also as regular images where if
someone clicks the link, the image opens another window and opens the full
size image.
No problem using the images in the folder as background images, but when I use
the hyperlink to link to one of these images, it does not put the image where
it needs to go so that it uploads. It works fine on the preview in the
browsers, but does not upload, those the same images when used as a background
image on the web show up fine and I get a 404 for all this image file links I
have made.
Do I have to bring the images in somehow internally? And as far as internal
options, it only seems that I can choose another page. The weird thing to me
is why the background images from the same folder can be found by Freeway and
uploaded properly, but not otherwise?
Linking to an image does not mean that it will be uploaded to your server. In fact, if you link to an image on your computer, it will work – just only on your computer and nowhere else.
What you need to do is guarantee that these images are uploaded to your server. There’s a couple of ways to do this.
You could use an FTP/SFTP application to upload all of the images to a sub-folder on your Web server, then make all of your links manually using the Hyperlink dialog. (If your files are in a folder called images, then you would enter /images/filename.jpg in the URL field, or a complete URI to the file like http://yourserver.com/images/filename.jpg ) This is tedious and the potential for error is high, but where it will save you time and trouble is if the images are large and many – you don’t want to have Freeway decide that they are all due for an update on the server and force you to wait a half-hour for your site to finish uploading.
Another more automatic way to do this is to create a new page for each picture. If they’re all the same relative size, this can take moments to do (set up a Master Page just for these, and put a picture box on the page ready for drag-and-drop or File / Import). Then, your links will simply be to those new pages, and you’re all set. Freeway will manage the upload of the images, there will be an unambiguous workflow, with nothing left outside of Freeway’s realm for you (or it) to forget to do.
Perfect answer, thanks. Unlike other programs like DW, GL and I think RW, Freeway does not automatically bring an image or file into the subfolders of the site on your hard drive. With these programs, all you do is link to an image via the Mac Finder ANYWHERE on your Mac, your external drives, or anywhere. Link it once like that and that file IS COPIED into the site and you never worry about it again. I expected the same ease of use of those three programs with Freeway. It is sort of a silly and user UNFREINDLY the way that it is done in Freeway, more work, less automation. Of the two choices, I would go with the first, but what a darn hassle! I expected Freeway to be more convienent and user friendly than this!
Another thing that I have been worried about is not being able to create the subfolders that I like to use for SEO purposes. Walter’s first suggestion is the best way for me to make the multiple subfolders that I WANT to be seen in the URL and not have Freeway stop it.
The longer you can make an URL string loaded with key words, the better. That means using some subfolders to help. I’m very, worried about losing SEO qualities by using Freeway. (Which is why I won’t use tables.)
But certainly, as far as files are concerned, Freeway does have a quite primitive way of handling them. Not elegant and easy like its competition.
I’m very, worried about losing SEO qualities by using Freeway.
(Which is why I won’t use tables.)
Fair enough, don’t use tables. But DON’T - please - believe that
tables cause problems with SEO. I’ve researched this area at
reasonable length. First of all, (a) there’s no logical reason in
technical terms why tables would harm SEO unless they were so
horribly convoluted that they fragmented actual sentences! And
second, (b) Google has said explicitly that tables are not a factor
in page indexing.
The longer you can make an URL string loaded with key words, the better.
To an extent. Although those tricks can only every be really
effective when they support more fundamentally good SEO practices,
namely having content that’s structured in semantically clear ways.
But anyway, other than the length of the name (which can at least be
extended to 31 characters in the Document Setup dialog), are there
further problems you’re having with folders?
With these programs, all you do is link to an image via the Mac
Finder ANYWHERE on your Mac, your external drives, or anywhere. Link
it once like that and that file IS COPIED into the site and you
never worry about it again.
In a sense, this is exactly what DOES happen when you use an image in
your Freeway document - but you can’t just make HTTP-oriented links
as this isn’t a thin veneer over a browser-based construction tool.
What you describe is, rather than using an image in a
Freeway-oriented manner, working in a fully generic way; linking to a
file rather than incorporating it into the site in more normal ways.
You really should not judge one application in terms of how another
works. Make sure you have a full and clear understanding of how it is
designed to work, try working in that way for a while, and then
criticise that.
It is very easy to end up with equally frustrating results in
Dreamweaver if you do things in certain ways. There are still extant
bugs relating to image handling that can lead to images being
destructively reoptimised, forced into incorrect formats, and even
overwriting masters, and all it takes is a certain kind of workflow.
So please, whatever software you use, make sure your workflow and
processes aren’t built on incorrect assumptions.
If you want to set up links that point directly to bare graphics, one
very simple way is to use the “Pic in New Window” action. Select the
thumbnail image you have on your page, choose Item > Actions > Pic in
New Window, and then use the Actions palette to select the source
image as well as set the size of the window you want to open, what UI
furniture you want in it, and so on. Far more control, and because
you’re working in a standard Freeway manner your images will be
included in the upload. Walter suggested some other methods, but do
try this one for a bit.