He does, and the process couldn’t be smoother…
Pete
On 3 Dec 2007, at 20:40, James Wilkinson wrote:
This is the exact reason why I include in every “Welcome Email” that
all new customer sign-ups receive - the exact information that you
need to place in your Freeway Upload Preferences - as it pertains to
our servers. The information also explains how to upload the files
via IP address, to the server that your account has been installed
on, even before any nameserver changes have occurred - allowing you
to pre-prepare your site on the server before going live!
I don’t mean to rain on your parade but I don’t think it is fair to
call it a Freeway FTP problem.
It’s been solved, it was a Freeway FTP problem. Joe at Softpress
told me I needed to put my ‘public’ folder as it is written on the
server in the Directory field.
Freeway will only ever do as you tell it. If all the information is
not there then it will only do as it is asked.
I suppose there is a lesson in this for us all - if you set up your
initial document with all the correct information from the start
then there will be less headaches in the long run.
The other problem can be that it is difficult to absorb and
implement what advice everybody is offering here. Who do you listen
to, what do you try first, do you follow all suggestions or do you
just filter out the ones that you think are most credible.
I guess what I am trying to say is ‘We told you so’ but in the
clamour it is difficult to hear selectively.
D,
I meant is was something that I had to understand in the way Freeway FTP works. What Joe explained made sense but I had always used Transmit to upload and didn’t have a ‘directory’ field there. That always worked so when I tried the Freeway FTP I didn’t think about that field as hadn’t needed it before. I’ll use Freeway FTP from now on.
I listened to everyone as I knew something would click sooner or later. Also I know I can get super help from the forum and you don’t seem to mind that I’m still just learning.
Anyway, I’m over the moon now and can get back to having fun with my Freeway and look forward to moving up to Pro.
Thanks, Carolyn
On Dec 3, 2007 3:50 PM, Pete MacKenzie <email@hidden> wrote:
He does, and the process couldn’t be smoother…
Pete
On 3 Dec 2007, at 20:40, James Wilkinson wrote:
This is the exact reason why I include in every “Welcome Email” that
all new customer sign-ups receive - the exact information that you
need to place in your Freeway Upload Preferences - as it pertains to
our servers. The information also explains how to upload the files
via IP address, to the server that your account has been installed
on, even before any nameserver changes have occurred - allowing you
to pre-prepare your site on the server before going live!
I don’t mean to rain on your parade but I don’t think it is fair to
call it a Freeway FTP problem.
It’s been solved, it was a Freeway FTP problem. Joe at Softpress
told me I needed to put my ‘public’ folder as it is written on the
server in the Directory field.
Freeway will only ever do as you tell it. If all the information is
not there then it will only do as it is asked.
I suppose there is a lesson in this for us all - if you set up your
initial document with all the correct information from the start
then there will be less headaches in the long run.
The other problem can be that it is difficult to absorb and
implement what advice everybody is offering here. Who do you listen
to, what do you try first, do you follow all suggestions or do you
just filter out the ones that you think are most credible.
I guess what I am trying to say is ‘We told you so’ but in the
clamour it is difficult to hear selectively.
We too include clear upload details that match the Freeway order Passwords in Welcome e-mails.
Upload details, email passwords and set up, are probably the most asked about question on our help desk, with the question, the process is very prone to human error, with mis-spelt passwords.
Its best to let the computer do the work by copy and paste the details, until someone figures a better way.
On 3 Dec 2007, at 20:40, James Wilkinson wrote:
This is the exact reason why I include in every “Welcome Email” that
This thread looks as though it is about done, but…
I have something that relates , somewhat. After uploading my latest site I couldn’t get a browser to read any of my pics, music, graphics, etc. Everything else was good. I assumed that something was wrong inside my resource folder. I banged my head for about an hour, was about to give up, but then noticed one thing: the only capitol letter in docs folder was the “R” in the name of the Resource folder. With my other ftp software I changed “Resource” to “resource” and my site instantly worked! My only dilemma is that Freeway won’t upload unless I change it back to “Resource.” So:
If file or folder name capitalization matters to your Web server,
then it is not configured according to the standards, and needs to be
fixed.
Freeway uses a capital R because that’s the way it has worked since
day 0, and I have deployed more (working) sites on more different
servers using that layout than I can count.
You should file a support ticket with your hosting provider, and if
they don’t fix it, you should move to another host. Seriously, that
is broken behavior, and anyone who argues otherwise is not reading
their IETF RFCs.
Walter
On Feb 1, 2008, at 1:08 AM, GregM wrote:
This thread looks as though it is about done, but…
I have something that relates , somewhat. After uploading my latest
site I couldn’t get a browser to read any of my pics, music,
graphics, etc. Everything else was good. I assumed that something
was wrong inside my resource folder. I banged my head for about an
hour, was about to give up, but then noticed one thing: the only
capitol letter in docs folder was the “R” in the name of the
Resource folder. With my other ftp software I changed “Resource” to
“resource” and my site instantly worked! My only dilemma is that
Freeway won’t upload unless I change it back to “Resource.” So:
Of course, a well-configured web server will care about
capitalisation; that’s normal. What’s odd there is that GregM’s one
seems to insist that everything is in lowercase, rather than just
allowing both and treating them as distinct.
Greg, Walter’s right: if this is what’s happening and your host
doesn’t fix it immediately, find a new host.
k
Sometime around 1/2/08 (at 08:50 -0500) Walter Lee Davis said:
If file or folder name capitalization matters to your Web server,
then it is not configured according to the standards, and needs to be
fixed.
Freeway uses a capital R because that’s the way it has worked since
day 0, and I have deployed more (working) sites on more different
servers using that layout than I can count.
You should file a support ticket with your hosting provider, and if
they don’t fix it, you should move to another host. Seriously, that
is broken behavior, and anyone who argues otherwise is not reading
their IETF RFCs.
Sometime around 2/2/08 (at 12:36 -0500) GregM said:
Thanks. I had no clue. I will contact my server and see if I need to move.
Don’t fret, that’s the sort of thing that you shouldn’t have to worry
about. It could be a mistake happening somewhere in the mix (did you
upload the stuff yourself or let Freeway manage it?)… but if not,
get different hosting.
I had Freeway upload everything. With my work-around Freeway works perfectly. I just have to remember to change the “r” character back and forth. “yuck”
Sometime around 2/2/08 (at 15:27 -0500) GregM said:
I had Freeway upload everything. With my work-around Freeway works
perfectly. I just have to remember to change the “r” character back
and forth. “yuck”
Yuck is the polite form of what I’d be saying!
That seems to be a weird hosting configuration issue, and it is
simply not acceptable. What host company is this? It would be good to
know where not to point my bargepole…
Well, I didn’t have anything to report until now. My WEB server finally did whatever they needed to do to fix the uppercase vs lowercase “R” in the Resource folder. My uploads now work without a work-around. That only took slightly over two months. Whew!