SSI Woes on 1&1 Buiness Package

[Css Lover]

I uploaded my web site to a 1&1 business package.

I did get SSI to run ok by adding a htaccess file. Sadly, I forgot what
directory I put in in. Either my web sites home directory, or the directory
that the web site was in, sharing with another web site.

After seeing the web site work, i then converted all the pages to shtml.

I failed to get Apache working on my own computers, so ended up using Win 2000
and the personal web manager, to actually see the web site work and to test all
the links out (I feel safer testing links in real time as well as link tester,
plus I have javascript I need to see)

In DW, you do get the design view accomodating SSI, so you can see all your
SSI as you work. You can see it, but cannot assume that what you see is what
you'll get. DW say as much.

You cannot just use your browser to see a shtml website.

Had I just stayed with xhtml, I could see the design working, but would have
100 pages waiting to be corrected if things went wrong or links needed to be
added.

There is no way I can live with a menu with over 100 links on each page and
that what I had! You've been there coding tons of pages just because you chose
to include a menu on each page written in html code. You copy that page as a
template and think you've done yourself a favour. You've actually created
future work.

I'm just using SSI for what it is. I hope.

After uploading to the 1&1 web space, I hit a stumbling block as my SSI does
not show. All I see is the main content which is not SSI and just written up in
html.

Also, I found another htaccess file in 'logs', this I presume is 1&1's doing.
I've emailed but got to wait a few days because they are 'busy'. I'm not
running a business web site, but if I was, this would be worrying.

The htacess file that I presume is writing over the ones I've put up has the
following lines...

Satisfy any
Order Deny,Allow
Allow from ***.**.*.*/**
Allow from ***.**.*.*/**
Allow from ***.**.*.*/**
Deny from all
RemoveType .html .gif
AuthType Basic
AuthName "Access for /logs"
AuthUserFile /*name*/homepages/**/******/htpasswd
require user *********

I've 'starred out' some ip numbers, plus user names and passwords.

I did not write the above htaccess file I just found it in 'logs'. I'm
wondering whether it was put there because I uploaded my own htacess, maybe it
overwrites mine, or something.

I wonder now if my package off 1&1 allows SS1.

I have php and cgi and so on.

Thanks in advance.

[Css Lover]

O.k.

My 1&1 package does have SSI - so I'm doing something wrong.

The FAQs were hidden away (ie, the site search engine never linked to all
instances of SSI.

The business package, at ?8.99 a month has 20gb limit, but plenty of scope for
some like me.

Anyone in the UK using 1&1 and SSI would obviously be able to help me.

Your help would be appreciated and God himself will reward you.

[Matthew]

Hi CSS Lover:

I'm sure you found it... but just incase, here is the link to 1and1's faq on
SSI's:
[url]http://faq.1and1.com/scripting_languages_supported/ssi_server_side_includes/index.html[/url]

The only SSI's I have tried to use so far are with PVII's Pop Menu. Here is
their link on how to use SSI's... it might give you some idea's:
[url]http://www.projectseven.com/products/menusystems/pmm/user_guide/site_wide/includes/overview.htm[/url]

Matthew

"Css Lover" <webforumsuser@macromedia.com> wrote in message
news:dv1p1m$l27$1@forums.macromedia.com...

> O.k.
>
> My 1&1 package does have SSI - so I'm doing something wrong.
>
> The FAQs were hidden away (ie, the site search engine never linked to all
> instances of SSI.
>
> The business package, at ?8.99 a month has 20gb limit, but plenty of scope
> for
> some like me.
>
> Anyone in the UK using 1&1 and SSI would obviously be able to help me.
>
> Your help would be appreciated and God himself will reward you.
>
>

[Css Lover]

Thanks Matthew, I'v sorted it all out now.

What I was doing was pointing to files when I should have pointed to a virtual
, if you know what I mean.

If the SSI files are in the same directory as the webpage, you point to a
file, but if outside of that directory, and if you use several SSI files, you
need to use the virtual 'command' or whatever you call it.

Example...

<!--#include virtual="../includes/cssandswitcher.html" -->

This points to a SSI file which is in its own folder and the web page I built
is also in its own folder.

So, another problem solved!

It is, I might add, a great relief, as I was almost in tears over this.

I guess my Apache server woes were because of me using a file instead of
virtual.

Windows web service is not fussy! It gives a false sense of security as the
web site works fine using that!

It is a good job I never took that as 'proof' all was well.