MicrostockGroup

Agency Based Discussion => Shutterstock.com => Topic started by: littleny on December 30, 2010, 09:17

Title: FTP uploaders
Post by: littleny on December 30, 2010, 09:17
I cant seem to upload using FTP client at shutterstock.  (i use it elsewhere without a problem).
I notice firefox doesnt give me an option to save my password there.  could this be the problem?
Title: Re: FTP uploaders
Post by: lisafx on December 30, 2010, 10:39
I just use the FTP option in Windows.  No problems uploading to SS or saving the password. 

If for some reason that doesn't work for you, you could try Filezilla or Coffeecup.
Title: Re: FTP uploaders
Post by: MikLav on December 30, 2010, 14:35
Not all file names are accepted at shutterstock via FTP, e.g. I can't upload my files containing spaces and brackets. Either have to rename files or upload via website.

Same with canstock by the way.
Title: Re: FTP uploaders
Post by: RacePhoto on December 30, 2010, 15:07
Not all file names are accepted at shutterstock via FTP, e.g. I can't upload my files containing spaces and brackets. Either have to rename files or upload via website.

Same with canstock by the way.


Yeah, figure that depending on the servers, people should just figure NEVER create a filename with spaces in it. Use a "-" and it works just fine. I think it's UNIX servers that start to go crazy when they fine spaces in filenames, depending on the configuration. Also a note, if you name something "0" that's zero and save it, my experience is, you can't delete it with out help from an Admin. at the server level. :(

Here's Filezilla, it works, it saves passwords, you can open multiple copies and upload to multiple sites at once... and a fan favorite FREE!

http://filezilla-project.org/ (http://filezilla-project.org/)
Title: Re: FTP uploaders
Post by: cathyslife on December 30, 2010, 15:20
Not all file names are accepted at shutterstock via FTP, e.g. I can't upload my files containing spaces and brackets. Either have to rename files or upload via website.

Same with canstock by the way.


Yeah, figure that depending on the servers, people should just figure NEVER create a filename with spaces in it. Use a "-" and it works just fine. I think it's UNIX servers that start to go crazy when they fine spaces in filenames, depending on the configuration. Also a note, if you name something "0" that's zero and save it, my experience is, you can't delete it with out help from an Admin. at the server level. :(

Here's Filezilla, it works, it saves passwords, you can open multiple copies and upload to multiple sites at once... and a fan favorite FREE!

[url]http://filezilla-project.org/[/url] ([url]http://filezilla-project.org/[/url])


You can't use a / in a filename either with Unix servers.
Title: Re: FTP uploaders
Post by: RacePhoto on December 30, 2010, 15:38
Not all file names are accepted at shutterstock via FTP, e.g. I can't upload my files containing spaces and brackets. Either have to rename files or upload via website.

Same with canstock by the way.


Yeah, figure that depending on the servers, people should just figure NEVER create a filename with spaces in it. Use a "-" and it works just fine. I think it's UNIX servers that start to go crazy when they fine spaces in filenames, depending on the configuration. Also a note, if you name something "0" that's zero and save it, my experience is, you can't delete it with out help from an Admin. at the server level. :(

Here's Filezilla, it works, it saves passwords, you can open multiple copies and upload to multiple sites at once... and a fan favorite FREE!

[url]http://filezilla-project.org/[/url] ([url]http://filezilla-project.org/[/url])


You can't use a / in a filename either with Unix servers.


Wouldn't think of it, but good point! :)

Some people claim to have problems at some sites with the "_", I don't but it was easy enough to retain my brain to use "-" for spaces in file names. No problems. Something about Macs and uploads, even though I don't own one.
Title: Re: FTP uploaders
Post by: cathyslife on December 30, 2010, 15:43
Not all file names are accepted at shutterstock via FTP, e.g. I can't upload my files containing spaces and brackets. Either have to rename files or upload via website.

Same with canstock by the way.


Yeah, figure that depending on the servers, people should just figure NEVER create a filename with spaces in it. Use a "-" and it works just fine. I think it's UNIX servers that start to go crazy when they fine spaces in filenames, depending on the configuration. Also a note, if you name something "0" that's zero and save it, my experience is, you can't delete it with out help from an Admin. at the server level. :(

Here's Filezilla, it works, it saves passwords, you can open multiple copies and upload to multiple sites at once... and a fan favorite FREE!

[url]http://filezilla-project.org/[/url] ([url]http://filezilla-project.org/[/url])


You can't use a / in a filename either with Unix servers.


Wouldn't think of it, but good point! :)

Some people claim to have problems at some sites with the "_", I don't but it was easy enough to retain my brain to use "-" for spaces in file names. No problems. Something about Macs and uploads, even though I don't own one.


Since the Mac OS is now based on Unix commands, I never use the slashes, but a person on Windows may not have encountered that problem before.
Title: Re: FTP uploaders
Post by: lisafx on December 30, 2010, 16:39
Maybe I'm misunderstanding something.  ALL my file names have spaces in them and they all upload fine with no problems.  The only thing I haven't been able to get through on SS was an ampersand (&). 

Never tried a slash because windows won't let me use those in names anyway.
Title: Re: FTP uploaders
Post by: cathyslife on December 30, 2010, 16:50
Maybe I'm misunderstanding something.  ALL my file names have spaces in them and they all upload fine with no problems.  The only thing I haven't been able to get through on SS was an ampersand (&). 

Never tried a slash because windows won't let me use those in names anyway.

Oh, Ok, I thought the slash was just a Unix problem.