Error with FP. HELP!!

I am trying to setup my new site using Frontpage. When I try to access it, I get the following error message:
"The folder 'http://medical-topics.com/' isn't accessible. The folder may be located in un unavailable location, protected with a password, or the filename contanins a / or ."

I have 5 other sites and I can get to them without any problems at all using FP, so my settings are correct. Does anyone know what I need to do to access my site?

Thanks

 

use notepad

 

LOL

may I reccomend HAPedit.

 

Sure... notepad... I can hardly figure out FP...

Anyway, I signed up for hostgator and had this problem. They ignored my trouble ticked so I did a paypal chargeback and told them to go to hell.

I then signed up to micfo.com. I also had the same problem. They started working on the server to get this fixed and now everything is working fine.

Once again, Micfo shows that their customer support is one of the best.

 

Hostgator does suck!

 

It appears that a redirection is taking place.

Check that.

tom

------------------- Correction -------------

Working fine now, I see "Test"

 

So fryman, was this a configuration of the server side FP? I never check that box when I create a site, so I'm just curious.

 

Well, after finally getting my VPS I have learned a lot about these kind of problems. Turns out that sometimes when you get a shared hosting account you have to go to the cpanel and enable the FP extensions. But most of the time the extensions get screwed up, so the server admin (or the shared hosting company) needs to enable them for you.

 

I think you would be surprised to see how easy HTML coding is Fryman. You should make a page with a simple table in it and a few other things and then try to replicate it by hand. Then you will see all of the crap that FP throws in there for your viewing pleasure. I am sure it would help your rankings to get that crap out of there.

 

I am learning... but still not enough to rely just on a notepad...

I have many sites... one day I was bored and decided to clean up the code on one of them, boy, did that take time... it really is amazing all the crap that I took off. I also sent a lot of it to a css file and my page code looks really neat

I am taking a dreamweaver and CSS course in a couple of months. That will finally allow me to ditch FP and move on to better coding.

 

Newer versions of frontpage don't have as much added code -- unless you start using some of their 'built-in' items. Overall FP is much better than it use to and saves a lot -- did I say A LOT of time...

 

What I like is being able to change something and checking straight away how it looks like.

Plus, I always use the "optimize code" command and that takes care of a lot of the mess

 

Actually Debunked, it looks like it still puts a ton of unecessary tags in there. I just checked out your heywhatsyour site and while there is less code in there than I saw using FP98 back in the day, there are still a ton of tags in there that don't need to be. BTW, I like the bus.

 

fryman, are you using something that ACTUALLY NEEDS frontpage extensions?

 

Yup, I work with FP on all my sites.

 

Yea, this is pretty much a general "it's broken" error. Heh... almost always on the server side. Frontpage extensions are the most annoying thing ever. Try setting them up with chroot + suexec + apache. Ugh.

It's so stupid, instead of just ftp or sftp, let's post this content to an suid binary, for which you don't even have the source for... ugh ugh UGH.

 

ssh and vim, is the way to go. =)

 

Why take the time to type? Frontpage is easy.
On your original problem:
"The folder 'http://medical-topics.com/' isn't accessible."
Did you publish it using frontpage?
Did you have the last / at the end?
If yes not a valid url.
Maybe fp extensions where not installed on that web.
Note it's calling it a folder also.
So it could be all and some of the above.
Also when you accesss your site, only use frontpage.
FTP is ok for server files such as: .htaccess or robots.txt but not for editing or uploading / downloading fp files.
Also it's the hosting companies on the fp extension problems - they don't know what they are doing.

 

Also when you published your web site with Frontpage. Did you have an index.html file?

 

Thanks, but the problem has been solved long ago