frontpage installation

Hi,

Just a quick question about installation.. I just purchased the Pro version and realize installation is free, but I'd like to give it a go myself so that I can hopefully learn something in the process. Anyway, I'd like the web on my hard drive (in Frontpage 2002) to match the web on my server. I know the directions say to unzip, then FTP to the server. But, is it possible to unzip to my web on the hard drive, then publish from Frontpage. I've read a few posts here about Frontpage not liking scripts all that well. .. but just wanted to make sure. If any of you more knowledgale folks here could give a suggestion it would be greatly appreciated. Thanks.

-Tate

OK, thanks... so you're telling me to set up Frontpage to ignore the /amember folder so that Frontpage won't want to try and delete it each time I go to publish (since it will reside on the server, but not my hard drive). Couldn't I just tell Frontpage not to delete the folder each time I publish. Or I suppose I could create an empty subweb on my hard drive called 'amember' and choose not to publish subwebs?

Better yet, would Dreamweaver be the better option for maintaining an aMember web? If so, do you know if it's possible to convert Frontpage to Dreamweaver? I've probably maxed out the number of questions I'm allowed to ask in one post!;]

That is probably your best bet.

Um. Er. I use FrontPage. And given that people pay me that would make me a professional.

Having said that I use NO native FP features (includes, themes, forms, nothing that means getting into those bots or needing extensions), NEVER publish, mostly design in HTML view, always FTP and also use DW, Homesite, Notepad, whatever is the best tool for the job. But the reason I use FP as my 'base camp' so to speak is that it has the best file management features of all of them.

FP is sniffed at mightily, but usually by those who have either never used it or used it too little to get to know it or used it back in the FP97 days when it truely was rubbish. Much maligned program. Good program.

thanks for your insight abbeyvet,

You said you never use any FP native features and always FTP.. is that to say that everyone using aMember on their site shouldn't either? I was under the impression that as long as I didn't try and alter the /amember using FP I would fine.

Here's some background on my site. I am using a purchased template (wish I hadn't!) and have been using FP 2002 to edit and publish my site. The only bots that are used that I can see are navigation includes. The amember protection method that I'm using is mod_rewrite with php include and it's protecting my /members folder. What are the ramifications of me using FP to publish files to my protected /members folder? I'd like to use FP to create my files and publish as it does save lots of time. Especially for someone like me who doesn't know or have much time to learn about programming. But I suppose I don't really have a choice do I?

Alex, I don't like those options!

I found this add in for Frontpage that allows you to work with PHP files. Alex, would you mind having a look to see if it would be a good solution to this problem.. As always thank you.

http://www.frontpage-templates-themes.com/shop-ftt-tools-phprocket.shtml

No, my PC does not have dedicated IP, just my website.

I thinks it's becoming clear I have a long way to go before I understand how all this works. I guess I'm not sure why publishing a file from Frontpage to my members area won't work. By the way, it did try this and it seems to work fine (although my login info isn't remembered - I have to login each time I leave the members area, then come back) What is it about the Frontpage publishing process that makes this a bad choice?

Publishing in Frontpage is a bit different than FTP. Apparently, publishing is required when you are using Fronpage components like forms, discussion, shared borders, etc. If you FTP pages with these components they may not work. Since I'm not using these components, I suppose it's OK to FTP to my server. However, i've read a few times where mixing publishing and FTPing together is not recommended. It appears to work OK publishing a file to my protected \members directory, so I'm not sure what the problem is. I don't know what to think at this point.. I guess I'll just continue publishing to my /members directory until it doesn't work anymore. I'm just having difficulty understanding why published files are no good for php_include mod_rewrite protected directories.

There are none, as long as you NEVER tick the FP option when publishing of "Upload overwriting all files on server" (or words to that effect). You can do this.

This is what you should do, which is something I have recommended often for people using FP and various scripts, and which has never been a problem.

1. Keep aMember out of your local FP web COMPLETELY. Keep the files elsewhere, it matters not a whit where.

2. Carry on as usual but never let FP delete anything off the server and never use the option above.

That is all.

You must however use a standard FTP client to upload the aMember files NOT FP even in FTP mode. Ever.

If mixing FTP and publishing in this way is a problem, then it is a problem with your host, not with FP. I run servers and it is not only possible but frequently done.

The reason this may have been mentioned to you is probably to do with FP includes - if you FTP these will appear, but unlike ordinary includes, if you edit an included page, then FTP it, the changes will not appear on the standard pages. For these type of edits to update as they should you need to publish.

However I repeat - there is NO problem with publishing parts of the site and FTPing others, none.

Also it is possible to work with PHP files in FP, and I do so reasonably regularly, though generally I use Homesite for this. What you do is this:

In Frontpage go to Tools>Options>Configure Editors
Choose "Add"
Put PHP for file type
Put the same information as you have for htm, html etc. - this is usually
Editor Name: FrontPage
Command: frontpg.exe
Save

Having said that, if you do this the files for aMember should still not be in your main local web.

Hope this helps.

very helpful, thanks again abbeyvet-- your posts are greatly appreciated.

Forgot to ask .. when using amember components in your pages (ie. adding a login form to my homepage or or adding member data to the member pages) is it OK to publish then?

Yes adding a form will be fine, that will be straight HTML.

Not sure what you mean about adding data to member pages, if you mean adding any standard content to the pages in protected directories, then there is no problem.