Client (restaurant) wants to upload 1 file to server daily. How?

files

[bartainer]

Hello,

I have a client who wants to upload 1 file (specials menu) to the server daily. I don't want him to screw up the site; however, I'm not doing this everyday. Can I use filezilla? He can drag and drop the file into the folder and upload. If not, what do you recommend?

Thanks.

[kiwibrit]

Depends. If if is a set layout, I would use a (access password controlled) form to populate a flat file. That can be called up as an include in the final menu page.

Or you can use a CMS of some sort.

[bwnbwn]

You can set up an ftp account for just one folder on the site if he messes it up the it will only mess up that folder or page.

Set him up ftp download the page or folder he is going to be in and show him how to change the menue prices and etc. This is a great way to get customers involved with the site development and yet restrict them to just on folder on the site and nothing else.

[jdMorgan]

For simple stuff, I like to let the customer use tools he's familiar with. For example, in a similar application, I let the client upload a .csv file straight out of Microsoft Excel, and then a PERL script included on the page reads that .csv file and outputs valid HTML (or a very specific error message if the file format is incorrect in any way).

If the client can be trusted to use an FTP upload, that's a simple way to do it. If not, I like the form-based method kiwibrit mentioned above.

Jim

[g1smd]

Upload some sort of file, containing only content, which is "included" into a pre-existing framework (*not* using i-frames or frames) of heading and navigation. I use something like this on very simple sites, but the person making the changes has to wrap content in heading and paragraph tags themselves, and know how to use strong and emphasis tags too. All styling happens from an external stylesheet which they cannot reach.

For one page, it would be overkill to use some sort of wiki application, but the easy formatting options that a wiki allows seems almost tempting. In this case, new page creation would be disallowed, and there would only be one authorised user.

[incrediBILL]

You can easily build a .bat file that uploads a specific file to a specific location.

You'll need three files in the same directory, such as "c:\ftpupload".

In "c:\ftpupload" place the following 3 files:

1. fileupload.bat to execute the upload
2. fileupload.txt with the FTP commands
3. specialsmenu.html with the daily specials

First a file called fileupload.bat that contains the following:

ftp -s:fileupload.txt

Next add this content to fileupload.txt changing the server, user and paths to fit your needs.

open example.com
(user name here)
(password here)
cd server/path/to/upload/specials
binary
prompt
mput c:\ftpupload\specialsmenu.html
close
bye

Now create 2 shortcuts, one to the specials menu to edit, the second shortcut to this script. Now it'll take one click to edit the file, a second click to upload the file after the daily edits.

Can't be any easier than that?

[bartainer]

I think I'll create an include file (e.g., menu.php). It will be text only without the header etc. The client will just upload it to the folder and whala...done. I'll use filezilla for his ftp.

[rocknbil]

If your client is like many of mine that are not interested in learning all the tech stuff ("I'm not a computer guy like you") I'd write them a small password-protected script to upload the files, and automate the process of storing the files precisely where you want them. There are many on the 'net to use as a starting point.

This has a number of distinct advantages. It makes the client feel like they have control, it makes them feel smarter, and it prevents the unexpected phone calls ("I think I messed something up, I went to upload that file and it was the wrong file, I tried to delete it but I deleted index.html, is that important?")

The other is when you get tired of this client and pass it on to someone else you don't have to explain all the hidden exceptions (customer has access to site, but only this directory . . . don't delete this, don't delete that . . . you get the idea . . .)